BIZTRAC BETA
Construction of residential and non-residential buildings

SOLCO BYGG AS

Org. no. 933856771 Limited company (AS) Bærum Incorporated 1983 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK −176,000
Equity NOK 4.5m
Incorporated 1983
Share capital NOK 125,000

Signals

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

SOLCO BYGG AS is registered as a limited company in Bærum, Akershus with organisation number 933856771. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1983. Registered share capital is NOK 125,000, divided into 1000 shares. The company's stated purpose is: “Utføre totalentrepriser, konsulentvirksomhet, eiendomsforvaltning og gårdsbestyrelse, kjøp og salg av eiendom samt annen virksomhet som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK −176,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK −176,000
Equity
NOK 4.5m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns SOLCO BYGG AS?

HANS IVAR SOLBERG
SOLCO BYGG AS
NOK 4.5m rev. · NOK −176,000 profit

SOLCO BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLCO BYGG AS

Who owns SOLCO BYGG AS?

HANS IVAR SOLBERG is the largest registered owner, with 70.0%.

What is the revenue of SOLCO BYGG AS?

SOLCO BYGG AS had revenue of NOK 4.5m in 2025.

Who is the general manager of SOLCO BYGG AS?

Hans Ivar Solberg is registered as general manager of SOLCO BYGG AS.

Where is SOLCO BYGG AS based?

SOLCO BYGG AS has its business address in Jar.

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.