BIZTRAC BETA
Marine fishing

MORO KYSTFISKE AS

Org. no. 919554010 Limited company (AS) Meløy Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 22,000
Equity NOK 1.1m
Incorporated 2017
Employees 9
Share capital NOK 4.1m

MORO KYSTFISKE AS is registered as a limited company in Meløy, Nordland with organisation number 919554010. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2017 and has 9 registered employees. Registered share capital is NOK 4.1m, divided into 4080000 shares. The company's stated purpose is: “Selskapet skal drive med fiske og fangst, kjøp og salg av båter og kvoter, samt virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 22,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 22,000
Equity
NOK 1.1m
Est. value
NOK 569,000

Financial health · 2024

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

Who owns MORO KYSTFISKE AS?

JOHAN R AS
MORO KYSTFISKE AS
NOK 4.9m rev. · NOK 22,000 profit

MORO KYSTFISKE AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MORO KYSTFISKE AS own?

MORO KYSTFISKE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MORO KYSTFISKE AS

Who owns MORO KYSTFISKE AS?

JOHAN R AS is the largest registered owner, with 34.0%.

What is the revenue of MORO KYSTFISKE AS?

MORO KYSTFISKE AS had revenue of NOK 4.9m in 2024.

Who is the general manager of MORO KYSTFISKE AS?

Morten Johan Røshagen is registered as general manager of MORO KYSTFISKE AS.

Where is MORO KYSTFISKE AS based?

MORO KYSTFISKE AS has its business address in Reipå.

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.