BIZTRAC BETA
Development of building projects

OSLOFJORD UTVIKLING AS

Org. no. 994344951 Limited company (AS) Frogn Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK −1.8m
Incorporated 2009
Share capital NOK 100,000

Signals

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

OSLOFJORD UTVIKLING AS is registered as a limited company in Frogn, Akershus with organisation number 994344951. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1002 shares. The company's stated purpose is: “Selskapets formål er deltakelse med kapital i andre foretak, eiendomsutvikling, utleie av eiendom, kjøp og salg av eiendom.”.

Key figures · 2024

Operating profit
NOK −24,000
Equity
NOK −1.8m

Financial health · 2024

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

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

Who owns OSLOFJORD UTVIKLING AS?

TEPER AS
OSLOFJORD UTVIKLING AS
· NOK −24,000 profit

OSLOFJORD UTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does OSLOFJORD UTVIKLING AS own?

OSLOFJORD UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OSLOFJORD UTVIKLING AS

Who owns OSLOFJORD UTVIKLING AS?

TEPER AS is the largest registered owner, with 33.3%.

Who is the general manager of OSLOFJORD UTVIKLING AS?

Richard Slåke is registered as general manager of OSLOFJORD UTVIKLING AS.

Where is OSLOFJORD UTVIKLING AS based?

OSLOFJORD UTVIKLING AS has its business address in Drøbak.

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.