BIZTRAC BETA
Other technical consultancy

COMPAX SOLUTIONS AS

Org. no. 920003303 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 747,000
Operating profit NOK −3.7m
Equity NOK 230,000
Incorporated 2017
Share capital NOK 54,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,7 mill kr).

COMPAX SOLUTIONS AS is registered as a limited company in Bærum, Akershus with organisation number 920003303. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 54,000, divided into 543816 shares. The company's stated purpose is: “Utvikle komprimeringsløsnigner for søppel til det offentlige og private markedet.”. The most recent filed accounts, for the 2024 financial year, show NOK 747,000 in revenue and NOK −3.7m in operating profit.

Key figures · 2024

Revenue
NOK 747,000
Operating profit
NOK −3.7m
Equity
NOK 230,000
Est. value
NOK 896,000

Financial health · 2024

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

Who owns COMPAX SOLUTIONS AS?

JFB INVEST AS
COMPAX SOLUTIONS AS
NOK 747,000 rev. · NOK −3.7m profit

COMPAX SOLUTIONS AS has 20 registered shareholders:

All shareholders and roles →

Which companies does COMPAX SOLUTIONS AS own?

COMPAX SOLUTIONS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about COMPAX SOLUTIONS AS

Who owns COMPAX SOLUTIONS AS?

JFB INVEST AS is the largest registered owner, with 15.0%.

What is the revenue of COMPAX SOLUTIONS AS?

COMPAX SOLUTIONS AS had revenue of NOK 747,000 in 2024.

Where is COMPAX SOLUTIONS AS based?

COMPAX SOLUTIONS AS has its business address in Lysaker.

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.