BIZTRAC BETA
Wholesale of information and communication equipment

COM2GETHER AS

Org. no. 982716616 Limited company (AS) Kongsberg Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 50.9m
Operating profit NOK −2.4m
Equity NOK 331,000
Incorporated 2000
Employees 24
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,4 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

COM2GETHER AS is registered as a limited company in Kongsberg, Buskerud with organisation number 982716616. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2000 and has 24 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handelsvirksomhet samt alt som står i forbindelse med dette - herunder delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 50.9m in revenue and NOK −2.4m in operating profit.

Key figures · 2024

Revenue
NOK 50.9m
Operating profit
NOK −2.4m
Equity
NOK 331,000
Est. value
NOK 16.4m

Financial health · 2024

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.7%
Weak
Equity as a share of total capital

Who owns COM2GETHER AS?

IMAGO GROUP AS
COM2GETHER AS
NOK 50.9m rev. · NOK −2.4m profit

COM2GETHER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about COM2GETHER AS

Who owns COM2GETHER AS?

IMAGO GROUP AS is the largest registered owner, with 91.0%.

What is the revenue of COM2GETHER AS?

COM2GETHER AS had revenue of NOK 50.9m in 2024.

Where is COM2GETHER AS based?

COM2GETHER AS has its business address in Kongsberg.

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.