BIZTRAC BETA
Operation of freshwater hatcheries

FISTER SMOLT AS

Org. no. 981979583 Limited company (AS) Hjelmeland Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 98.7m
Operating profit NOK 6.7m
Equity NOK 28.1m
Incorporated 2000
Employees 25
Share capital NOK 1.5m

FISTER SMOLT AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 981979583. The business is classified under operation of freshwater hatcheries (NACE 03.222). The company was incorporated in 2000 and has 25 registered employees. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Å drive fiskeoppdrett herunder deltagelse og investering i andre selskap, og alt hva dermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 98.7m in revenue and NOK 6.7m in operating profit.

Key figures · 2025

Revenue
NOK 98.7m
Operating profit
NOK 6.7m
Equity
NOK 28.1m
Est. value
NOK 27.0m

Financial health · 2025

Liquidity
2.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.5%
Good
Equity as a share of total capital

Who owns FISTER SMOLT AS?

PIGGSTEIN AS
FISTER SMOLT AS
NOK 98.7m rev. · NOK 6.7m profit

FISTER SMOLT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FISTER SMOLT AS own?

FISTER SMOLT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FISTER SMOLT AS

Who owns FISTER SMOLT AS?

PIGGSTEIN AS is the largest registered owner, with 100.0%.

What is the revenue of FISTER SMOLT AS?

FISTER SMOLT AS had revenue of NOK 98.7m in 2025.

Who is the general manager of FISTER SMOLT AS?

Nils Viga is registered as general manager of FISTER SMOLT AS.

Where is FISTER SMOLT AS based?

FISTER SMOLT AS has its business address in Fister.

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.