BIZTRAC BETA
Rental and operating of own or leased real estate

RAUMA EIENDOM AS

Org. no. 990012768 Limited company (AS) Rauma Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −379,000
Equity NOK 152,000
Incorporated 2006
Share capital NOK 2.1m

Signals

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

RAUMA EIENDOM AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 990012768. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 2.1m, divided into 2100 shares. The company's stated purpose is: “Eie eiendom, drive virksomhet i hotellbransjen og alt som derved står i forbindelse, herunder eie aksjer eller andeler i tilsvarende selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −379,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −379,000
Equity
NOK 152,000
Est. value
NOK 139,000

Financial health · 2024

Liquidity
13.51
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.5%
Weak
Equity as a share of total capital

Who owns RAUMA EIENDOM AS?

ARNSTEIN DIGERNES
RAUMA EIENDOM AS
NOK 0 rev. · NOK −379,000 profit

RAUMA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAUMA EIENDOM AS

Who owns RAUMA EIENDOM AS?

ARNSTEIN DIGERNES is the largest registered owner, with 100.0%.

What is the revenue of RAUMA EIENDOM AS?

RAUMA EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of RAUMA EIENDOM AS?

Arnstein Digernes is registered as general manager of RAUMA EIENDOM AS.

Where is RAUMA EIENDOM AS based?

RAUMA EIENDOM AS has its business address in Veblungsnes.

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.