biztrac. BETA
COMPANY REGISTER PROFILE
828318772 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other machinery and equipment

S.CHACHA AS

Org. no. 828318772 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 503,000
Operating profit NOK 351,000
Equity NOK 498,000
Incorporated 2021
Share capital NOK 50,000

Signals

1 flags
  • Nylig endring 2026-07-15 Adresseendring registrert 2026-07-15.

S.CHACHA AS is registered as a limited company in Oslo, Oslo with organisation number 828318772. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Investere i verdipapirer, eie aksjer i andre selskaper samt konsulentbistand og annen virksomhet med naturlig forbindelse til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 503,000 in revenue and NOK 351,000 in operating profit.

Key figures · 2025

Revenue
NOK 503,000
▲ +74 %
Operating profit
NOK 351,000
▲ +220 %
Equity
NOK 498,000
▲ +118 %
Est. value
NOK 962,000

Financial health · 2025

Liquidity
6.35
Very good
Current assets ÷ current liabilities
Profitability
31.3%
Very good
Return on total assets
Solidity
34.7%
Good
Equity as a share of total capital

Who owns S.CHACHA AS?

S.CHACHA AS has 6 registered shareholders:

All shareholders and roles →

Which companies does S.CHACHA AS own?

S.CHACHA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about S.CHACHA AS

Who owns S.CHACHA AS?

Abbas Sikandarali Fazal is the largest registered owner, with 41.5%.

What is the revenue of S.CHACHA AS?

S.CHACHA AS had revenue of NOK 503,000 in 2025.

Where is S.CHACHA AS based?

S.CHACHA 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.