biztrac. BETA
COMPANY REGISTER PROFILE
934058135 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of china and glassware and cleaning materials

GASTIQ AS

Org. no. 934058135 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 0
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-31 Adresseendring registrert 2026-05-31.

GASTIQ AS is registered as a limited company in Lillestrøm, Akershus with organisation number 934058135. The business is classified under wholesale of china and glassware and cleaning materials (NACE 46.440). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Import, eksport, kjøp, salg, engros- og detaljhandel med nytt og brukt storkjøkkenutstyr, kjøkkenmaskiner, kjøle- og fryseutstyr, restaurantdrift, invetar, reservedeleer og tilhørende produkter til restaurant-, hotell-, catering- og serveringsbransjen. Selskapet kan også drive med montering, installasjon, vedlikehold, reperasjon og service av storkjøkkenutstyr og maskiner, samt investeringer og annen virksomhet som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 0
▼ −100 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GASTIQ AS?

GASTIQ AS
· NOK 0 profit

GASTIQ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GASTIQ AS

Who owns GASTIQ AS?

Tajjamal Iqbal is the largest registered owner, with 100.0%.

Where is GASTIQ AS based?

GASTIQ AS has its business address in Strømmen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.