BIZTRAC BETA
Other captive investment companies

DITLEF HOLDING AS

Org. no. 994830112 Limited company (AS) Østre Toten Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 232,000
Operating profit NOK −184,000
Equity NOK 10.9m
Incorporated 2009
Share capital NOK 102,000

Signals

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

DITLEF HOLDING AS is registered as a limited company in Østre Toten, Innlandet with organisation number 994830112. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2009. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Aksjebesittelse, kjøp og salg av aksjer, konsulenttjenester og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 232,000 in revenue and NOK −184,000 in operating profit.

Key figures · 2025

Revenue
NOK 232,000
Operating profit
NOK −184,000
Equity
NOK 10.9m
Est. value
NOK 14.2m

Financial health · 2025

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

Who owns DITLEF HOLDING AS?

ARNE JOHANNES DITLEFSEN
DITLEF HOLDING AS
NOK 232,000 rev. · NOK −184,000 profit

DITLEF HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does DITLEF HOLDING AS own?

DITLEF HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about DITLEF HOLDING AS

Who owns DITLEF HOLDING AS?

ARNE JOHANNES DITLEFSEN is the largest registered owner, with 97.1%.

What is the revenue of DITLEF HOLDING AS?

DITLEF HOLDING AS had revenue of NOK 232,000 in 2025.

Where is DITLEF HOLDING AS based?

DITLEF HOLDING AS has its business address in Nordre Toten.

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.