BIZTRAC BETA
Activities of fitness centres

KI DRIFT AS

Org. no. 899189582 Limited company (AS) Stavanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 182,000
Equity NOK −577,000
Incorporated 2012
Share capital NOK 195,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−577k kr).
  • Nylig endring 2026-06-26 Adresseendring registrert 2026-06-26.

KI DRIFT AS is registered as a limited company in Stavanger, Rogaland with organisation number 899189582. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2012. Registered share capital is NOK 195,000, divided into 97500 shares. The company's stated purpose is: “Drift av treningssenter med tilstøtende virksomhet herunder salg av sports- og treningsartikler, konsulent virksomhet, drift av kafevirksomhet i lokalene, arrangement samt deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 182,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 182,000
Equity
NOK −577,000
Est. value
NOK 790,000

Financial health · 2024

Liquidity
3.11
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-36.3%
Weak
Equity as a share of total capital

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

Who owns KI DRIFT AS?

HELIOS INVEST AS
KI DRIFT AS
NOK 4.8m rev. · NOK 182,000 profit

KI DRIFT AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about KI DRIFT AS

Who owns KI DRIFT AS?

HELIOS INVEST AS is the largest registered owner, with 73.3%.

What is the revenue of KI DRIFT AS?

KI DRIFT AS had revenue of NOK 4.8m in 2024.

Where is KI DRIFT AS based?

KI DRIFT AS has its business address in Stavanger.

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.