biztrac. BETA
COMPANY REGISTER PROFILE
935969859 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

SOLBERG AS

Org. no. 935969859 Limited company (AS) Osterøy Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 769,000
Operating profit NOK 166,000
Equity NOK 154,000
Incorporated 2025
Share capital NOK 30,000

SOLBERG AS is registered as a limited company in Osterøy, Vestland with organisation number 935969859. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen snekkerarbeid, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 769,000 in revenue and NOK 166,000 in operating profit.

Key figures · 2025

Revenue
NOK 769,000
Operating profit
NOK 166,000
Equity
NOK 154,000
Est. value
NOK 556,000

Financial health · 2025

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

Who owns SOLBERG AS?

SOLBERG AS
NOK 769,000 rev. · NOK 166,000 profit

SOLBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLBERG AS

Who owns SOLBERG AS?

Kjetil Olsen Solberg is the largest registered owner, with 100.0%.

What is the revenue of SOLBERG AS?

SOLBERG AS had revenue of NOK 769,000 in 2025.

Who is the general manager of SOLBERG AS?

Kjetil Olsen Solberg is registered as general manager of SOLBERG AS.

Where is SOLBERG AS based?

SOLBERG AS has its business address in Valestrandsfossen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.