BIZTRAC BETA
Repair and maintenance of motor vehicles

AUTO CHECK AS

Org. no. 971002921 Limited company (AS) Stavanger Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 295,000
Operating profit NOK −354,000
Equity NOK 4.2m
Incorporated 1994
Share capital NOK 100,000

Signals

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

AUTO CHECK AS is registered as a limited company in Stavanger, Rogaland with organisation number 971002921. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og stå for drift av bilvrksted, og å drive handel fra denne eiendom samt hva herved står i forbindelse, herunder å delta i andre selskaper av lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 295,000 in revenue and NOK −354,000 in operating profit.

Key figures · 2024

Revenue
NOK 295,000
Operating profit
NOK −354,000
Equity
NOK 4.2m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns AUTO CHECK AS?

GÜLSEN AKIN
AUTO CHECK AS
NOK 295,000 rev. · NOK −354,000 profit

AUTO CHECK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AUTO CHECK AS

Who owns AUTO CHECK AS?

GÜLSEN AKIN is the largest registered owner, with 50.0%.

What is the revenue of AUTO CHECK AS?

AUTO CHECK AS had revenue of NOK 295,000 in 2024.

Who is the general manager of AUTO CHECK AS?

Resul Pektas is registered as general manager of AUTO CHECK AS.

Where is AUTO CHECK AS based?

AUTO CHECK AS has its business address in Stavanger.

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.