BIZTRAC BETA
Construction of residential and non-residential buildings

RE-BYGG AS

Org. no. 951962449 Limited company (AS) Gloppen Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 30.2m
Operating profit NOK 1.0m
Equity NOK 4.7m
Incorporated 1989
Employees 13
Share capital NOK 148,000

Signals

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

RE-BYGG AS is registered as a limited company in Gloppen, Vestland with organisation number 951962449. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1989 and has 13 registered employees. Registered share capital is NOK 148,000, divided into 50 shares. The company's stated purpose is: “Næringsverksemd som bygningsentreprenør.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.2m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 30.2m
Operating profit
NOK 1.0m
Equity
NOK 4.7m
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns RE-BYGG AS?

RE-BYGG HOLDING AS
RE-BYGG AS
NOK 30.2m rev. · NOK 1.0m profit

RE-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RE-BYGG AS er morselskap for 2 datterselskaper:

Frequently asked questions about RE-BYGG AS

Who owns RE-BYGG AS?

RE-BYGG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RE-BYGG AS?

RE-BYGG AS had revenue of NOK 30.2m in 2024.

Who is the general manager of RE-BYGG AS?

Jørgen Veien is registered as general manager of RE-BYGG AS.

Where is RE-BYGG AS based?

RE-BYGG AS has its business address in Byrkjelo.

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.