biztrac. BETA
COMPANY REGISTER PROFILE
933220281 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Camping grounds and recreational vehicle parks

RAPUMA AS

Org. no. 933220281 Limited company (AS) Averøy Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −75,000
Equity NOK 1.4m
Incorporated 2024
Share capital NOK 1.7m

Signals

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

RAPUMA AS is registered as a limited company in Averøy, Møre og Romsdal with organisation number 933220281. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2024. Registered share capital is NOK 1.7m, divided into 1680000 shares. The company's stated purpose is: “Utleie av egen eller leid fast eiendom, driftsmidler, m.v., hovedsakelig i sammenheng med turisme, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −75,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +14 %
Operating profit
NOK −75,000
▼ −112 %
Equity
NOK 1.4m
▼ −24 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
4.32
Very good
Current assets ÷ current liabilities
Profitability
-1.0%
Not satisfactory
Return on total assets
Solidity
21.9%
Good
Equity as a share of total capital

Who owns RAPUMA AS?

RAPUMA AS
NOK 1.9m rev. · NOK −75,000 profit

RAPUMA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAPUMA AS

Who owns RAPUMA AS?

Mario Uebe is the largest registered owner, with 50.0%.

What is the revenue of RAPUMA AS?

RAPUMA AS had revenue of NOK 1.9m in 2025.

Who is the general manager of RAPUMA AS?

Mario Uebe is registered as general manager of RAPUMA AS.

Where is RAPUMA AS based?

RAPUMA 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.