BIZTRAC BETA
Construction of residential and non-residential buildings

ROALDSAND EIENDOMS RENOVERING AS

Org. no. 928960420 Limited company (AS) Ålesund Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 103,000
Operating profit NOK 50,000
Equity NOK 40,000
Incorporated 2022
Share capital NOK 80,000

ROALDSAND EIENDOMS RENOVERING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 928960420. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 80,000, divided into 100 shares. The company's stated purpose is: “Bygging og rehabilitering av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 103,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2025

Revenue
NOK 103,000
Operating profit
NOK 50,000
Equity
NOK 40,000
Est. value
NOK 158,000

Financial health · 2025

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.4%
Weak
Equity as a share of total capital

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

Who owns ROALDSAND EIENDOMS RENOVERING AS?

No shareholders are registered for ROALDSAND EIENDOMS RENOVERING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ROALDSAND EIENDOMS RENOVERING AS

What is the revenue of ROALDSAND EIENDOMS RENOVERING AS?

ROALDSAND EIENDOMS RENOVERING AS had revenue of NOK 103,000 in 2025.

Who is the general manager of ROALDSAND EIENDOMS RENOVERING AS?

Patrick Rødal Roaldsand is registered as general manager of ROALDSAND EIENDOMS RENOVERING AS.

Where is ROALDSAND EIENDOMS RENOVERING AS based?

ROALDSAND EIENDOMS RENOVERING 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.