BIZTRAC BETA
COMPANY REGISTER PROFILE
985082189 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS

Org. no. 985082189 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −389,000
Equity NOK −4.5m
Incorporated 2002
Share capital NOK 100,000

Signals

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

BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 985082189. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering av enhver art, herunder utleie og forvaltning av fast eiendom, samt deltagelse i andre selskaper.”.

Former names: AS STARTSKUDDET 454

Key figures · 2025

Operating profit
NOK −389,000
▲ +93 %
Equity
NOK −4.5m
▼ −9 %

Financial health · 2025

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

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

Who owns BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS?

BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS
· NOK −389,000 profit

BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS

Who owns BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS?

OSLO EIENDOMSSELSKAP AS is the largest registered owner, with 100.0%.

Where is BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING AS based?

BÆRUM PROSJEKT- OG EIENDOMSUTVIKLING 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 02.09.2026.

Report a problem

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