biztrac. BETA
COMPANY REGISTER PROFILE
922796165 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Support activities for fishing and aquaculture

SPORBARHET AS

Org. no. 922796165 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK −2.0m
Equity NOK 8.7m
Incorporated 2019
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).

SPORBARHET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922796165. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2019. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Etablere og drifte et eller flere sporbarhetssystem for laks, med salg av tjenester til kunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK −2.0m in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
▼ −67 %
Operating profit
NOK −2.0m
▼ −532 %
Equity
NOK 8.7m
▼ −18 %
Est. value
NOK 8.0m

Financial health · 2025

Liquidity
9.69
Very good
Current assets ÷ current liabilities
Profitability
-13.0%
Not satisfactory
Return on total assets
Solidity
89.7%
Very good
Equity as a share of total capital

Who owns SPORBARHET AS?

SPORBARHET AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPORBARHET AS

Who owns SPORBARHET AS?

MOWI HOLDING AS is the largest registered owner, with 43.4%.

What is the revenue of SPORBARHET AS?

SPORBARHET AS had revenue of NOK 6.9m in 2025.

Who is the general manager of SPORBARHET AS?

Helge Klungland is registered as general manager of SPORBARHET AS.

Where is SPORBARHET AS based?

SPORBARHET AS has its business address in Trondheim.

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.