BIZTRAC BETA
COMPANY REGISTER PROFILE
999213197 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

OCH EIENDOM AS

Org. no. 999213197 Limited company (AS) Øksnes Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK −106,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−106k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

OCH EIENDOM AS is registered as a limited company in Øksnes, Nordland with organisation number 999213197. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK −106,000

Financial health · 2025

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

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

Who owns OCH EIENDOM AS?

OCH EIENDOM AS
· NOK −14,000 profit

OCH EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OCH EIENDOM AS

Who owns OCH EIENDOM AS?

Ole Christian Hansen is the largest registered owner, with 100.0%.

Who is the general manager of OCH EIENDOM AS?

Ole Christian Hansen is registered as general manager of OCH EIENDOM AS.

Where is OCH EIENDOM AS based?

OCH EIENDOM AS has its business address in Myre.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.