BIZTRAC BETA
Restaurant activities

ANITAS SJØMAT AS

Org. no. 998554624 Limited company (AS) Moskenes Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 31.2m
Operating profit NOK 3.7m
Equity NOK 14.7m
Incorporated 2012
Employees 41
Share capital NOK 1.0m

ANITAS SJØMAT AS is registered as a limited company in Moskenes, Nordland with organisation number 998554624. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 41 registered employees. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Kjøp, produksjon og salg av fiskeprodukter og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 31.2m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 31.2m
Operating profit
NOK 3.7m
Equity
NOK 14.7m
Est. value
NOK 21.7m

Financial health · 2024

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

Who owns ANITAS SJØMAT AS?

ANITA OLETTE FIGENSCHOU GYLSETH
ANITAS SJØMAT AS
NOK 31.2m rev. · NOK 3.7m profit

ANITAS SJØMAT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ANITAS SJØMAT AS own?

ANITAS SJØMAT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ANITAS SJØMAT AS

Who owns ANITAS SJØMAT AS?

ANITA OLETTE FIGENSCHOU GYLSETH is the largest registered owner, with 100.0%.

What is the revenue of ANITAS SJØMAT AS?

ANITAS SJØMAT AS had revenue of NOK 31.2m in 2024.

Who is the general manager of ANITAS SJØMAT AS?

Anita Olette Figenschou Gylseth is registered as general manager of ANITAS SJØMAT AS.

Where is ANITAS SJØMAT AS based?

ANITAS SJØMAT AS has its business address in Reine.

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.