BIZTRAC BETA
Business and other management consultancy activities

DILATIVE MANAGEMENT AS

Org. no. 922747970 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 776
Operating profit NOK −28,000
Equity NOK 27,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

DILATIVE MANAGEMENT AS is registered as a limited company in Drammen, Buskerud with organisation number 922747970. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Forretningsutvikling.”. The most recent filed accounts, for the 2024 financial year, show NOK 776 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 776
Operating profit
NOK −28,000
Equity
NOK 27,000
Est. value
NOK 14,000

Financial health · 2024

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

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

Who owns DILATIVE MANAGEMENT AS?

DILATIVE INVEST AS
DILATIVE MANAGEMENT AS
NOK 776 rev. · NOK −28,000 profit

DILATIVE MANAGEMENT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DILATIVE MANAGEMENT AS er morselskap for 1 datterselskap:

Frequently asked questions about DILATIVE MANAGEMENT AS

Who owns DILATIVE MANAGEMENT AS?

DILATIVE INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of DILATIVE MANAGEMENT AS?

DILATIVE MANAGEMENT AS had revenue of NOK 776 in 2024.

Where is DILATIVE MANAGEMENT AS based?

DILATIVE MANAGEMENT AS has its business address in Drammen.

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.