BIZTRAC BETA
Rental and operating of own or leased real estate

VILLA SVOLVÆR AS

Org. no. 925790419 Limited company (AS) Vågan Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 260,000
Equity NOK 53,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

VILLA SVOLVÆR AS is registered as a limited company in Vågan, Nordland with organisation number 925790419. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive investering, utvikling og forvaltning av næringseiendom, samt engasjere seg i øvrig virksomhet som selskapet måtte finne økonomisk formålstjenlig.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 260,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 260,000
Equity
NOK 53,000
Est. value
NOK 464,000

Financial health · 2024

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

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

Who owns VILLA SVOLVÆR AS?

BHKL HOLDING AS
VILLA SVOLVÆR AS
NOK 1.5m rev. · NOK 260,000 profit

VILLA SVOLVÆR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VILLA SVOLVÆR AS

Who owns VILLA SVOLVÆR AS?

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

What is the revenue of VILLA SVOLVÆR AS?

VILLA SVOLVÆR AS had revenue of NOK 1.5m in 2024.

Where is VILLA SVOLVÆR AS based?

VILLA SVOLVÆR 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 15.06.2026.

Report a problem

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