BIZTRAC BETA
Civil engineering activities

SOLBERG KONSERN AS

Org. no. 915811809 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −42,000
Equity NOK 6.1m
Incorporated 2015
Share capital NOK 201,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−42k kr).
  • Nylig endring 2026-04-15 Adresseendring registrert 2026-04-15.

SOLBERG KONSERN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915811809. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2015. Registered share capital is NOK 201,000, divided into 30 shares. The company's stated purpose is: “Formuesforvaltning, herunder investering i aksjer og andre formuesobjekter, samt annen virksomhet som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −42,000
Equity
NOK 6.1m
Est. value
NOK 12.7m

Financial health · 2024

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

Who owns SOLBERG KONSERN AS?

KNUT BJARNE SOLBERG
SOLBERG KONSERN AS
· NOK −42,000 profit

SOLBERG KONSERN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SOLBERG KONSERN AS own?

SOLBERG KONSERN AS holds a stake in 1 company:

See the full ownership structure →

Group structure

SOLBERG KONSERN AS er morselskap for 1 datterselskap:

Frequently asked questions about SOLBERG KONSERN AS

Who owns SOLBERG KONSERN AS?

KNUT BJARNE SOLBERG is the largest registered owner, with 53.3%.

Who is the general manager of SOLBERG KONSERN AS?

Knut Bjarne Solberg is registered as general manager of SOLBERG KONSERN AS.

Where is SOLBERG KONSERN AS based?

SOLBERG KONSERN AS has its business address in Tiller.

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.