BIZTRAC BETA
Rental and operating of own or leased real estate

HENSMOEN EIENDOM AS

Org. no. 890751202 Limited company (AS) Ringerike Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −133,000
Equity NOK 4.1m
Incorporated 2006
Share capital NOK 1.1m

Signals

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

HENSMOEN EIENDOM AS is registered as a limited company in Ringerike, Buskerud with organisation number 890751202. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.1m, divided into 110 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignede virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −133,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −133,000
Equity
NOK 4.1m
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns HENSMOEN EIENDOM AS?

TRONRUD EIENDOM AS
HENSMOEN EIENDOM AS
NOK 0 rev. · NOK −133,000 profit

HENSMOEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HENSMOEN EIENDOM AS er morselskap for 31 datterselskaper:

Frequently asked questions about HENSMOEN EIENDOM AS

Who owns HENSMOEN EIENDOM AS?

TRONRUD EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HENSMOEN EIENDOM AS?

HENSMOEN EIENDOM AS had revenue of NOK 0 in 2024.

Where is HENSMOEN EIENDOM AS based?

HENSMOEN EIENDOM AS has its business address in Hønefoss.

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.