BIZTRAC BETA
Rental and operating of own or leased real estate

HAGLUND EIENDOM AS

Org. no. 823601832 Limited company (AS) Åmot Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 2.2m
Equity NOK 48,000
Incorporated 2019
Employees 15
Share capital NOK 1.4m

HAGLUND EIENDOM AS is registered as a limited company in Åmot, Innlandet with organisation number 823601832. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019 and has 15 registered employees. Registered share capital is NOK 1.4m, divided into 26752 shares. The company's stated purpose is: “Investering og utleie av fast eiendom. Selskapet kan også investere i andre selskaper av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 2.2m
Equity
NOK 48,000
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

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

Who owns HAGLUND EIENDOM AS?

HAGLUND HOLDING 1 AS
HAGLUND EIENDOM AS
NOK 7.0m rev. · NOK 2.2m profit

HAGLUND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAGLUND EIENDOM AS

Who owns HAGLUND EIENDOM AS?

HAGLUND HOLDING 1 AS is the largest registered owner, with 100.0%.

What is the revenue of HAGLUND EIENDOM AS?

HAGLUND EIENDOM AS had revenue of NOK 7.0m in 2024.

Who is the general manager of HAGLUND EIENDOM AS?

Marianne Haglund is registered as general manager of HAGLUND EIENDOM AS.

Where is HAGLUND EIENDOM AS based?

HAGLUND EIENDOM AS has its business address in Rena.

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.