BIZTRAC BETA
Marine fishing

RAMOEN AS

Org. no. 920767443 Limited company (AS) Ørsta Incorporated 1937 Active
Ownership graph ↗
Revenue 2024 NOK 249.9m
Operating profit NOK 45.4m
Equity NOK 175.3m
Incorporated 1937
Employees 8
Share capital NOK 3.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RAMOEN AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 920767443. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 1937 and has 8 registered employees. Registered share capital is NOK 3.0m, divided into 2950 shares. The company's stated purpose is: “Drift av F/T "Ramoen".”. The most recent filed accounts, for the 2024 financial year, show NOK 249.9m in revenue and NOK 45.4m in operating profit.

Key figures · 2024

Revenue
NOK 249.9m
Operating profit
NOK 45.4m
Equity
NOK 175.3m
Est. value
NOK 199.2m

Financial health · 2024

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

Who owns RAMOEN AS?

EROS AS
RAMOEN AS
NOK 249.9m rev. · NOK 45.4m profit

RAMOEN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does RAMOEN AS own?

RAMOEN AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

RAMOEN AS er morselskap for 1 datterselskap:

Frequently asked questions about RAMOEN AS

Who owns RAMOEN AS?

EROS AS is the largest registered owner, with 65.0%.

What is the revenue of RAMOEN AS?

RAMOEN AS had revenue of NOK 249.9m in 2024.

Who is the general manager of RAMOEN AS?

Per Magne Eggesbø is registered as general manager of RAMOEN AS.

Where is RAMOEN AS based?

RAMOEN AS has its business address in Vartdal.

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.