BIZTRAC BETA
Marine fishing

JOKER AS

Org. no. 983043291 Limited company (AS) Værøy Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 96,000
Operating profit NOK −257,000
Equity NOK −1.1m
Incorporated 2001
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−257k kr).

JOKER AS is registered as a limited company in Værøy, Nordland with organisation number 983043291. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Havfiske, samt hva som naturlig hører inn under dette, herunder delta i selskap med samme tilknytning. Fiske etter torskefisk vil være det viktigste fiske.”. The most recent filed accounts, for the 2025 financial year, show NOK 96,000 in revenue and NOK −257,000 in operating profit.

Key figures · 2025

Revenue
NOK 96,000
Operating profit
NOK −257,000
Equity
NOK −1.1m

Financial health · 2024

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

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

Who owns JOKER AS?

Fritz Ottar Olsen
JOKER AS
NOK 96,000 rev. · NOK −257,000 profit

JOKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOKER AS

Who owns JOKER AS?

Fritz Ottar Olsen is the largest registered owner, with 100.0%.

What is the revenue of JOKER AS?

JOKER AS had revenue of NOK 96,000 in 2025.

Who is the general manager of JOKER AS?

Fritz Ottar Olsen is registered as general manager of JOKER AS.

Where is JOKER AS based?

JOKER AS has its business address in Værøy.

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.