BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

FRODE BRUN SOLBERG HOLDING AS

Org. no. 989270761 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 1.4m
Incorporated 2005
Share capital NOK 100,000

Signals

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

FRODE BRUN SOLBERG HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989270761. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og fast eiendom, samt rådgivningsvirksomhet.”.

Key figures · 2024

Operating profit
NOK −8,000
Equity
NOK 1.4m
Est. value
NOK 1.7m

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 FRODE BRUN SOLBERG HOLDING AS?

FRODE BRUN SOLBERG
FRODE BRUN SOLBERG HOLDING AS
· NOK −8,000 profit

FRODE BRUN SOLBERG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRODE BRUN SOLBERG HOLDING AS own?

FRODE BRUN SOLBERG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRODE BRUN SOLBERG HOLDING AS

Who owns FRODE BRUN SOLBERG HOLDING AS?

FRODE BRUN SOLBERG is the largest registered owner, with 100.0%.

Who is the general manager of FRODE BRUN SOLBERG HOLDING AS?

Frode Brun Solberg is registered as general manager of FRODE BRUN SOLBERG HOLDING AS.

Where is FRODE BRUN SOLBERG HOLDING AS based?

FRODE BRUN SOLBERG HOLDING AS has its business address in Trondheim.

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.