BIZTRAC BETA
Construction of other civil engineering projects n.e.c.

MØREAKSEN AS

Org. no. 942390742 Limited company (AS) Molde Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 425,000
Equity NOK 115,000
Incorporated 1986
Share capital NOK 7.4m

MØREAKSEN AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 942390742. The business is classified under construction of other civil engineering projects n.e.c. (NACE 42.990). The company was incorporated in 1986. Registered share capital is NOK 7.4m, divided into 74025 shares. The company's stated purpose is: “Å realisere eit fergefritt samband over Romsdalsfjorden, som samtidig knyter Aukra kommune og tidlegare Midsund kommune til fastlandet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 425,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 425,000
Equity
NOK 115,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns MØREAKSEN AS?

MOLDE KOMMUNE
MØREAKSEN AS
NOK 1.6m rev. · NOK 425,000 profit

MØREAKSEN AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does MØREAKSEN AS own?

MØREAKSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MØREAKSEN AS

Who owns MØREAKSEN AS?

MOLDE KOMMUNE is the largest registered owner, with 33.3%.

What is the revenue of MØREAKSEN AS?

MØREAKSEN AS had revenue of NOK 1.6m in 2024.

Who is the general manager of MØREAKSEN AS?

Roald Torstein Fiksdal is registered as general manager of MØREAKSEN AS.

Where is MØREAKSEN AS based?

MØREAKSEN AS has its business address in Molde.

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.