biztrac. BETA
COMPANY REGISTER PROFILE
920239692 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

CAROID AS

Org. no. 920239692 Limited company (AS) Indre Østfold Incorporated 2018 Active
Revenue 2025 NOK 387,000
Operating profit NOK −53,000
Equity NOK −111,000
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−111k kr).

CAROID AS is registered as a limited company in Indre Østfold, Østfold with organisation number 920239692. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg og utleie av nye og brukte kjøretøy, og alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 387,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 387,000
▲ +617 %
Operating profit
NOK −53,000
▲ +5 %
Equity
NOK −111,000
▼ −86 %

Financial health · 2025

Liquidity
-9.93
Not satisfactory
Current assets ÷ current liabilities
Profitability
-191.4%
Not satisfactory
Return on total assets
Solidity
-841.7%
Weak
Equity as a share of total capital

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

Who owns CAROID AS?

CAROID AS
NOK 387,000 rev. · NOK −53,000 profit

CAROID AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAROID AS

Who owns CAROID AS?

Gursharnbir Singh Sohal is the largest registered owner, with 50.0%.

What is the revenue of CAROID AS?

CAROID AS had revenue of NOK 387,000 in 2025.

Who is the general manager of CAROID AS?

Sukhbir Singh Sohal is registered as general manager of CAROID AS.

Where is CAROID AS based?

CAROID AS has its business address in Askim.

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.