BIZTRAC BETA
Non-specialised wholesale trade

GAZECHIM COMPOSITES NORGE AS

Org. no. 918026770 Limited company (AS) Malvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 42.7m
Operating profit NOK 592,000
Equity NOK 12.0m
Incorporated 2016
Share capital NOK 100,000

GAZECHIM COMPOSITES NORGE AS is registered as a limited company in Malvik, Trøndelag with organisation number 918026770. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vare salg av komposittprodukter og tilhørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 42.7m in revenue and NOK 592,000 in operating profit.

Key figures · 2025

Revenue
NOK 42.7m
Operating profit
NOK 592,000
Equity
NOK 12.0m
Est. value
NOK 8.9m

Financial health · 2025

Liquidity
3.27
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
69.4%
Very good
Equity as a share of total capital

Who owns GAZECHIM COMPOSITES NORGE AS?

GAZECHIM COMPOSITES NORDEN AB
GAZECHIM COMPOSITES NORGE AS
NOK 42.7m rev. · NOK 592,000 profit

GAZECHIM COMPOSITES NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAZECHIM COMPOSITES NORGE AS

Who owns GAZECHIM COMPOSITES NORGE AS?

GAZECHIM COMPOSITES NORDEN AB is the largest registered owner, with 100.0%.

What is the revenue of GAZECHIM COMPOSITES NORGE AS?

GAZECHIM COMPOSITES NORGE AS had revenue of NOK 42.7m in 2025.

Who is the general manager of GAZECHIM COMPOSITES NORGE AS?

James Walton is registered as general manager of GAZECHIM COMPOSITES NORGE AS.

Where is GAZECHIM COMPOSITES NORGE AS based?

GAZECHIM COMPOSITES NORGE AS has its business address in Hommelvik.

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

Report a problem

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