BIZTRAC BETA
Uoppgitt

DUX DUCIS AS

Org. no. 999525822 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 50,000
Operating profit NOK −18,000
Equity NOK −398,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−398k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

DUX DUCIS AS is registered as a limited company in Oslo, Oslo with organisation number 999525822. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper, immaterielle rettigheter, driftsmidler og fast eiendom, samt konsulentvirksomhet i forbindelse med selskapets investeringer mv.”. The most recent filed accounts, for the 2024 financial year, show NOK 50,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 50,000
Operating profit
NOK −18,000
Equity
NOK −398,000

Financial health · 2024

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.6%
Weak
Equity as a share of total capital

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

Who owns DUX DUCIS AS?

HÅVARD KROGSÆTER
DUX DUCIS AS
NOK 50,000 rev. · NOK −18,000 profit

DUX DUCIS AS has 9 registered shareholders:

All shareholders and roles →

Which companies does DUX DUCIS AS own?

DUX DUCIS AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about DUX DUCIS AS

Who owns DUX DUCIS AS?

HÅVARD KROGSÆTER is the largest registered owner, with 20.0%.

What is the revenue of DUX DUCIS AS?

DUX DUCIS AS had revenue of NOK 50,000 in 2024.

Where is DUX DUCIS AS based?

DUX DUCIS 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 15.06.2026.

Report a problem

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