BIZTRAC BETA
Manufacture of non-domestic air conditioning equipment

TROX AURANOR AS

Org. no. 976699963 Limited company (AS) Gran Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 496.8m
Operating profit NOK 63.4m
Equity NOK 305.1m
Incorporated 1996
Employees 164
Share capital NOK 9.3m

TROX AURANOR AS is registered as a limited company in Gran, Innlandet with organisation number 976699963. The business is classified under manufacture of non-domestic air conditioning equipment (NACE 28.250). The company was incorporated in 1996 and has 164 registered employees. Registered share capital is NOK 9.3m, divided into 9281 shares. The company's stated purpose is: “Investere i andre selskaper samt drive med utvikling, produksjon og salg av luftbehandlings- og ventilasjonssystemer.”. The most recent filed accounts, for the 2024 financial year, show NOK 496.8m in revenue and NOK 63.4m in operating profit.

Key figures · 2024

Revenue
NOK 496.8m
Operating profit
NOK 63.4m
Equity
NOK 305.1m
Est. value
NOK 426.4m

Financial health · 2024

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

Who owns TROX AURANOR AS?

TROX SE
TROX AURANOR AS
NOK 496.8m rev. · NOK 63.4m profit

TROX AURANOR AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TROX AURANOR AS er morselskap for 1 datterselskap:

Frequently asked questions about TROX AURANOR AS

Who owns TROX AURANOR AS?

TROX SE is the largest registered owner, with 100.0%.

What is the revenue of TROX AURANOR AS?

TROX AURANOR AS had revenue of NOK 496.8m in 2024.

Who is the general manager of TROX AURANOR AS?

John Georg Storvik is registered as general manager of TROX AURANOR AS.

Where is TROX AURANOR AS based?

TROX AURANOR AS has its business address in Jaren.

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.