biztrac. BETA
COMPANY REGISTER PROFILE
934671791 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SOLHAUGEN AS

Org. no. 934671791 Limited company (AS) Sveio Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 57,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

SOLHAUGEN AS is registered as a limited company in Sveio, Vestland with organisation number 934671791. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
▲ +0 %
Equity
NOK 57,000
▲ +12 %
Est. value
NOK 245,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
7.7%
Satisfactory
Return on total assets
Solidity
12.3%
Weak
Equity as a share of total capital

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

Who owns SOLHAUGEN AS?

SOLHAUGEN AS
NOK 0 rev. · NOK −2,000 profit

SOLHAUGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLHAUGEN AS own?

SOLHAUGEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLHAUGEN AS

Who owns SOLHAUGEN AS?

Svein Olaf Bua is the largest registered owner, with 100.0%.

What is the revenue of SOLHAUGEN AS?

SOLHAUGEN AS had revenue of NOK 0 in 2025.

Who is the general manager of SOLHAUGEN AS?

Svein Olaf Bua is registered as general manager of SOLHAUGEN AS.

Where is SOLHAUGEN AS based?

SOLHAUGEN AS has its business address in Sveio.

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.