BIZTRAC BETA
Rental and operating of own or leased real estate

DK FINANCE AS

Org. no. 918421645 Limited company (AS) Stange Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2,000
Operating profit NOK −6,000
Equity NOK 168
Incorporated 2016
Share capital NOK 30,000

Signals

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

DK FINANCE AS is registered as a limited company in Stange, Innlandet with organisation number 918421645. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Investeringer og eierinteresser i andre selskaper, og eiendom. Samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 2,000
Operating profit
NOK −6,000
Equity
NOK 168
Est. value
NOK 2,000

Financial health · 2024

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.0%
Weak
Equity as a share of total capital

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

Who owns DK FINANCE AS?

DANIEL KRISTOFFERSEN
DK FINANCE AS
NOK 2,000 rev. · NOK −6,000 profit

DK FINANCE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DK FINANCE AS own?

DK FINANCE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DK FINANCE AS

Who owns DK FINANCE AS?

DANIEL KRISTOFFERSEN is the largest registered owner, with 100.0%.

What is the revenue of DK FINANCE AS?

DK FINANCE AS had revenue of NOK 2,000 in 2024.

Where is DK FINANCE AS based?

DK FINANCE AS has its business address in Ottestad.

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.