BIZTRAC BETA
Other software publishing

STICOS AS

Org. no. 934228391 Limited company (AS) Trondheim Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 324.6m
Operating profit NOK 104.2m
Equity NOK 6.0m
Incorporated 1983
Employees 156
Share capital NOK 5.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STICOS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934228391. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 1983 and has 156 registered employees. Registered share capital is NOK 5.0m, divided into 5000 shares. The company's stated purpose is: “Utvikling, produksjon og salg av varer og datatjenester og alt som derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 324.6m in revenue and NOK 104.2m in operating profit.

Key figures · 2024

Revenue
NOK 324.6m
Operating profit
NOK 104.2m
Equity
NOK 6.0m
Est. value
NOK 446.6m

Financial health · 2024

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.0%
Weak
Equity as a share of total capital

Who owns STICOS AS?

VISMA NORGE HOLDING AS
STICOS AS
NOK 324.6m rev. · NOK 104.2m profit

STICOS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STICOS AS er morselskap for 3 datterselskaper:

Frequently asked questions about STICOS AS

Who owns STICOS AS?

VISMA NORGE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STICOS AS?

STICOS AS had revenue of NOK 324.6m in 2024.

Who is the general manager of STICOS AS?

Johnny Johnsen is registered as general manager of STICOS AS.

Where is STICOS AS based?

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