biztrac. BETA
COMPANY REGISTER PROFILE
831034572 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of fish, crustaceans and molluscs

FISKERUTA AS

Org. no. 831034572 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 161.3m
Operating profit NOK 13.0m
Equity NOK 12.2m
Incorporated 2023
Employees 71
Share capital NOK 120,000

Signals

1 flags
  • Nylig endring 2026-05-31 Adresseendring registrert 2026-05-31.

FISKERUTA AS is registered as a limited company in Drammen, Buskerud with organisation number 831034572. The business is classified under retail sale of fish, crustaceans and molluscs (NACE 47.230). The company was incorporated in 2023 and has 71 registered employees. Registered share capital is NOK 120,000, divided into 30000 shares. The company's stated purpose is: “Omsetning av fisk til forbrukere samt deltagelse i andre økonomiske foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 161.3m in revenue and NOK 13.0m in operating profit.

Key figures · 2025

Revenue
NOK 161.3m
▲ +28 %
Operating profit
NOK 13.0m
▲ +60 %
Equity
NOK 12.2m
▲ +89 %
Est. value
NOK 47.0m

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
42.0%
Very good
Return on total assets
Solidity
32.1%
Good
Equity as a share of total capital

Who owns FISKERUTA AS?

FISKERUTA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FISKERUTA AS

Who owns FISKERUTA AS?

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

What is the revenue of FISKERUTA AS?

FISKERUTA AS had revenue of NOK 161.3m in 2025.

Who is the general manager of FISKERUTA AS?

Pål Raymond Sømme is registered as general manager of FISKERUTA AS.

Where is FISKERUTA AS based?

FISKERUTA AS has its business address in Mjøndalen.

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.