BIZTRAC BETA
Other technical consultancy

DCXPERTISE AS

Org. no. 933227820 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −194,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

DCXPERTISE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 933227820. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen industrirådgivning - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −194,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −194,000
Equity
NOK 24,000
Est. value
NOK 39,000

Financial health · 2025

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

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

Who owns DCXPERTISE AS?

CASTORTROY AS
DCXPERTISE AS
NOK 0 rev. · NOK −194,000 profit

DCXPERTISE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DCXPERTISE AS

Who owns DCXPERTISE AS?

CASTORTROY AS is the largest registered owner, with 100.0%.

What is the revenue of DCXPERTISE AS?

DCXPERTISE AS had revenue of NOK 0 in 2025.

Who is the general manager of DCXPERTISE AS?

Halvor Bjerke is registered as general manager of DCXPERTISE AS.

Where is DCXPERTISE AS based?

DCXPERTISE AS has its business address in Blaker.

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.