BIZTRAC BETA
Computer programming activities

KRAFT AI AS

Org. no. 923137572 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK −243,000
Equity NOK 7.5m
Incorporated 2019
Share capital NOK 88,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−243k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KRAFT AI AS is registered as a limited company in Drammen, Buskerud with organisation number 923137572. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 88,000, divided into 4382 shares. The company's stated purpose is: “Levere IT-produkter og tjenester til næringslivet. Konsulenttjenester relatert til bedriftsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK −243,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK −243,000
Equity
NOK 7.5m
Est. value
NOK 10.5m

Financial health · 2024

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

Who owns KRAFT AI AS?

KRAFTIA ENERGI AS
KRAFT AI AS
NOK 4.2m rev. · NOK −243,000 profit

KRAFT AI AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRAFT AI AS

Who owns KRAFT AI AS?

KRAFTIA ENERGI AS is the largest registered owner, with 50.4%.

What is the revenue of KRAFT AI AS?

KRAFT AI AS had revenue of NOK 4.2m in 2025.

Who is the general manager of KRAFT AI AS?

Harald Ketilsson is registered as general manager of KRAFT AI AS.

Where is KRAFT AI AS based?

KRAFT AI AS has its business address in Drammen.

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.