BIZTRAC BETA
Construction of residential and non-residential buildings

DK DRIFT AS

Org. no. 933910113 Limited company (AS) Klepp Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 630,000
Operating profit NOK −43,000
Equity NOK −36,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−36k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−43k kr).

DK DRIFT AS is registered as a limited company in Klepp, Rogaland with organisation number 933910113. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bygg og renovering tjenester og alt som hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 630,000 in revenue and NOK −43,000 in operating profit.

Key figures · 2025

Revenue
NOK 630,000
Operating profit
NOK −43,000
Equity
NOK −36,000

Financial health · 2025

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

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

Who owns DK DRIFT AS?

DARIUS KILIJONAS
DK DRIFT AS
NOK 630,000 rev. · NOK −43,000 profit

DK DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DK DRIFT AS

Who owns DK DRIFT AS?

DARIUS KILIJONAS is the largest registered owner, with 100.0%.

What is the revenue of DK DRIFT AS?

DK DRIFT AS had revenue of NOK 630,000 in 2025.

Who is the general manager of DK DRIFT AS?

Darius Kilijonas is registered as general manager of DK DRIFT AS.

Where is DK DRIFT AS based?

DK DRIFT AS has its business address in Kleppe.

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.