BIZTRAC BETA
Combined facilities support activities

SPORTSTAD AUTO AS

Org. no. 812784412 Limited company (AS) Lillestrøm Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −59,000
Incorporated 2013
Share capital NOK 170,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−59k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

SPORTSTAD AUTO AS is registered as a limited company in Lillestrøm, Akershus with organisation number 812784412. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2013. Registered share capital is NOK 170,000, divided into 2000 shares. The company's stated purpose is: “Eksport og import av varer og tjenester, kjøp og salg av biler, samt virksomhet som står i naturlig sammenheng med dette, herunder utleie av biler.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK −59,000

Financial health · 2024

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

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

Who owns SPORTSTAD AUTO AS?

NICK GHOOCHANI NEJAD
SPORTSTAD AUTO AS
· NOK −5,000 profit

SPORTSTAD AUTO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPORTSTAD AUTO AS own?

SPORTSTAD AUTO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPORTSTAD AUTO AS

Who owns SPORTSTAD AUTO AS?

NICK GHOOCHANI NEJAD is the largest registered owner, with 100.0%.

Who is the general manager of SPORTSTAD AUTO AS?

Nick Ghoochani Nejad is registered as general manager of SPORTSTAD AUTO AS.

Where is SPORTSTAD AUTO AS based?

SPORTSTAD AUTO AS has its business address in Strømmen.

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.