BIZTRAC BETA
Marine fishing

TURI OG NILSEN FISK AS

Org. no. 913589106 Limited company (AS) Nesseby Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 657,000
Operating profit NOK −2,000
Equity NOK 141,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

TURI OG NILSEN FISK AS is registered as a limited company in Nesseby, Finnmark with organisation number 913589106. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive med kyst- og fjordfiske med dertil hørende tilleggstjenester. Selskapet driver også innen reidrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 657,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 657,000
Operating profit
NOK −2,000
Equity
NOK 141,000
Est. value
NOK 423,000

Financial health · 2024

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

Who owns TURI OG NILSEN FISK AS?

JØRGEN TURI
TURI OG NILSEN FISK AS
NOK 657,000 rev. · NOK −2,000 profit

TURI OG NILSEN FISK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TURI OG NILSEN FISK AS

Who owns TURI OG NILSEN FISK AS?

JØRGEN TURI is the largest registered owner, with 51.0%.

What is the revenue of TURI OG NILSEN FISK AS?

TURI OG NILSEN FISK AS had revenue of NOK 657,000 in 2024.

Who is the general manager of TURI OG NILSEN FISK AS?

Jørgen Turi is registered as general manager of TURI OG NILSEN FISK AS.

Where is TURI OG NILSEN FISK AS based?

TURI OG NILSEN FISK AS has its business address in Varangerbotn.

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.