biztrac. BETA
COMPANY REGISTER PROFILE
981971388 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freezing and further processing of fish, crustaceans and molluscs

MIKALS LAKS AS

Org. no. 981971388 Limited company (AS) Hjelmeland Incorporated 2000 Active
Revenue 2025 NOK 11.5m
Operating profit NOK 586,000
Equity NOK 3.5m
Incorporated 2000
Share capital NOK 2.5m

MIKALS LAKS AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 981971388. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 2000. Registered share capital is NOK 2.5m, divided into 2500 shares. The company's stated purpose is: “Videreforedle sjømat i egen regi eller i samarbeid med andre.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.5m in revenue and NOK 586,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.5m
▲ +8 %
Operating profit
NOK 586,000
▲ +352 %
Equity
NOK 3.5m
▲ +15 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
2.08
Very good
Current assets ÷ current liabilities
Profitability
11.6%
Good
Return on total assets
Solidity
64.9%
Very good
Equity as a share of total capital

Who owns MIKALS LAKS AS?

MIKALS LAKS AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MIKALS LAKS AS own?

MIKALS LAKS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MIKALS LAKS AS

Who owns MIKALS LAKS AS?

VIGA FORVALTNING AS is the largest registered owner, with 50.0%.

What is the revenue of MIKALS LAKS AS?

MIKALS LAKS AS had revenue of NOK 11.5m in 2025.

Who is the general manager of MIKALS LAKS AS?

Maren Fossaa Viga is registered as general manager of MIKALS LAKS AS.

Where is MIKALS LAKS AS based?

MIKALS LAKS AS has its business address in Skiftun.

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.