BIZTRAC BETA
Development of building projects

VOLDA PRESTEGATA 35 AS

Org. no. 933029336 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 3.2m
Equity NOK 18.5m
Incorporated 2024
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.

VOLDA PRESTEGATA 35 AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 933029336. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling, drift,forvaltning og salg av fast eiendom samt det som står i forhold til dette, herunder også deltakelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 3.2m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 3.2m
Equity
NOK 18.5m
Est. value
NOK 19.8m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
59.9%
Very good
Equity as a share of total capital

Who owns VOLDA PRESTEGATA 35 AS?

COM EIENDOM AS
VOLDA PRESTEGATA 35 AS
NOK 4.4m rev. · NOK 3.2m profit

VOLDA PRESTEGATA 35 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOLDA PRESTEGATA 35 AS

Who owns VOLDA PRESTEGATA 35 AS?

COM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of VOLDA PRESTEGATA 35 AS?

VOLDA PRESTEGATA 35 AS had revenue of NOK 4.4m in 2025.

Where is VOLDA PRESTEGATA 35 AS based?

VOLDA PRESTEGATA 35 AS has its business address in Ålesund.

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.