biztrac. BETA
COMPANY REGISTER PROFILE
925408441 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SVOLVÆR PARK AS

Org. no. 925408441 Limited company (AS) Vågan Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK −19,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

SVOLVÆR PARK AS is registered as a limited company in Vågan, Nordland with organisation number 925408441. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, forvaltning og utleie av fast eiendom samt det som står i forbindelse hermed.”.

Key figures · 2025

Operating profit
NOK −8,000
▲ +31 %
Equity
NOK −19,000
▼ −46 %

Financial health · 2025

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
-21.4%
Not satisfactory
Return on total assets
Solidity
-60.4%
Weak
Equity as a share of total capital

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

Who owns SVOLVÆR PARK AS?

SVOLVÆR PARK AS
· NOK −8,000 profit

SVOLVÆR PARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVOLVÆR PARK AS

Who owns SVOLVÆR PARK AS?

EBB HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of SVOLVÆR PARK AS?

Erik Berg Blomstrand is registered as general manager of SVOLVÆR PARK AS.

Where is SVOLVÆR PARK AS based?

SVOLVÆR PARK AS has its business address in Svolvær.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.