BIZTRAC BETA
Construction of residential and non-residential buildings

R&R BYGG AS

Org. no. 923712860 Limited company (AS) Vestvågøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK −228,000
Equity NOK 1.5m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−228k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

R&R BYGG AS is registered as a limited company in Vestvågøy, Nordland with organisation number 923712860. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrervirksomhet og alt som faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK −228,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK −228,000
Equity
NOK 1.5m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns R&R BYGG AS?

R&R EIENDOM AS
R&R BYGG AS
NOK 4.2m rev. · NOK −228,000 profit

R&R BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R&R BYGG AS

Who owns R&R BYGG AS?

R&R EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of R&R BYGG AS?

R&R BYGG AS had revenue of NOK 4.2m in 2025.

Who is the general manager of R&R BYGG AS?

Roy Andre Ingebrigtsen is registered as general manager of R&R BYGG AS.

Where is R&R BYGG AS based?

R&R BYGG AS has its business address in Valberg.

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.