BIZTRAC BETA
Marine fishing

LOFOTVÆRING II AS

Org. no. 917788251 Limited company (AS) Vågan Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 16.2m
Operating profit NOK 346,000
Equity NOK 12.7m
Incorporated 2016
Share capital NOK 870,000

Signals

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

LOFOTVÆRING II AS is registered as a limited company in Vågan, Nordland with organisation number 917788251. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2016. Registered share capital is NOK 870,000, divided into 8700 shares. The company's stated purpose is: “Drive fiske og fangst, samt annen virksomhet som naturlig faller inn under dette, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.2m in revenue and NOK 346,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.2m
Operating profit
NOK 346,000
Equity
NOK 12.7m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns LOFOTVÆRING II AS?

INDAHL STAR AS
LOFOTVÆRING II AS
NOK 16.2m rev. · NOK 346,000 profit

LOFOTVÆRING II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOFOTVÆRING II AS

Who owns LOFOTVÆRING II AS?

INDAHL STAR AS is the largest registered owner, with 100.0%.

What is the revenue of LOFOTVÆRING II AS?

LOFOTVÆRING II AS had revenue of NOK 16.2m in 2024.

Who is the general manager of LOFOTVÆRING II AS?

Lars Kristian Indahl is registered as general manager of LOFOTVÆRING II AS.

Where is LOFOTVÆRING II AS based?

LOFOTVÆRING II 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.