BIZTRAC BETA
Construction of residential and non-residential buildings

REBO BYGG AS

Org. no. 911686996 Limited company (AS) Sarpsborg Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 557,000
Operating profit NOK −49,000
Equity NOK 367,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

REBO BYGG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 911686996. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rehabilitering av leiligheter, samt bygging av nybygg og tilbygg.”. The most recent filed accounts, for the 2024 financial year, show NOK 557,000 in revenue and NOK −49,000 in operating profit.

Key figures · 2024

Revenue
NOK 557,000
Operating profit
NOK −49,000
Equity
NOK 367,000
Est. value
NOK 352,000

Financial health · 2024

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

Who owns REBO BYGG AS?

CHRISTIAN ANDRÉ JOHANNESSEN SOLBERG
REBO BYGG AS
NOK 557,000 rev. · NOK −49,000 profit

REBO BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REBO BYGG AS

Who owns REBO BYGG AS?

CHRISTIAN ANDRÉ JOHANNESSEN SOLBERG is the largest registered owner, with 100.0%.

What is the revenue of REBO BYGG AS?

REBO BYGG AS had revenue of NOK 557,000 in 2024.

Who is the general manager of REBO BYGG AS?

Christian André Johannessen Solberg is registered as general manager of REBO BYGG AS.

Where is REBO BYGG AS based?

REBO BYGG AS has its business address in Klavestadhaugen.

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.