BIZTRAC BETA
Development of building projects

OHC EIENDOM AS

Org. no. 983581161 Limited company (AS) Bærum Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK −13,000
Equity NOK −1.4m
Incorporated 2001
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

OHC EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 983581161. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre tjenester i fast eiendom og/ eller ha eierinteresser i annen relatert virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK −13,000
Equity
NOK −1.4m

Financial health · 2024

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

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

Who owns OHC EIENDOM AS?

OHC HOLDING AS
OHC EIENDOM AS
NOK 2.4m rev. · NOK −13,000 profit

OHC EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OHC EIENDOM AS

Who owns OHC EIENDOM AS?

OHC HOLDING AS is the largest registered owner, with 95.0%.

What is the revenue of OHC EIENDOM AS?

OHC EIENDOM AS had revenue of NOK 2.4m in 2024.

Who is the general manager of OHC EIENDOM AS?

Ole Henrik Christensen is registered as general manager of OHC EIENDOM AS.

Where is OHC EIENDOM AS based?

OHC EIENDOM AS has its business address in Jar.

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.