BIZTRAC BETA
COMPANY REGISTER PROFILE
933697703 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

LOFOTVÆR AS

Org. no. 933697703 Limited company (AS) Vågan Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 1.0m
Incorporated 2024
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

LOFOTVÆR AS is registered as a limited company in Vågan, Nordland with organisation number 933697703. 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 1.1m, divided into 1065 shares. The company's stated purpose is: “Utvikling og utleie av eiendom og annet som faller naturlig innenfor dette.”.

Key figures · 2025

Operating profit
NOK −12,000
▼ −30 %
Equity
NOK 1.0m
▼ −1 %
Est. value
NOK 944,000

Financial health · 2025

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

Who owns LOFOTVÆR AS?

LOFOTVÆR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOFOTVÆR AS

Who owns LOFOTVÆR AS?

FELVIK HOLDING AS is the largest registered owner, with 33.3%.

Where is LOFOTVÆR AS based?

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

Property

Business address Meyerbakken 22, 8300 Svolvær
Cadastral unit 1865-18/1256/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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