BIZTRAC BETA
Other real estate activities on a fee or contract basis

DITKA INVEST AS

Org. no. 994854224 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −38,000
Equity NOK 19.2m
Incorporated 2009
Share capital NOK 100,000

Signals

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

DITKA INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 994854224. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og forvalte aksjer, obligasjoner og andre verdipapirer, eie og forvalte eiendom, deltagelse i andre selskaper, samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 19.2m
Est. value
NOK 23.4m

Financial health · 2024

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

Who owns DITKA INVEST AS?

DITLEF MARTENS
DITKA INVEST AS
NOK 0 rev. · NOK −38,000 profit

DITKA INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does DITKA INVEST AS own?

DITKA INVEST AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about DITKA INVEST AS

Who owns DITKA INVEST AS?

DITLEF MARTENS is the largest registered owner, with 50.1%.

What is the revenue of DITKA INVEST AS?

DITKA INVEST AS had revenue of NOK 0 in 2024.

Where is DITKA INVEST AS based?

DITKA INVEST 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.