BIZTRAC BETA
COMPANY REGISTER PROFILE
928430987 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 02.09.2026
SILEDA HOLDCO III AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

SILEDA HOLDCO III AS

Org. no. 928430987 Limited company (AS) Oslo Incorporated 2021 In liquidation
Ownership graph ↗
Operating profit NOK −138,000
Equity NOK 252.6m
Incorporated 2021
Share capital NOK 39,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−138k kr).

SILEDA HOLDCO III AS is registered as a limited company in Oslo, Oslo with organisation number 928430987. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 39,000, divided into 3000 shares. The company's stated purpose is: “Å investere i, eie, utvikle og selge eller på annet vis helt eller delvis realisere virksomhet og selskaper, samt deltagelse i andre selskaper og dertil hørende virksomhet.”.

Former names: NFH 211227 AS

Key figures · 2025

Operating profit
NOK −138,000
Equity
NOK 252.6m

Financial health · 2025

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

Who owns SILEDA HOLDCO III AS?

SILEDA HOLDCO III AS
· NOK −138,000 profit

SILEDA HOLDCO III AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SILEDA HOLDCO III AS own?

SILEDA HOLDCO III AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SILEDA HOLDCO III AS

Who owns SILEDA HOLDCO III AS?

CIRCURA TOPHOLDING AB is the largest registered owner, with 100.0%.

Where is SILEDA HOLDCO III AS based?

SILEDA HOLDCO III 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 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.