BIZTRAC BETA
Computer programming activities

SYSTOR AS

Org. no. 945413808 Limited company (AS) Kongsberg Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 39,000
Operating profit NOK −68,000
Equity NOK 630,000
Incorporated 1987
Share capital NOK 112,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−68k kr).

SYSTOR AS is registered as a limited company in Kongsberg, Buskerud with organisation number 945413808. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 1987. Registered share capital is NOK 112,000, divided into 480 shares. The company's stated purpose is: “Utvikle og levere EDB-systemer og utøve rådgivning i bruk av slike systemer samt ervervelse og utleie av fast eiendom og beslektet virksomhet, herunder også deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 39,000 in revenue and NOK −68,000 in operating profit.

Key figures · 2024

Revenue
NOK 39,000
Operating profit
NOK −68,000
Equity
NOK 630,000
Est. value
NOK 352,000

Financial health · 2025

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

Who owns SYSTOR AS?

KJETIL HVILA SOLHAUG
SYSTOR AS
NOK 39,000 rev. · NOK −68,000 profit

SYSTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYSTOR AS

Who owns SYSTOR AS?

KJETIL HVILA SOLHAUG is the largest registered owner, with 100.0%.

What is the revenue of SYSTOR AS?

SYSTOR AS had revenue of NOK 39,000 in 2024.

Who is the general manager of SYSTOR AS?

Kjetil Hvila Solhaug is registered as general manager of SYSTOR AS.

Where is SYSTOR AS based?

SYSTOR 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.