BIZTRAC BETA
Rental and leasing of air transport equipment

BRANNHAUGEN EIENDOM AS

Org. no. 997843193 Limited company (AS) Frosta Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 14.5m
Operating profit NOK 10.0m
Equity NOK 20.0m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-02-09 Adresseendring registrert 2026-02-09.

BRANNHAUGEN EIENDOM AS is registered as a limited company in Frosta, Trøndelag with organisation number 997843193. The business is classified under rental and leasing of air transport equipment (NACE 77.350). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Erverve, eie, forvalte og leie ut luftfartøy og båter, samt å foreta investeringer i og utvikling av fast eiendom, aksjer og øvrige verdipapirer, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.5m in revenue and NOK 10.0m in operating profit.

Key figures · 2025

Revenue
NOK 14.5m
Operating profit
NOK 10.0m
Equity
NOK 20.0m
Est. value
NOK 43.8m

Financial health · 2025

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

Who owns BRANNHAUGEN EIENDOM AS?

HELI-HOLDING AS
BRANNHAUGEN EIENDOM AS
NOK 14.5m rev. · NOK 10.0m profit

BRANNHAUGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRANNHAUGEN EIENDOM AS

Who owns BRANNHAUGEN EIENDOM AS?

HELI-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRANNHAUGEN EIENDOM AS?

BRANNHAUGEN EIENDOM AS had revenue of NOK 14.5m in 2025.

Where is BRANNHAUGEN EIENDOM AS based?

BRANNHAUGEN EIENDOM AS has its business address in Frosta.

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.