biztrac. BETA
COMPANY REGISTER PROFILE
935454581 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

ADMEL TECHNOLOGIES AS

Org. no. 935454581 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −83,000
Equity NOK −59,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−59k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−83k kr).
  • Nylig endring 2026-07-29 Aksjekapital registrert 2026-07-29.

ADMEL TECHNOLOGIES AS is registered as a limited company in Oslo, Oslo with organisation number 935454581. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Driftsselskap under AdMel Holding AS. Selskapet er et tech basert selskap som utvikler ulike software programvarer.”.

Key figures · 2025

Operating profit
NOK −83,000
Equity
NOK −59,000

Financial health · 2025

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

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

Who owns ADMEL TECHNOLOGIES AS?

ADMEL TECHNOLOGIES AS
· NOK −83,000 profit

ADMEL TECHNOLOGIES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADMEL TECHNOLOGIES AS

Who owns ADMEL TECHNOLOGIES AS?

ADMEL HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of ADMEL TECHNOLOGIES AS?

Mattis Deila Dusmanu is registered as general manager of ADMEL TECHNOLOGIES AS.

Where is ADMEL TECHNOLOGIES AS based?

ADMEL TECHNOLOGIES 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 03.10.2026.

Report a problem

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