BIZTRAC BETA
Computer consultancy and computer facilities management activities

UNICOM GROUP AS

Org. no. 920451993 Limited company (AS) Lillestrøm Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 762,000
Operating profit NOK −204,000
Equity NOK −211,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−211k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−204k kr).

UNICOM GROUP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 920451993. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg og markedsføring av gaveartikler via nettbutikk og rådgivende innenfor digitale medier.”. The most recent filed accounts, for the 2024 financial year, show NOK 762,000 in revenue and NOK −204,000 in operating profit.

Key figures · 2024

Revenue
NOK 762,000
Operating profit
NOK −204,000
Equity
NOK −211,000

Financial health · 2024

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-71.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns UNICOM GROUP AS?

TROY CAPITAL AS
UNICOM GROUP AS
NOK 762,000 rev. · NOK −204,000 profit

UNICOM GROUP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNICOM GROUP AS

Who owns UNICOM GROUP AS?

TROY CAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of UNICOM GROUP AS?

UNICOM GROUP AS had revenue of NOK 762,000 in 2024.

Where is UNICOM GROUP AS based?

UNICOM GROUP AS has its business address in Strømmen.

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.