BIZTRAC BETA
Construction of residential and non-residential buildings

R.BYGG HOLDING AS

Org. no. 921583834 Limited company (AS) Indre Østfold Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −62,000
Equity NOK 2.9m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).

R.BYGG HOLDING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 921583834. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter å investere i aksjer, verdipapirer, fast eiendom og andre formuesverdier av hvilken som helst art, og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −62,000
Equity
NOK 2.9m
Est. value
NOK 12.6m

Financial health · 2025

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

Who owns R.BYGG HOLDING AS?

R.S. HOLDING AS
R.BYGG HOLDING AS
· NOK −62,000 profit

R.BYGG HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does R.BYGG HOLDING AS own?

R.BYGG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about R.BYGG HOLDING AS

Who owns R.BYGG HOLDING AS?

R.S. HOLDING AS is the largest registered owner, with 70.0%.

Who is the general manager of R.BYGG HOLDING AS?

Svein Raknerud is registered as general manager of R.BYGG HOLDING AS.

Where is R.BYGG HOLDING AS based?

R.BYGG HOLDING AS has its business address in Trøgstad.

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.