BIZTRAC BETA
Rental and operating of own or leased real estate

HILLEGARN EIENDOM AS

Org. no. 991445374 Limited company (AS) Kristiansand Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −679,000
Equity NOK 40.4m
Incorporated 2007
Share capital NOK 10.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−679k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HILLEGARN EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 991445374. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 10.0m, divided into 100000 shares. The company's stated purpose is: “Investering i fast eiendom, herunder også investering i andre aksjeselskaper.”.

Key figures · 2024

Operating profit
NOK −679,000
Equity
NOK 40.4m
Est. value
NOK 135.5m

Financial health · 2024

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

Who owns HILLEGARN EIENDOM AS?

MOSVOLD & CO AS
HILLEGARN EIENDOM AS
· NOK −679,000 profit

HILLEGARN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HILLEGARN EIENDOM AS own?

HILLEGARN EIENDOM AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about HILLEGARN EIENDOM AS

Who owns HILLEGARN EIENDOM AS?

MOSVOLD & CO AS is the largest registered owner, with 50.0%.

Who is the general manager of HILLEGARN EIENDOM AS?

Roy Gundersen is registered as general manager of HILLEGARN EIENDOM AS.

Where is HILLEGARN EIENDOM AS based?

HILLEGARN EIENDOM AS has its business address in Kristiansand S.

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.