biztrac. BETA
COMPANY REGISTER PROFILE
914962447 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SINGULAR HOLDING AS

Org. no. 914962447 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK −719,000
Incorporated 2015
Share capital NOK 522,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−719k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

SINGULAR HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 914962447. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 522,000, divided into 5217063 shares. The company's stated purpose is: “Å investere i og eie aksjer, finansielle instrumenter og andeler i andre selskaper, med formål om å bidra til utvikling av slike selskaper og verdiskapning for selskapets aksjonærer, samt annen virksomhet som står i naturlig forbindelse med dette.”.

Former names: KREVU INVEST AS

Key figures · 2025

Operating profit
NOK −19,000
▲ +27 %
Equity
NOK −719,000
▼ −3 %

Financial health · 2025

Liquidity
29.81
Very good
Current assets ÷ current liabilities
Profitability
-19.0%
Not satisfactory
Return on total assets
Solidity
-643.6%
Weak
Equity as a share of total capital

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

Who owns SINGULAR HOLDING AS?

SINGULAR HOLDING AS has 7 registered shareholders:

All shareholders and roles →

Which companies does SINGULAR HOLDING AS own?

SINGULAR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SINGULAR HOLDING AS

Who owns SINGULAR HOLDING AS?

ESKELAND INVEST AS is the largest registered owner, with 38.3%.

Where is SINGULAR HOLDING AS based?

SINGULAR HOLDING AS has its business address in Oslo.

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.