BIZTRAC BETA
Development of building projects

ALFARHEIM EIENDOM AS

Org. no. 984890451 Limited company (AS) Elverum Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK −290,000
Equity NOK 4.9m
Incorporated 2002
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−290k kr).

ALFARHEIM EIENDOM AS is registered as a limited company in Elverum, Innlandet with organisation number 984890451. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom for salg og utleie, kjøp og salg av aksjer, samt det som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK −290,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK −290,000
Equity
NOK 4.9m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns ALFARHEIM EIENDOM AS?

HELLEBEKKEN AS
ALFARHEIM EIENDOM AS
NOK 2.6m rev. · NOK −290,000 profit

ALFARHEIM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALFARHEIM EIENDOM AS

Who owns ALFARHEIM EIENDOM AS?

HELLEBEKKEN AS is the largest registered owner, with 100.0%.

What is the revenue of ALFARHEIM EIENDOM AS?

ALFARHEIM EIENDOM AS had revenue of NOK 2.6m in 2024.

Who is the general manager of ALFARHEIM EIENDOM AS?

John Rune Hellebekken is registered as general manager of ALFARHEIM EIENDOM AS.

Where is ALFARHEIM EIENDOM AS based?

ALFARHEIM EIENDOM AS has its business address in Elverum.

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.