BIZTRAC BETA
Computer programming activities

UNISOT HOLDING AS

Org. no. 927232944 Limited company (AS) Ullensaker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.1m
Equity NOK 15.7m
Incorporated 2021
Share capital NOK 915,000

UNISOT HOLDING AS is registered as a limited company in Ullensaker, Akershus with organisation number 927232944. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 915,000, divided into 12039446 shares. The company's stated purpose is: “Å eie og investere i andre selskaper og virksomheter og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.1m
Equity
NOK 15.7m
Est. value
NOK 10.8m

Financial health · 2024

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

Who owns UNISOT HOLDING AS?

TRENOB HOLDING AS
UNISOT HOLDING AS
NOK 1.7m rev. · NOK 1.1m profit

UNISOT HOLDING AS has 20 registered shareholders:

All shareholders and roles →

Which companies does UNISOT HOLDING AS own?

UNISOT HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about UNISOT HOLDING AS

Who owns UNISOT HOLDING AS?

TRENOB HOLDING AS is the largest registered owner, with 50.7%.

What is the revenue of UNISOT HOLDING AS?

UNISOT HOLDING AS had revenue of NOK 1.7m in 2024.

Who is the general manager of UNISOT HOLDING AS?

Lars Olle Stephan Nilsson is registered as general manager of UNISOT HOLDING AS.

Where is UNISOT HOLDING AS based?

UNISOT HOLDING AS has its business address in Kløfta.

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.