BIZTRAC BETA
Other captive investment companies

SVARTSKJÆR AS

Org. no. 915252478 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 372,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

SVARTSKJÆR AS is registered as a limited company in Bærum, Akershus with organisation number 915252478. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i omsettelige verdipapirer (aksjer og andre verdipapirer som kan sidestilles med aksjer), fonds- og selskapsandeler (herunder andeler i ansvarlig selskap, kommandittselskap, indre selskap eller liknende eller tilsvarende fonds- eller selskapsstrukturer etablert i fremmed jurisdiksjon), obligasjoner og andre gjeldsinstrumenter hvor verdien i det vesentlige er knyttet til fast eiendom, samt drive virksomhet som hører naturlig sammen med dette.”.

Key figures · 2025

Operating profit
NOK −8,000
Equity
NOK 372,000
Est. value
NOK 267,000

Financial health · 2025

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

Who owns SVARTSKJÆR AS?

CHRISTIAN MYHRE
SVARTSKJÆR AS
· NOK −8,000 profit

SVARTSKJÆR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVARTSKJÆR AS own?

SVARTSKJÆR AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SVARTSKJÆR AS

Who owns SVARTSKJÆR AS?

CHRISTIAN MYHRE is the largest registered owner, with 100.0%.

Where is SVARTSKJÆR AS based?

SVARTSKJÆR AS has its business address in Høvik.

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.