BIZTRAC BETA
Rental and leasing of cars and light motor vehicles

LOFOTEN VANLIFE AS

Org. no. 926357573 Limited company (AS) Vågan Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 544,000
Equity NOK −86,000
Incorporated 2020
Share capital NOK 324,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−86k kr).

LOFOTEN VANLIFE AS is registered as a limited company in Vågan, Nordland with organisation number 926357573. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2020. Registered share capital is NOK 324,000, divided into 270000 shares. The company's stated purpose is: “Utleie av campingbiler.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 544,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 544,000
Equity
NOK −86,000
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.3%
Weak
Equity as a share of total capital

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

Who owns LOFOTEN VANLIFE AS?

KARSTEN ANDREASSEN ELLINGSEN
LOFOTEN VANLIFE AS
NOK 4.0m rev. · NOK 544,000 profit

LOFOTEN VANLIFE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOFOTEN VANLIFE AS

Who owns LOFOTEN VANLIFE AS?

KARSTEN ANDREASSEN ELLINGSEN is the largest registered owner, with 67.0%.

What is the revenue of LOFOTEN VANLIFE AS?

LOFOTEN VANLIFE AS had revenue of NOK 4.0m in 2025.

Who is the general manager of LOFOTEN VANLIFE AS?

Karsten Andreassen Ellingsen is registered as general manager of LOFOTEN VANLIFE AS.

Where is LOFOTEN VANLIFE AS based?

LOFOTEN VANLIFE 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.