biztrac. BETA
COMPANY REGISTER PROFILE
983525245 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

OCM EIENDOM AS

Org. no. 983525245 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 557,000
Operating profit NOK 421,000
Equity NOK 12.6m
Incorporated 2001
Share capital NOK 150,000

OCM EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 983525245. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 150,000, divided into 200 shares. The company's stated purpose is: “Investering.”. The most recent filed accounts, for the 2025 financial year, show NOK 557,000 in revenue and NOK 421,000 in operating profit.

Key figures · 2025

Revenue
NOK 557,000
▲ +9 %
Operating profit
NOK 421,000
▲ +5 %
Equity
NOK 12.6m
▲ +1 %
Est. value
NOK 9.7m

Financial health · 2025

Liquidity
15.10
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
69.5%
Very good
Equity as a share of total capital

Who owns OCM EIENDOM AS?

OCM EIENDOM AS
NOK 557,000 rev. · NOK 421,000 profit

OCM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OCM EIENDOM AS own?

OCM EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OCM EIENDOM AS

Who owns OCM EIENDOM AS?

Ole Clausen Mørch is the largest registered owner, with 100.0%.

What is the revenue of OCM EIENDOM AS?

OCM EIENDOM AS had revenue of NOK 557,000 in 2025.

Who is the general manager of OCM EIENDOM AS?

Ole Clausen Mørch is registered as general manager of OCM EIENDOM AS.

Where is OCM EIENDOM AS based?

OCM 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 03.10.2026.

Report a problem

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