BIZTRAC BETA
Marine fishing

JOHNNYS KYSTFISKE AS

Org. no. 936231071 Limited company (AS) Narvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4,000
Operating profit NOK −97,000
Equity NOK 513,000
Incorporated 2025
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−97k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-19.

JOHNNYS KYSTFISKE AS is registered as a limited company in Narvik, Nordland with organisation number 936231071. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Kommersielt fiske etter torsk, hyse, sei og pelagiske arter med garn, snurrevad, not o.l. Selskapet skal også drive teinefangst av hummer og krabbe. Selskapet kan også delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4,000 in revenue and NOK −97,000 in operating profit.

Key figures · 2025

Revenue
NOK 4,000
Operating profit
NOK −97,000
Equity
NOK 513,000
Est. value
NOK 488,000

Financial health · 2025

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

Who owns JOHNNYS KYSTFISKE AS?

JOHNNY RASMUSSEN
JOHNNYS KYSTFISKE AS
NOK 4,000 rev. · NOK −97,000 profit

JOHNNYS KYSTFISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOHNNYS KYSTFISKE AS

Who owns JOHNNYS KYSTFISKE AS?

JOHNNY RASMUSSEN is the largest registered owner, with 100.0%.

What is the revenue of JOHNNYS KYSTFISKE AS?

JOHNNYS KYSTFISKE AS had revenue of NOK 4,000 in 2025.

Where is JOHNNYS KYSTFISKE AS based?

JOHNNYS KYSTFISKE AS has its business address in Beisfjord.

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.