BIZTRAC BETA
Rental and operating of own or leased real estate

OSC EIENDOM AS

Org. no. 928787230 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 663,000
Operating profit NOK −178,000
Equity NOK −5.9m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5,9 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−178k kr).

OSC EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 928787230. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å investere i eiendommer til egen bruk og herunder utvikle disse til ulike virksomheter. Selskapet skal også investere i eiendomsselskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 663,000 in revenue and NOK −178,000 in operating profit.

Key figures · 2025

Revenue
NOK 663,000
Operating profit
NOK −178,000
Equity
NOK −5.9m

Financial health · 2025

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

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

Who owns OSC EIENDOM AS?

OSC HOLDING AS
OSC EIENDOM AS
NOK 663,000 rev. · NOK −178,000 profit

OSC EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSC EIENDOM AS

Who owns OSC EIENDOM AS?

OSC HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OSC EIENDOM AS?

OSC EIENDOM AS had revenue of NOK 663,000 in 2025.

Where is OSC EIENDOM AS based?

OSC 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.