BIZTRAC BETA
Computer programming activities

MALIKA KEYS AS

Org. no. 916729383 Limited company (AS) Indre Østfold Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 208,000
Equity NOK 336,000
Incorporated 2016
Share capital NOK 30,000

MALIKA KEYS AS is registered as a limited company in Indre Østfold, Østfold with organisation number 916729383. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Programvarerelaterte konsulenttjenester, økonomirelaterte konsulenttjenester, utleievirksomhet samt investering og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 208,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 208,000
Equity
NOK 336,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.3%
Good
Equity as a share of total capital

Who owns MALIKA KEYS AS?

STURLA DRAUMÅS
MALIKA KEYS AS
NOK 1.6m rev. · NOK 208,000 profit

MALIKA KEYS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MALIKA KEYS AS own?

MALIKA KEYS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MALIKA KEYS AS

Who owns MALIKA KEYS AS?

STURLA DRAUMÅS is the largest registered owner, with 50.0%.

What is the revenue of MALIKA KEYS AS?

MALIKA KEYS AS had revenue of NOK 1.6m in 2024.

Who is the general manager of MALIKA KEYS AS?

Sturla Draumås is registered as general manager of MALIKA KEYS AS.

Where is MALIKA KEYS AS based?

MALIKA KEYS AS has its business address in Askim.

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.