BIZTRAC BETA
Buying and selling of own real estate

HØNEFOSS OFFENTLIG EIENDOM AS

Org. no. 926707477 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −482,000
Equity NOK 41.6m
Incorporated 2021
Share capital NOK 2.6m

Signals

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

HØNEFOSS OFFENTLIG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 926707477. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 2.6m, divided into 520000 shares. The company's stated purpose is: “Å forvalte investeringen i Offentlig Bygg Hønefoss AS (org. nr. 921 563 183), som eier eiendommen gnr. 318, bnr. 71 og 74, snr. 1 og 2 i Ringerike kommune, samt tilknyttet virksomhet.”.

Key figures · 2024

Operating profit
NOK −482,000
Equity
NOK 41.6m
Est. value
NOK 37.9m

Financial health · 2024

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

Who owns HØNEFOSS OFFENTLIG EIENDOM AS?

INVEST63 AS
HØNEFOSS OFFENTLIG EIENDOM AS
· NOK −482,000 profit

HØNEFOSS OFFENTLIG EIENDOM AS has 7 registered shareholders:

All shareholders and roles →

Which companies does HØNEFOSS OFFENTLIG EIENDOM AS own?

HØNEFOSS OFFENTLIG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HØNEFOSS OFFENTLIG EIENDOM AS

Who owns HØNEFOSS OFFENTLIG EIENDOM AS?

INVEST63 AS is the largest registered owner, with 26.0%.

Where is HØNEFOSS OFFENTLIG EIENDOM AS based?

HØNEFOSS OFFENTLIG EIENDOM AS has its business address in Oslo.

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.