BIZTRAC BETA
Marine fishing

LYSVOLD KYSTFISKE AS

Org. no. 831319712 Limited company (AS) Vågan Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 218,000
Operating profit NOK −58,000
Equity NOK −119,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−119k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−58k kr).

LYSVOLD KYSTFISKE AS is registered as a limited company in Vågan, Nordland with organisation number 831319712. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Fiske.”. The most recent filed accounts, for the 2024 financial year, show NOK 218,000 in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 218,000
Operating profit
NOK −58,000
Equity
NOK −119,000

Financial health · 2024

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

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

Who owns LYSVOLD KYSTFISKE AS?

KARSTEIN JOHAN LYSVOLD
LYSVOLD KYSTFISKE AS
NOK 218,000 rev. · NOK −58,000 profit

LYSVOLD KYSTFISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYSVOLD KYSTFISKE AS

Who owns LYSVOLD KYSTFISKE AS?

KARSTEIN JOHAN LYSVOLD is the largest registered owner, with 100.0%.

What is the revenue of LYSVOLD KYSTFISKE AS?

LYSVOLD KYSTFISKE AS had revenue of NOK 218,000 in 2024.

Who is the general manager of LYSVOLD KYSTFISKE AS?

Karstein Johan Lysvold is registered as general manager of LYSVOLD KYSTFISKE AS.

Where is LYSVOLD KYSTFISKE AS based?

LYSVOLD KYSTFISKE 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.