BIZTRAC BETA
Computer programming activities

TURBULENT FLUX AS

Org. no. 917802971 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK −9.6m
Equity NOK 22.6m
Incorporated 2016
Employees 5
Share capital NOK 359,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9,6 mill kr).

TURBULENT FLUX AS is registered as a limited company in Oslo, Oslo with organisation number 917802971. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016 and has 5 registered employees. Registered share capital is NOK 359,000, divided into 3588048 shares. The company's stated purpose is: “Utvikle og levere produkter og tjenester basert på informasjonsteknologi for å optimalisere og effektivisere prosesser.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK −9.6m in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK −9.6m
Equity
NOK 22.6m
Est. value
NOK 14.7m

Financial health · 2024

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

Who owns TURBULENT FLUX AS?

COMMERCOR AS
TURBULENT FLUX AS
NOK 6.9m rev. · NOK −9.6m profit

TURBULENT FLUX AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about TURBULENT FLUX AS

Who owns TURBULENT FLUX AS?

COMMERCOR AS is the largest registered owner, with 17.7%.

What is the revenue of TURBULENT FLUX AS?

TURBULENT FLUX AS had revenue of NOK 6.9m in 2024.

Who is the general manager of TURBULENT FLUX AS?

Trond Halvard Ellingsen is registered as general manager of TURBULENT FLUX AS.

Where is TURBULENT FLUX AS based?

TURBULENT FLUX 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 15.06.2026.

Report a problem

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