BIZTRAC BETA
Retail sale of fish, crustaceans and molluscs

AR-SJØMAT AS

Org. no. 931084135 Limited company (AS) Averøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −390,000
Equity NOK 9,000
Incorporated 2023
Employees 5
Share capital NOK 895,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−390k kr).

AR-SJØMAT AS is registered as a limited company in Averøy, Møre og Romsdal with organisation number 931084135. The business is classified under retail sale of fish, crustaceans and molluscs (NACE 47.230). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 895,000, divided into 30 shares. The company's stated purpose is: “Videresalg av frossenfisk/reker/fiskemat.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −390,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK −390,000
Equity
NOK 9,000
Est. value
NOK 761,000

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AR-SJØMAT AS?

RONNY FAGERLUND LILLEROVDE
AR-SJØMAT AS
NOK 2.7m rev. · NOK −390,000 profit

AR-SJØMAT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AR-SJØMAT AS

Who owns AR-SJØMAT AS?

RONNY FAGERLUND LILLEROVDE is the largest registered owner, with 50.0%.

What is the revenue of AR-SJØMAT AS?

AR-SJØMAT AS had revenue of NOK 2.7m in 2025.

Who is the general manager of AR-SJØMAT AS?

Ronny Fagerlund Lillerovde is registered as general manager of AR-SJØMAT AS.

Where is AR-SJØMAT AS based?

AR-SJØMAT AS has its business address in Averøy.

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.