BIZTRAC BETA
Operation of marine hatcheries

TYRIFJORD FISK AS

Org. no. 998154545 Limited company (AS) Modum Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 104,000
Operating profit NOK −21,000
Equity NOK 531,000
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

TYRIFJORD FISK AS is registered as a limited company in Modum, Buskerud with organisation number 998154545. The business is classified under operation of marine hatcheries (NACE 03.212). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppdrett/salg av settefisk og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 104,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 104,000
Operating profit
NOK −21,000
Equity
NOK 531,000
Est. value
NOK 257,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
62.2%
Very good
Equity as a share of total capital

Who owns TYRIFJORD FISK AS?

KNUT EINAR DØLVEN SØRENSEN
TYRIFJORD FISK AS
NOK 104,000 rev. · NOK −21,000 profit

TYRIFJORD FISK AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about TYRIFJORD FISK AS

Who owns TYRIFJORD FISK AS?

KNUT EINAR DØLVEN SØRENSEN is the largest registered owner, with 89.0%.

What is the revenue of TYRIFJORD FISK AS?

TYRIFJORD FISK AS had revenue of NOK 104,000 in 2025.

Who is the general manager of TYRIFJORD FISK AS?

Knut Einar Dølven Sørensen is registered as general manager of TYRIFJORD FISK AS.

Where is TYRIFJORD FISK AS based?

TYRIFJORD FISK AS has its business address in Vikersund.

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.