BIZTRAC BETA
Rental and operating of own or leased real estate

B SØRHEIM HOLDING AS

Org. no. 921980051 Limited company (AS) Strand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 63,000
Operating profit NOK −320,000
Equity NOK 1.8m
Incorporated 2018
Share capital NOK 180,000

Signals

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

B SØRHEIM HOLDING AS is registered as a limited company in Strand, Rogaland with organisation number 921980051. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 180,000, divided into 1 shares. The company's stated purpose is: “Å eie aksjer i selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 63,000 in revenue and NOK −320,000 in operating profit.

Key figures · 2025

Revenue
NOK 63,000
Operating profit
NOK −320,000
Equity
NOK 1.8m
Est. value
NOK 6.2m

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.1%
Good
Equity as a share of total capital

Who owns B SØRHEIM HOLDING AS?

BJARNE SØRHEIM
B SØRHEIM HOLDING AS
NOK 63,000 rev. · NOK −320,000 profit

B SØRHEIM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does B SØRHEIM HOLDING AS own?

B SØRHEIM HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about B SØRHEIM HOLDING AS

Who owns B SØRHEIM HOLDING AS?

BJARNE SØRHEIM is the largest registered owner, with 100.0%.

What is the revenue of B SØRHEIM HOLDING AS?

B SØRHEIM HOLDING AS had revenue of NOK 63,000 in 2025.

Where is B SØRHEIM HOLDING AS based?

B SØRHEIM HOLDING AS has its business address in Tau.

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.