BIZTRAC BETA
Wholesale of information and communication equipment

ATEA AS

Org. no. 976239997 Limited company (AS) Oslo Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 8.7bn
Operating profit NOK 351.3m
Equity NOK 1.3bn
Incorporated 1996
Employees 1833
Share capital NOK 100.0m

ATEA AS is registered as a limited company in Oslo, Oslo with organisation number 976239997. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1996 and has 1833 registered employees. Registered share capital is NOK 100.0m, divided into 100000 shares. The company's stated purpose is: “Konsulentvirksomhet, handel og agenturvirksomhet samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.7bn in revenue and NOK 351.3m in operating profit.

Key figures · 2024

Revenue
NOK 8.7bn
Operating profit
NOK 351.3m
Equity
NOK 1.3bn
Est. value
NOK 1.8bn

Financial health · 2024

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.1%
Good
Equity as a share of total capital

Who owns ATEA AS?

ATEA ASA
ATEA AS
NOK 8.7bn rev. · NOK 351.3m profit

ATEA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ATEA AS own?

ATEA AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

ATEA AS er morselskap for 8 datterselskaper:

Frequently asked questions about ATEA AS

Who owns ATEA AS?

ATEA ASA is the largest registered owner, with 100.0%.

What is the revenue of ATEA AS?

ATEA AS had revenue of NOK 8.7bn in 2024.

Who is the general manager of ATEA AS?

Ole Petter Saxrud is registered as general manager of ATEA AS.

Where is ATEA AS based?

ATEA 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.