BIZTRAC BETA
Computer programming activities

KAMAMUTA AS

Org. no. 925297119 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −203,000
Equity NOK −289,000
Incorporated 2020
Share capital NOK 40,000

Signals

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

KAMAMUTA AS is registered as a limited company in Bærum, Akershus with organisation number 925297119. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 40,000, divided into 33712114 shares. The company's stated purpose is: “Utvikling av programvare og datatjenester og salg og markedsføring av disse, handel, agentur, distribusjon av varer og tjenester og dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −203,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −203,000
Equity
NOK −289,000

Financial health · 2025

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

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

Who owns KAMAMUTA AS?

FUTT CONSULTING AS
KAMAMUTA AS
NOK 0 rev. · NOK −203,000 profit

KAMAMUTA AS has 17 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAMAMUTA AS

Who owns KAMAMUTA AS?

FUTT CONSULTING AS is the largest registered owner, with 62.0%.

What is the revenue of KAMAMUTA AS?

KAMAMUTA AS had revenue of NOK 0 in 2025.

Where is KAMAMUTA AS based?

KAMAMUTA AS has its business address in Lommedalen.

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.