BIZTRAC BETA
Other captive investment companies

SS SIDHU INVEST AS

Org. no. 919817259 Limited company (AS) Lillestrøm Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK −788,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−788k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

SS SIDHU INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 919817259. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer og fast eiendom samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK −788,000

Financial health · 2025

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

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

Who owns SS SIDHU INVEST AS?

SURINDER SINGH SIDHU
SS SIDHU INVEST AS
· NOK −3,000 profit

SS SIDHU INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SS SIDHU INVEST AS own?

SS SIDHU INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SS SIDHU INVEST AS

Who owns SS SIDHU INVEST AS?

SURINDER SINGH SIDHU is the largest registered owner, with 100.0%.

Who is the general manager of SS SIDHU INVEST AS?

Surinder Singh Sidhu is registered as general manager of SS SIDHU INVEST AS.

Where is SS SIDHU INVEST AS based?

SS SIDHU INVEST AS has its business address in Lillestrøm.

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.