BIZTRAC BETA
Computer programming activities

EXOREACTION AS

Org. no. 926492527 Limited company (AS) Eidsvoll Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 10.9m
Operating profit NOK −968,000
Equity NOK 132,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−968k kr).

EXOREACTION AS is registered as a limited company in Eidsvoll, Akershus with organisation number 926492527. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å sikre verdiskapning og konkurransekraft til næringslivet ved å levere kostnadseffektiv og aktivt forvaltning av næringslivets investeringer i IT skreddersøm.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.9m in revenue and NOK −968,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.9m
Operating profit
NOK −968,000
Equity
NOK 132,000
Est. value
NOK 18.5m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.1%
Weak
Equity as a share of total capital

Who owns EXOREACTION AS?

T-HEX HOLDING AS
EXOREACTION AS
NOK 10.9m rev. · NOK −968,000 profit

EXOREACTION AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EXOREACTION AS

Who owns EXOREACTION AS?

T-HEX HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of EXOREACTION AS?

EXOREACTION AS had revenue of NOK 10.9m in 2024.

Who is the general manager of EXOREACTION AS?

Selina Hansen Stenberg is registered as general manager of EXOREACTION AS.

Where is EXOREACTION AS based?

EXOREACTION AS has its business address in Eidsvoll Verk.

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.