biztrac. BETA
COMPANY REGISTER PROFILE
890497292 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other activities of other membership organisations

H.M. AARHØNEN BYGNINGSLINJENS FORENING

Org. no. 890497292 Association/club/organisation (FLI) Trondheim Incorporated 1913 Active
Ownership graph ↗
Revenue 2024 NOK 274,000
Operating profit NOK 274,000
Equity NOK 2.1m
Incorporated 1913

H.M. AARHØNEN BYGNINGSLINJENS FORENING is registered as a association/club/organisation in Trondheim, Trøndelag with organisation number 890497292. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1913. The most recent filed accounts, for the 2024 financial year, show NOK 274,000 in revenue and NOK 274,000 in operating profit.

Key figures · 2024

Revenue
NOK 274,000
▼ −88 %
Operating profit
NOK 274,000
▼ −48 %
Equity
NOK 2.1m
▲ +0 %
Est. value
NOK 2.3m

Financial health · 2020

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

Who owns H.M. AARHØNEN BYGNINGSLINJENS FORENING?

No shareholders are registered for H.M. AARHØNEN BYGNINGSLINJENS FORENING in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about H.M. AARHØNEN BYGNINGSLINJENS FORENING

What is the revenue of H.M. AARHØNEN BYGNINGSLINJENS FORENING?

H.M. AARHØNEN BYGNINGSLINJENS FORENING had revenue of NOK 274,000 in 2024.

Who is the general manager of H.M. AARHØNEN BYGNINGSLINJENS FORENING?

Solveig Aschehoug Morken is registered as general manager of H.M. AARHØNEN BYGNINGSLINJENS FORENING.

Where is H.M. AARHØNEN BYGNINGSLINJENS FORENING based?

H.M. AARHØNEN BYGNINGSLINJENS FORENING has its business address in Trondheim.

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.