BIZTRAC BETA
Other software publishing

ABAX AS

Org. no. 993098736 Limited company (AS) Larvik Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 497.9m
Operating profit NOK 105.6m
Equity NOK 1.3bn
Incorporated 2008
Employees 103
Share capital NOK 349.4m

ABAX AS is registered as a limited company in Larvik, Vestfold with organisation number 993098736. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2008 and has 103 registered employees. Registered share capital is NOK 349.4m, divided into 17918097 shares. The company's stated purpose is: “Utvikle, produsere, markedsføre og å selge utstyr og tjenester for gjenfinning og sporing av mennesker, eiendeler og utstyr i Norge og andre land. Selskapet skal også eie og investere i verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 497.9m in revenue and NOK 105.6m in operating profit.

Key figures · 2024

Revenue
NOK 497.9m
Operating profit
NOK 105.6m
Equity
NOK 1.3bn
Est. value
NOK 1.3bn

Financial health · 2024

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

Who owns ABAX AS?

ABAX GROUP AS
ABAX AS
NOK 497.9m rev. · NOK 105.6m profit

ABAX AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ABAX AS own?

ABAX AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ABAX AS

Who owns ABAX AS?

ABAX GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of ABAX AS?

ABAX AS had revenue of NOK 497.9m in 2024.

Who is the general manager of ABAX AS?

Emma Sofia Dyga is registered as general manager of ABAX AS.

Where is ABAX AS based?

ABAX AS has its business address in Larvik.

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.