BIZTRAC BETA
Development of building projects

VOLLEBEKK NÆRING B1 AS

Org. no. 928884708 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −26.8m
Equity NOK −20.5m
Incorporated 2021
Share capital NOK 70,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−20,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−26,8 mill kr).

VOLLEBEKK NÆRING B1 AS is registered as a limited company in Oslo, Oslo with organisation number 928884708. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 70,000, divided into 1 shares. The company's stated purpose is: “Eiendomsutvikling i egen regi eller gjennom deltagelse i andre selskaper samt annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −26.8m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −26.8m
Equity
NOK −20.5m

Financial health · 2024

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

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

Who owns VOLLEBEKK NÆRING B1 AS?

OBOS NYE HJEM AS
VOLLEBEKK NÆRING B1 AS
NOK 2.0m rev. · NOK −26.8m profit

VOLLEBEKK NÆRING B1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOLLEBEKK NÆRING B1 AS

Who owns VOLLEBEKK NÆRING B1 AS?

OBOS NYE HJEM AS is the largest registered owner, with 100.0%.

What is the revenue of VOLLEBEKK NÆRING B1 AS?

VOLLEBEKK NÆRING B1 AS had revenue of NOK 2.0m in 2024.

Where is VOLLEBEKK NÆRING B1 AS based?

VOLLEBEKK NÆRING B1 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.