BIZTRAC BETA
Rental and operating of own or leased real estate

BØRVÅGEN AS

Org. no. 933406032 Limited company (AS) Vågan Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 143,000
Operating profit NOK −121,000
Equity NOK 9.5m
Incorporated 2024
Share capital NOK 80,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−121k kr).

BØRVÅGEN AS is registered as a limited company in Vågan, Nordland with organisation number 933406032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 80,000, divided into 300 shares. The company's stated purpose is: “Investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 143,000 in revenue and NOK −121,000 in operating profit.

Key figures · 2024

Revenue
NOK 143,000
Operating profit
NOK −121,000
Equity
NOK 9.5m
Est. value
NOK 8.8m

Financial health · 2024

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

Who owns BØRVÅGEN AS?

TORUNN KVALVIK
BØRVÅGEN AS
NOK 143,000 rev. · NOK −121,000 profit

BØRVÅGEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BØRVÅGEN AS own?

BØRVÅGEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BØRVÅGEN AS

Who owns BØRVÅGEN AS?

TORUNN KVALVIK is the largest registered owner, with 50.0%.

What is the revenue of BØRVÅGEN AS?

BØRVÅGEN AS had revenue of NOK 143,000 in 2024.

Where is BØRVÅGEN AS based?

BØRVÅGEN 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.