BIZTRAC BETA
COMPANY REGISTER PROFILE
990324204 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

DISEN INVEST AS

Org. no. 990324204 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −28,000
Equity NOK 28.1m
Incorporated 2006
Share capital NOK 500,000

Signals

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

DISEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 990324204. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2006. Registered share capital is NOK 500,000, divided into 50000 shares. The company's stated purpose is: “Løpende investering i form av kjøp og salg av verdipapirer og annet hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 28.1m
Est. value
NOK 22.1m

Financial health · 2024

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

Who owns DISEN INVEST AS?

MORTEN KAMPLI
DISEN INVEST AS
NOK 0 rev. · NOK −28,000 profit

DISEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DISEN INVEST AS

Who owns DISEN INVEST AS?

MORTEN KAMPLI is the largest registered owner, with 100.0%.

What is the revenue of DISEN INVEST AS?

DISEN INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of DISEN INVEST AS?

Morten Kampli is registered as general manager of DISEN INVEST AS.

Where is DISEN INVEST AS based?

DISEN 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.