BIZTRAC BETA
Joinery installation

O.S BYGG AS

Org. no. 930688436 Limited company (AS) Haugesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −523,000
Equity NOK −482,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−482k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−523k kr).

O.S BYGG AS is registered as a limited company in Haugesund, Rogaland with organisation number 930688436. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Utføring av snekkertjenester, maling, sparkel og flislegging samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −523,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −523,000
Equity
NOK −482,000

Financial health · 2024

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-242.8%
Weak
Equity as a share of total capital

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

Who owns O.S BYGG AS?

SALOMONSEN GROUP AS
O.S BYGG AS
NOK 0 rev. · NOK −523,000 profit

O.S BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about O.S BYGG AS

Who owns O.S BYGG AS?

SALOMONSEN GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of O.S BYGG AS?

O.S BYGG AS had revenue of NOK 0 in 2024.

Who is the general manager of O.S BYGG AS?

Christoffer Andersen Salomonsen is registered as general manager of O.S BYGG AS.

Where is O.S BYGG AS based?

O.S BYGG AS has its business address in Haugesund.

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.