biztrac. BETA
COMPANY REGISTER PROFILE
812190962 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computing infrastructure, data processing, hosting and related activities

NORDEX AS

Org. no. 812190962 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −11,000
Incorporated 2013
Share capital NOK 47,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).

NORDEX AS is registered as a limited company in Oslo, Oslo with organisation number 812190962. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2013. Registered share capital is NOK 47,000, divided into 46960 shares. The company's stated purpose is: “Produsere og tilby datakommunikasjonstjenester og annen virksomhet som står i forbindelse med transport av data.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −11,000
▼ −118 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns NORDEX AS?

NORDEX AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDEX AS

Who owns NORDEX AS?

ETHERCOM AS is the largest registered owner, with 49.1%.

What is the revenue of NORDEX AS?

NORDEX AS had revenue of NOK 0 in 2025.

Who is the general manager of NORDEX AS?

Kjell Arne Øien is registered as general manager of NORDEX AS.

Where is NORDEX AS based?

NORDEX 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 03.10.2026.

Report a problem

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