biztrac. BETA
COMPANY REGISTER PROFILE
812503812 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

DPK CONSULTANTS AS

Org. no. 812503812 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 85,000
Operating profit NOK 22,000
Equity NOK −59,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−59k kr).

DPK CONSULTANTS AS is registered as a limited company in Oslo, Oslo with organisation number 812503812. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet og alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 85,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 85,000
▼ −36 %
Operating profit
NOK 22,000
▲ +841 %
Equity
NOK −59,000
▲ +9 %
Est. value
NOK 112,000

Financial health · 2025

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

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

Who owns DPK CONSULTANTS AS?

DPK CONSULTANTS AS
NOK 85,000 rev. · NOK 22,000 profit

DPK CONSULTANTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DPK CONSULTANTS AS

Who owns DPK CONSULTANTS AS?

Usifo Christopher Osuman is the largest registered owner, with 100.0%.

What is the revenue of DPK CONSULTANTS AS?

DPK CONSULTANTS AS had revenue of NOK 85,000 in 2025.

Where is DPK CONSULTANTS AS based?

DPK CONSULTANTS 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.