BIZTRAC BETA
Development of building projects

VAAGSBYEN BOLIG AS

Org. no. 998001323 Limited company (AS) Stavanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 51,000
Operating profit NOK −92,000
Equity NOK 2.9m
Incorporated 2012
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−92k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VAAGSBYEN BOLIG AS is registered as a limited company in Stavanger, Rogaland with organisation number 998001323. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 51,000 in revenue and NOK −92,000 in operating profit.

Key figures · 2024

Revenue
NOK 51,000
Operating profit
NOK −92,000
Equity
NOK 2.9m
Est. value
NOK 2.7m

Financial health · 2024

Liquidity
7.13
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.1%
Good
Equity as a share of total capital

Who owns VAAGSBYEN BOLIG AS?

SOLON SØRVEST AS
VAAGSBYEN BOLIG AS
NOK 51,000 rev. · NOK −92,000 profit

VAAGSBYEN BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VAAGSBYEN BOLIG AS

Who owns VAAGSBYEN BOLIG AS?

SOLON SØRVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VAAGSBYEN BOLIG AS?

VAAGSBYEN BOLIG AS had revenue of NOK 51,000 in 2024.

Where is VAAGSBYEN BOLIG AS based?

VAAGSBYEN BOLIG AS has its business address in Stavanger.

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.