BIZTRAC BETA
Civil engineering activities

UCON AS

Org. no. 976120655 Limited company (AS) Trondheim Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 2.1m
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

UCON AS is registered as a limited company in Trondheim, Trøndelag with organisation number 976120655. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “-Rådgivende ingeniørvirksomhet. -Utvikling og salg av teknisk programvare. -Import og videresalg (eventuelt postordresalg og eksport) av programvare. -Kursvirksomhet rettet mot opplæring innen ingeniørfag og bruk av dataprogram- -Deltakelse i annen virksomhet ved kjøp av aksjer og/eller fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 2.1m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns UCON AS?

TROND GRANLI
UCON AS
NOK 0 rev. · NOK −18,000 profit

UCON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UCON AS

Who owns UCON AS?

TROND GRANLI is the largest registered owner, with 78.0%.

What is the revenue of UCON AS?

UCON AS had revenue of NOK 0 in 2025.

Who is the general manager of UCON AS?

Trond Granli is registered as general manager of UCON AS.

Where is UCON AS based?

UCON AS has its business address in Trondheim.

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.