biztrac. BETA
COMPANY REGISTER PROFILE
958954379 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other machinery and equipment

FISHTECH AS

Org. no. 958954379 Limited company (AS) Vestby Incorporated 1990 Active
Revenue 2025 NOK 28.8m
Operating profit NOK 2.6m
Equity NOK 4.2m
Incorporated 1990
Employees 5
Share capital NOK 100,000

FISHTECH AS is registered as a limited company in Vestby, Akershus with organisation number 958954379. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1990 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive salg av teknisk utstyr til fiskeoppdretts- næringen samt virksomhet som måtte stå i forbind- else med dette og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.8m in revenue and NOK 2.6m in operating profit.

Former names: STERNER FISHFARMING TECHNOLOGY AS, STERNER FISH TECH AS

Key figures · 2025

Revenue
NOK 28.8m
▲ +12 %
Operating profit
NOK 2.6m
▲ +27 %
Equity
NOK 4.2m
▲ +14 %
Est. value
NOK 11.2m

Financial health · 2025

Liquidity
2.43
Very good
Current assets ÷ current liabilities
Profitability
37.1%
Very good
Return on total assets
Solidity
61.3%
Very good
Equity as a share of total capital

Who owns FISHTECH AS?

FISHTECH AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FISHTECH AS

Who owns FISHTECH AS?

FISHTECH HOLDING AS is the largest registered owner, with 75.0%.

What is the revenue of FISHTECH AS?

FISHTECH AS had revenue of NOK 28.8m in 2025.

Who is the general manager of FISHTECH AS?

Norvald Soleng is registered as general manager of FISHTECH AS.

Where is FISHTECH AS based?

FISHTECH AS has its business address in Vestby.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.