BIZTRAC BETA
COMPANY REGISTER PROFILE
920859755 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

SOLHEIMSNES HOLDING AS

Org. no. 920859755 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13
Equity NOK 7.6m
Incorporated 2018
Share capital NOK 30,000

Signals

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

SOLHEIMSNES HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 920859755. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Finansieringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13
Equity
NOK 7.6m
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns SOLHEIMSNES HOLDING AS?

LINDA SOLHEIMSNES
SOLHEIMSNES HOLDING AS
NOK 0 rev. · NOK −13 profit

SOLHEIMSNES HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLHEIMSNES HOLDING AS

Who owns SOLHEIMSNES HOLDING AS?

LINDA SOLHEIMSNES is the largest registered owner, with 100.0%.

What is the revenue of SOLHEIMSNES HOLDING AS?

SOLHEIMSNES HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of SOLHEIMSNES HOLDING AS?

Linda Solheimsnes is registered as general manager of SOLHEIMSNES HOLDING AS.

Where is SOLHEIMSNES HOLDING AS based?

SOLHEIMSNES HOLDING AS has its business address in Bekkestua.

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.