BIZTRAC BETA
Rental and operating of own or leased real estate

AS VAAGEN 35

Org. no. 891946902 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 35,000
Operating profit NOK 33,000
Equity NOK 52,000
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AS VAAGEN 35 is registered as a limited company in Stavanger, Rogaland with organisation number 891946902. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å være en industriell investor ved å utøve aktivt eierskap i andre selskaper, kjøp og salg av fast eiendom, utleie av fast eiendom og ellers hva som heri står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 35,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2024

Revenue
NOK 35,000
Operating profit
NOK 33,000
Equity
NOK 52,000
Est. value
NOK 93,000

Financial health · 2024

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

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

Who owns AS VAAGEN 35?

AS FJELDE
AS VAAGEN 35
NOK 35,000 rev. · NOK 33,000 profit

AS VAAGEN 35 has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AS VAAGEN 35

Who owns AS VAAGEN 35?

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

What is the revenue of AS VAAGEN 35?

AS VAAGEN 35 had revenue of NOK 35,000 in 2024.

Where is AS VAAGEN 35 based?

AS VAAGEN 35 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.