BIZTRAC BETA
Retail sale of other new goods

MÅLØY OPPLEVELSE AS

Org. no. 931496298 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −154,000
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−154k kr).

MÅLØY OPPLEVELSE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931496298. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Handel innen bransjen suvenir- og gaveartikler m.v., samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −154,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −154,000
Equity
NOK 30,000
Est. value
NOK 332,000

Financial health · 2024

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

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

Who owns MÅLØY OPPLEVELSE AS?

NORD SUVENIR AS
MÅLØY OPPLEVELSE AS
NOK 1.2m rev. · NOK −154,000 profit

MÅLØY OPPLEVELSE AS has 2 registered shareholders:

All shareholders and roles →

Group structure

MÅLØY OPPLEVELSE AS er morselskap for 2 datterselskaper:

Frequently asked questions about MÅLØY OPPLEVELSE AS

Who owns MÅLØY OPPLEVELSE AS?

NORD SUVENIR AS is the largest registered owner, with 50.0%.

What is the revenue of MÅLØY OPPLEVELSE AS?

MÅLØY OPPLEVELSE AS had revenue of NOK 1.2m in 2024.

Where is MÅLØY OPPLEVELSE AS based?

MÅLØY OPPLEVELSE AS has its business address in Ålesund.

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.