BIZTRAC BETA
Wholesale of information and communication equipment

SAAKK AS

Org. no. 927070057 Limited company (AS) Sarpsborg Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 170,000
Operating profit NOK −13,000
Equity NOK 3.0m
Incorporated 2021
Share capital NOK 30,000

Signals

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

SAAKK AS is registered as a limited company in Sarpsborg, Østfold with organisation number 927070057. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å investere i og delta i andre selskaper med et hvilket som helst formål, samt yte tjenester i forbindelse med investeringsvirksomhet og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 170,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 170,000
Operating profit
NOK −13,000
Equity
NOK 3.0m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns SAAKK AS?

SEBASTIAN ÅDALEN
SAAKK AS
NOK 170,000 rev. · NOK −13,000 profit

SAAKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAAKK AS own?

SAAKK AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SAAKK AS

Who owns SAAKK AS?

SEBASTIAN ÅDALEN is the largest registered owner, with 100.0%.

What is the revenue of SAAKK AS?

SAAKK AS had revenue of NOK 170,000 in 2024.

Where is SAAKK AS based?

SAAKK AS has its business address in Sarpsborg.

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.