BIZTRAC BETA
Manufacture of communication equipment

APPEAR ASA

Org. no. 986942033 Public limited company (ASA) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 602.2m
Operating profit NOK 66.4m
Equity NOK 259.7m
Incorporated 2004
Employees 166
Share capital NOK 1.2m

APPEAR ASA is registered as a public limited company in Oslo, Oslo with organisation number 986942033. The business is classified under manufacture of communication equipment (NACE 26.300). The company was incorporated in 2004 and has 166 registered employees. Registered share capital is NOK 1.2m, divided into 41217000 shares. The company's stated purpose is: “Utvilkle og tilby produkter, løsninger og tjenester for telekommunikasjon, leie ut konsulenter, delta i og investere i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 602.2m in revenue and NOK 66.4m in operating profit.

Key figures · 2024

Revenue
NOK 602.2m
Operating profit
NOK 66.4m
Equity
NOK 259.7m
Est. value
NOK 405.3m

Financial health · 2024

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

Who owns APPEAR ASA?

ACCELERATOR LTD
APPEAR ASA
NOK 602.2m rev. · NOK 66.4m profit

APPEAR ASA has 20+ registered shareholders:

All shareholders and roles →

Which companies does APPEAR ASA own?

APPEAR ASA holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about APPEAR ASA

Who owns APPEAR ASA?

ACCELERATOR LTD is the largest registered owner, with 37.8%.

What is the revenue of APPEAR ASA?

APPEAR ASA had revenue of NOK 602.2m in 2024.

Who is the general manager of APPEAR ASA?

Thomas Bostrøm Jørgensen is registered as general manager of APPEAR ASA.

Where is APPEAR ASA based?

APPEAR ASA 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.