BIZTRAC BETA
COMPANY REGISTER PROFILE
930697419 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

SAAMA SOLUTION AS

Org. no. 930697419 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 11,000
Operating profit NOK −5,000
Equity NOK 17,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SAAMA SOLUTION AS is registered as a limited company in Oslo, Oslo with organisation number 930697419. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “IT-tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 11,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 11,000
Operating profit
NOK −5,000
Equity
NOK 17,000
Est. value
NOK 19,000

Financial health · 2024

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

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

Who owns SAAMA SOLUTION AS?

OUSMAN TOURAY
SAAMA SOLUTION AS
NOK 11,000 rev. · NOK −5,000 profit

SAAMA SOLUTION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAAMA SOLUTION AS

Who owns SAAMA SOLUTION AS?

OUSMAN TOURAY is the largest registered owner, with 100.0%.

What is the revenue of SAAMA SOLUTION AS?

SAAMA SOLUTION AS had revenue of NOK 11,000 in 2024.

Who is the general manager of SAAMA SOLUTION AS?

Ousman Touray is registered as general manager of SAAMA SOLUTION AS.

Where is SAAMA SOLUTION AS based?

SAAMA SOLUTION 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.