BIZTRAC BETA
Computer programming activities

SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS

Org. no. 820915542 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 180,000
Equity NOK 348,000
Incorporated 2018
Share capital NOK 30,000

SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS is registered as a limited company in Oslo, Oslo with organisation number 820915542. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive forretningsutvikling, service og salg av teknologibaserte produkter og tjenester samt hva somhører til under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 180,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 180,000
Equity
NOK 348,000
Est. value
NOK 1.2m

Financial health · 2024

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.6%
Good
Equity as a share of total capital

Who owns SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS?

SAPIENS (UK) INSURANCE SOFTWARE SOL
SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS
NOK 3.8m rev. · NOK 180,000 profit

SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS

Who owns SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS?

SAPIENS (UK) INSURANCE SOFTWARE SOL is the largest registered owner, with 100.0%.

What is the revenue of SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS?

SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS had revenue of NOK 3.8m in 2024.

Where is SAPIENS SOFTWARE SOLUTIONS (NORWAY) AS based?

SAPIENS SOFTWARE SOLUTIONS (NORWAY) 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.