BIZTRAC BETA
Development of building projects

ROALDHUS AS

Org. no. 934454421 Limited company (AS) Giske Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 12.4m
Operating profit NOK −841,000
Equity NOK 5.0m
Incorporated 1983
Share capital NOK 700,000

Signals

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

ROALDHUS AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 934454421. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1983. Registered share capital is NOK 700,000, divided into 700 shares. The company's stated purpose is: “Bygge- og anleggsvirksomhet, samt handel, og hva dermed står i forbindelse. Selskapet skal gjennom aksjeinnskudd eller på annen måte også kunne delta i eller være interessert i andre selskap med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.4m in revenue and NOK −841,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.4m
Operating profit
NOK −841,000
Equity
NOK 5.0m
Est. value
NOK 22.0m

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.8%
Good
Equity as a share of total capital

Who owns ROALDHUS AS?

ROALD EIGEDOM AS
ROALDHUS AS
NOK 12.4m rev. · NOK −841,000 profit

ROALDHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROALDHUS AS

Who owns ROALDHUS AS?

ROALD EIGEDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ROALDHUS AS?

ROALDHUS AS had revenue of NOK 12.4m in 2024.

Who is the general manager of ROALDHUS AS?

Sondre Olai Roald is registered as general manager of ROALDHUS AS.

Where is ROALDHUS AS based?

ROALDHUS AS has its business address in Vigra.

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.