BIZTRAC BETA
Construction of residential and non-residential buildings

RAUMA BYGG AS

Org. no. 828303422 Limited company (AS) Rauma Incorporated 1976 Active
Ownership graph ↗
Revenue 2024 NOK 720,000
Operating profit NOK 536,000
Equity NOK 2.1m
Incorporated 1976
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RAUMA BYGG AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 828303422. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1976. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Eie og drive faste eiendommer, samt delta i dermed beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 720,000 in revenue and NOK 536,000 in operating profit.

Key figures · 2024

Revenue
NOK 720,000
Operating profit
NOK 536,000
Equity
NOK 2.1m
Est. value
NOK 2.7m

Financial health · 2024

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.8%
Very good
Equity as a share of total capital

Who owns RAUMA BYGG AS?

VEIDEKKE ENTREPRENØR AS
RAUMA BYGG AS
NOK 720,000 rev. · NOK 536,000 profit

RAUMA BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAUMA BYGG AS

Who owns RAUMA BYGG AS?

VEIDEKKE ENTREPRENØR AS is the largest registered owner, with 100.0%.

What is the revenue of RAUMA BYGG AS?

RAUMA BYGG AS had revenue of NOK 720,000 in 2024.

Who is the general manager of RAUMA BYGG AS?

Stig Ivar Mork is registered as general manager of RAUMA BYGG AS.

Where is RAUMA BYGG AS based?

RAUMA BYGG AS has its business address in Åndalsnes.

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.