BIZTRAC BETA
Other captive investment companies

SINGULARITY CAPITAL AS

Org. no. 916916779 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −107,000
Equity NOK 13.1m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−107k kr).

SINGULARITY CAPITAL AS is registered as a limited company in Bergen, Vestland with organisation number 916916779. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper og tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −107,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −107,000
Equity
NOK 13.1m
Est. value
NOK 16.7m

Financial health · 2024

Liquidity
-137.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
86.0%
Very good
Equity as a share of total capital

Who owns SINGULARITY CAPITAL AS?

CHRISTOFFER PETTERSEN
SINGULARITY CAPITAL AS
NOK 0 rev. · NOK −107,000 profit

SINGULARITY CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SINGULARITY CAPITAL AS own?

SINGULARITY CAPITAL AS holds stakes in 42 companies:

See the full ownership structure →

Frequently asked questions about SINGULARITY CAPITAL AS

Who owns SINGULARITY CAPITAL AS?

CHRISTOFFER PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of SINGULARITY CAPITAL AS?

SINGULARITY CAPITAL AS had revenue of NOK 0 in 2024.

Where is SINGULARITY CAPITAL AS based?

SINGULARITY CAPITAL AS has its business address in Bergen.

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.