BIZTRAC BETA
Other software publishing

ZISSON AS

Org. no. 989849492 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 77.4m
Operating profit NOK 977,000
Equity NOK −26.5m
Incorporated 2006
Employees 43
Share capital NOK 7.0m

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−26,5 mill kr).

ZISSON AS is registered as a limited company in Oslo, Oslo with organisation number 989849492. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2006 and has 43 registered employees. Registered share capital is NOK 7.0m, divided into 697691065 shares. The company's stated purpose is: “Teknologiutvikling, utnyttelse av teknologi i egen virksomhet, lisensiering og salg av teknologiløsninger, samt investering i selskaper og dertil hørende aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 77.4m in revenue and NOK 977,000 in operating profit.

Key figures · 2024

Revenue
NOK 77.4m
Operating profit
NOK 977,000
Equity
NOK −26.5m
Est. value
NOK 4.2m

Financial health · 2024

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

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

Who owns ZISSON AS?

LEADDESK OYJ
ZISSON AS
NOK 77.4m rev. · NOK 977,000 profit

ZISSON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZISSON AS

Who owns ZISSON AS?

LEADDESK OYJ is the largest registered owner, with 100.0%.

What is the revenue of ZISSON AS?

ZISSON AS had revenue of NOK 77.4m in 2024.

Who is the general manager of ZISSON AS?

Olli Sakari Nokso-Koivisto is registered as general manager of ZISSON AS.

Where is ZISSON AS based?

ZISSON AS has its business address in Oslo.

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.