BIZTRAC BETA
Development of building projects

SOLBAKKEN ØVRE VANG AS

Org. no. 918172912 Limited company (AS) Jevnaker Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 351,000
Operating profit NOK −67,000
Equity NOK −763,000
Incorporated 2016
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−763k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−67k kr).

SOLBAKKEN ØVRE VANG AS is registered as a limited company in Jevnaker, Akershus with organisation number 918172912. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling og utleie samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 351,000 in revenue and NOK −67,000 in operating profit.

Key figures · 2024

Revenue
NOK 351,000
Operating profit
NOK −67,000
Equity
NOK −763,000

Financial health · 2024

Liquidity
2.46
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.7%
Weak
Equity as a share of total capital

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

Who owns SOLBAKKEN ØVRE VANG AS?

VOLVAT INDUSTRIER AS
SOLBAKKEN ØVRE VANG AS
NOK 351,000 rev. · NOK −67,000 profit

SOLBAKKEN ØVRE VANG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLBAKKEN ØVRE VANG AS

Who owns SOLBAKKEN ØVRE VANG AS?

VOLVAT INDUSTRIER AS is the largest registered owner, with 75.0%.

What is the revenue of SOLBAKKEN ØVRE VANG AS?

SOLBAKKEN ØVRE VANG AS had revenue of NOK 351,000 in 2024.

Where is SOLBAKKEN ØVRE VANG AS based?

SOLBAKKEN ØVRE VANG AS has its business address in Jevnaker.

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.