π Dataset at a Glance
Dataset period: 18 August – 26 September 2026 · Q3 2026 snapshot · Published September 2026
| Metric | Result |
|---|---|
| Service requests reviewed | 34 |
| Reporting period | 18 August β 26 September 2026 |
| Countries represented | 19 |
| Repair shops | 23 (68%) |
| Vehicle owners | 9 (26%) |
| Dealers / 4S stores | 2 (6%) |
| Software-related requests | 16 (47%) |
| Fault repair requests | 11 (32%) |
| Fault diagnosis requests | 5 (15%) |
| Other service requests | 2 (6%) |
π What We Analyzed
This article is based on service requests submitted through the NEV Fix remote support request form. Before writing anything, we cleaned the dataset:
- The database contained 55 request records in total.
- 21 records were removed as internal test submissions, identified by test names, command-line user agents, loopback IP addresses, placeholder VINs and internal contact numbers.
- 34 genuine requests remained, received between 18 August and 26 September 2026.
One limitation should be stated at the start. The request table records what customers asked for. It does not store repair outcomes, resolution rates or commercial results. Every case below is therefore described as a service request or diagnostic case, not as a completed repair, unless the request itself documented an outcome.
Two of the 34 requests concerned a non-Chinese model, a Chevrolet Spark EV. They are included in the totals because they arrived through the same form, and we note them here rather than quietly dropping them.
We also removed all identifying information. No VIN, customer name, phone number, email address, workshop name or precise location appears anywhere in this article.
π§Ύ What the 34 Requests Included
Broken down by the service category selected in the request form:
| Request type | Cases | Share |
|---|---|---|
| Software Service | 16 | 47% |
| Fault Repair | 11 | 32% |
| Fault Diagnosis | 5 | 15% |
| Other Service | 2 | 6% |
| Total | 34 | 100% |
Who submitted the requests
| Submitter | Cases | Share |
|---|---|---|
| Repair shop | 23 | 68% |
| Vehicle owner | 9 | 26% |
| Dealer / 4S store | 2 | 6% |
Repair shops submitted roughly two thirds of the requests in this dataset. That matters for anyone building service capability outside China: in this dataset, most requests came from professional workshops rather than private owners.
Where the requests came from
The 34 requests came from 19 countries. The largest single country group was Russia with 9 requests. Seven countries contributed two requests each, and a further eleven countries contributed one request each.
Russia accounted for 9 of the 34 requests (26%), while the remaining requests were distributed across 18 other countries. No other country contributed more than two requests.
On geographic distribution: this spread reflects where NEV Fix currently receives requests. It is not a measurement of where Chinese vehicles are sold, and it should not be read as a national market ranking.
Which vehicles appeared
More than a dozen Chinese vehicle brands appeared in the dataset. The most frequently represented brand was Zeekr with 6 requests, followed by Leapmotor and BYD with 3 requests each.
No single brand dominated the dataset. Zeekr's six requests were the largest single group, and several other brands appeared only once or twice.
What diagnostic hardware was already available
The request form asks whether the submitter has an ENET diagnostic cable and a Smartlink-C interface. The answers show a clear split:
| Hardware | Available | Not available | Not sure |
|---|---|---|---|
| ENET cable | 24 (71%) | 5 (15%) | 5 (15%) |
| Smartlink-C | 13 (38%) | 17 (50%) | 4 (12%) |
Read carefully, this does not say that overseas workshops lack diagnostic capability. It says the capability is unevenly equipped. Most submitters had an ENET cable. Only about a third had Smartlink-C, and half stated clearly that they did not.
π» Software Support Was as Common as Repair and Diagnosis Combined
This is the finding we did not expect when we started reviewing the data.
Requests classified as Software Service accounted for 16 of the 34 requests (47%). Fault repair accounted for 11 requests and fault diagnosis for 5 requests β also 16 combined.
In other words, in this six-week sample, the number of software-related support requests was equal to the number of fault-repair and fault-diagnosis requests combined. We are not claiming that software problems outnumber hardware problems in the wider market. We are reporting what appeared in requests sent to NEV Fix during this period.
Software Service was the largest single request category in this dataset. We analysed those 16 requests separately in Chinese EV Software Support: 16 Real Overseas Service Requests.
Seven requests explicitly selected "Software Update" in the form. After reviewing the free-text descriptions, we identified roughly ten requests involving OTA or broader system-update issues. These two figures differ because the form category and the written description capture slightly different things, and we have labelled the second figure as an approximation.
What the software requests were actually about
Based on our manual review of the request descriptions, the software-related cases grouped into these areas:
| Request area | Approximate cases |
|---|---|
| OTA and system updates | ~10 |
| Keys, accounts and mobile apps | 4 |
| Language and interface localization | 4 |
| Configuration after component replacement | 2 |
| Navigation, time settings and other | 2 |
These areas are not mutually exclusive. A single request may appear in more than one area, so the counts above do not add up to the 16 software-related requests. The OTA figure is an approximation, because several requests described update-related symptoms without selecting the software category in the form.
These groups were produced by reading the request text, not by a database field. We have marked them as approximate for that reason.
π οΈ Five Real Problems We Saw
Aggregate numbers only go so far. These five requests show the range of problems that appear in the dataset. All identifying details have been removed.
1. A replacement OBC that still needed vehicle matching β SAIC Rising R7, Russia
A repair shop in Russia submitted a request about an SAIC Rising R7 that would not charge. The workshop reported that the on-board charger had been replaced with a used unit, and that the replacement unit needed to be linked to the vehicle before charging would work.
What makes this request useful is its shape. The mechanical repair was already done. The remaining problem was vehicle-level configuration β getting the car to accept a component that had come from another vehicle.
2. Configuration loss after an interrupted software operation β Geely Lynk & Co Z10, Central Asia
A workshop in Central Asia requested help recovering the vehicle configuration on a Geely Lynk & Co Z10. According to the request, the central screen began repeatedly rebooting and several vehicle functions stopped working after an unsuccessful software update. The workshop had official diagnostic software and confirmed it could connect to the vehicle normally.
The request specifically asked NEV Fix to diagnose and recover the configuration before flashing any control unit. That sequencing is worth noting: the customer's priority was recovery of the existing configuration, not replacement of hardware.
3. Intermittent propulsion loss with Hall sensor codes β BYD Seal 05 DM-i, Iraq
A repair shop in Iraq submitted a request about a 2025 BYD Seal 05 DM-i that lost propulsion after five to ten minutes of driving, displaying a "check power system" warning. The stored fault codes pointed to the front drive motor controller current Hall sensors:
- P1BC900 β front drive motor controller current Hall sensor A fault
- P1BC500 β front drive motor controller current Hall sensor B fault
- P2B5700 β front motor system fault
The workshop noted that the Hall sensor faults appeared as historical even when scanned immediately after shutdown. It asked for sensor location, wiring information and the official BYD diagnostic procedure.
We are publishing this as a diagnostic request, not as a resolved repair. A related case covering a different fault on the same model is documented in our BYD Seal 05 charging fault case from Iraq.
4. A battery temperature fault that moved between modules β Skywell BE11, South Asia
A workshop in South Asia submitted a request about a Skywell BE11 showing battery temperature imbalance. The request described something more specific than a simple sensor failure: the maximum temperature reading moved between different battery modules over time.
The workshop had already done substantial work before contacting NEV Fix. Temperature sensors had been swapped and tested. Sensor resistance was normal. Wiring and connector continuity were normal. After one sensor was replaced, the original module returned to normal β but a different module later showed high temperature.
The question the workshop asked was precise: is the fault in the temperature sensor circuit, the cell monitoring unit, or the BMS itself?
5. A replaced inverter that did not end the diagnosis β Dongfeng Fucang ES600, Russia
A repair shop in Russia submitted a request about a Dongfeng Fucang ES600 that arrived unable to run and not detecting the battery. The workshop replaced the inverter. After replacement, the vehicle detected the battery but still would not start, and there were fault codes the workshop could not interpret with its available diagnostic equipment.
This request illustrates a common pattern in the dataset: the workshop had already replaced the inverter, but the vehicle still would not start because the remaining fault codes required further diagnostic interpretation beyond what the workshop's available equipment could provide.
π What This Dataset Shows
Read as a whole, the 34 requests suggest that overseas service demand for Chinese vehicles is broader than conventional fault repair. Across this sample we saw:
- Software and configuration work appeared alongside conventional repair. Sixteen of 34 requests were software-related β the same number as fault repair and fault diagnosis combined.
- Component replacement often did not finish the job. In several requests, replacing a component was not the end of the diagnostic process. The remaining issue involved vehicle-level configuration, component matching or fault-code interpretation.
- Workshops were the main requesters. Twenty-three of 34 requests came from repair shops, not private owners.
- Diagnostic capability was uneven rather than absent. Most submitters had an ENET cable; far fewer had Smartlink-C.
- Demand was spread across many brands and countries. No single brand or country dominated this sample.
Within this dataset, the requests were often not simply about a vehicle being broken. Several involved a vehicle that had already been repaired, replaced or updated, with the remaining issue involving software, configuration or diagnostic interpretation. These are the types of cases for which NEV Fix provides remote diagnostic support.
When a diagnosis points to a failed or replacement component, the next step is usually confirming the correct part before sourcing it. NEV Fix's Parts Lookup lets workshops check Chinese vehicle parts by model and part information.
βοΈ What This Small Dataset Cannot Tell Us
We want to be explicit about the limits of this data, because reading it correctly matters more than reading it impressively:
- It is not a market survey. These are requests received by NEV Fix. They are not a statistically representative sample of all Chinese vehicles overseas.
- It cannot establish failure rates by brand or model. The dataset is far too small, and the counts are affected by where NEV Fix already has customers and visibility.
- It does not show outcomes. The request table records what customers asked for, not what was resolved.
- Six weeks is a short window. Seasonal and regional variation is not captured.
- Category boundaries are imperfect. A request logged as "Software Service" may still involve hardware, and the sub-groupings above are our manual reading of the text rather than database fields.
These limits matter because the dataset describes NEV Fix's incoming service requests, not the wider Chinese EV market. That is what allows another workshop to use the numbers properly.
π§ How Overseas Workshops Can Prepare
If your workshop is working on Chinese-brand electric and hybrid vehicles without local dealer support, three things reduce the time lost on difficult jobs:
- Capture diagnostic data before replacing parts. Several requests in this dataset arrived after a component had already been replaced, with the remaining issue requiring further diagnosis or configuration.
- Check that your diagnostic hardware matches the vehicle. ENET coverage was common in this sample; Smartlink-C coverage was not. Our workshop equipment guide lists what is typically needed.
- Know when to bring in remote support. Fault codes that cannot be interpreted, configuration work after module replacement, and software-state problems are among the situations where remote diagnostic support may be useful.
NEV Fix runs remote diagnostic sessions using the vehicle's own diagnostic interface and the workshop's existing equipment. If a session identifies a hardware fault, we can also support parts sourcing, and longer-term capability building through our EV repair training programmes, including a dedicated battery repair course.
You can browse further first-hand cases in our tech blog, including the GAC Trumpchi S7 remote diagnosis case from Russia, the Li Auto L9 module failure following an OTA update and the Zeekr region lock case study.
β Frequently Asked Questions
How many overseas service requests did NEV Fix analyze?
34 genuine service requests, received between 18 August and 26 September 2026. A further 21 internal test records were removed from the database before analysis.
What share of the requests were software-related?
16 of the 34 requests (47%) were software-related. That is the same number as fault-repair requests (11) and fault-diagnosis requests (5) combined.
Who submits most Chinese EV remote support requests?
In this dataset, repair shops submitted 23 of the 34 requests (68%). Vehicle owners submitted 9 and dealer or 4S store staff submitted 2.
Do overseas workshops have the right diagnostic equipment?
Availability was uneven. ENET cables were reported as available in 24 of 34 requests (71%), while Smartlink-C was available in 13 (38%) and stated as unavailable in 17 (50%).
Can remote support help with software and configuration problems?
Yes. Configuration recovery after module replacement, software-state diagnosis and fault-code interpretation were among the request types in this dataset. Sessions run through the workshop's own equipment and the vehicle's diagnostic interface.
Does this data represent the global Chinese EV market?
No. It is a snapshot of service requests received by NEV Fix during a defined reporting period. It is not a statistically representative market survey and cannot establish failure rates by brand or model.
What Chinese EV brands appeared in the requests?
More than a dozen Chinese vehicle brands appeared in the 34-request dataset. Zeekr was the most frequently represented with six requests, followed by Leapmotor and BYD with three requests each. Several other brands appeared only once or twice.
What kinds of software issues appeared in the requests?
The software-related requests included OTA and system-update issues, keys and mobile apps, language and interface localization, configuration after component replacement, and navigation or time-setting issues. The categories overlap because some requests involved more than one issue.
Working on a Chinese EV Your Workshop Cannot Fully Diagnose?
NEV Fix runs remote diagnostic sessions using your existing workshop equipment and the vehicle's own diagnostic interface. Send us the vehicle details and the symptoms β we will tell you what data to capture first.