BIZTRAC BETA
Uoppgitt

VESTSOL AS

Org. no. 826612282 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −472,000
Equity NOK −7.0m
Incorporated 2021
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−7,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−472k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VESTSOL AS is registered as a limited company in Oslo, Oslo with organisation number 826612282. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom, samt naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −472,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −472,000
Equity
NOK −7.0m

Financial health · 2024

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

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

Who owns VESTSOL AS?

BEVI AS
VESTSOL AS
NOK 0 rev. · NOK −472,000 profit

VESTSOL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTSOL AS

Who owns VESTSOL AS?

BEVI AS is the largest registered owner, with 100.0%.

What is the revenue of VESTSOL AS?

VESTSOL AS had revenue of NOK 0 in 2024.

Who is the general manager of VESTSOL AS?

Rune Solstad is registered as general manager of VESTSOL AS.

Where is VESTSOL AS based?

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