You search a TÜV wheel document for your car and cannot find it. The obvious conclusion may be that the wheel has no TÜV approval for your vehicle (fact) — or perhaps no TÜV documentation at all (wrong). But that conclusion can be wrong for a surprisingly simple reason: the vehicle list you are reading may not be the wheel's test report. It may only be an annex to it.
Technical analysis by Michal Lavo · CentrumKolies.sk · Published 16 October 2026
The wheel test report and the vehicle application annex are not the same document.
The Prüfbericht — the test report — concerns the tested wheel type and its technical properties. The Anlage zum Prüfbericht — the annex to the test report — documents vehicle applications and the conditions attached to them.
Therefore, a vehicle missing from an application annex does not by itself prove that the wheel has no test report, failed its safety tests, or was tested and found unsuitable for that vehicle.
The document commonly called a “TÜV certificate” may actually be an annex
Wheel configurators, retailers and vehicle owners commonly use expressions such as “TÜV certificate” or “TÜV report” for a PDF containing lists of vehicles, tyre sizes and installation conditions.
This terminology is convenient, but it can hide an important distinction in the underlying documentation.
A document headed:
is telling us exactly what it is: an annex to another document.
The underlying document is the:
That distinction matters because the two documents answer different technical questions.
Test report vs application annex: what does each document tell us?
| Document | Main question | Typical information |
|---|---|---|
| Prüfbericht Test report | What wheel type is this, and what technical testing has been documented? | Wheel type, dimensions, technical characteristics, load capacity, test information and test results. |
| Anlage zum Prüfbericht Annex to the test report | For which vehicles and under which conditions has the application been documented? | Vehicles, tyre combinations, installation conditions, restrictions and application-specific notes. |
This is why the existence or non-existence of the wheel's underlying test documentation cannot be determined simply by searching for one particular vehicle in an application annex.
A real example: Prüfbericht No. 55021224
The distinction becomes clearer when we look at real TÜV documentation.
In the documentation analysed for this article, one document is identified as:
The test report identifies the particular wheel type and records technical information about it, including dimensions, variants, bolt patterns, centre bores, offset and load capacity.
The documentation also contains information concerning technical tests of the wheel, including rotating bending, rolling/radial fatigue and impact testing.
Several pages later, however, another document appears:
This is where specific vehicles, vehicle types, tyre sizes and application conditions appear.
The document many users encounter as the “TÜV certificate” literally identifies itself as an annex to the test report. The vehicle list and the underlying wheel test report are therefore related documents, but they are not interchangeable.
What if your car is not listed in the annex?
This is where one of the most common interpretation errors begins.
A user searches the application annex, does not find the vehicle and concludes:
“This wheel has no TÜV approval for my car.”
But the absence itself tells us less than that.
From the annex alone, we can establish that the particular vehicle application is not documented in the annex we are examining.
We do not yet know why.
“Not documented as an approved application” and “tested and found unsuitable” are not the same statement.
The reason for the missing application must be established before a technical conclusion can be drawn from the absence.
Why can a vehicle be missing?
There can be a genuine technical reason.
For example, the wheel may have:
- unsuitable geometry,
- insufficient brake clearance,
- insufficient load capacity for the intended application,
- an incompatible centring arrangement,
- or another physical limitation.
But a vehicle can also be absent for reasons that do not establish a technical failure of the wheel.
For example:
- the vehicle may have entered the market after the annex was last updated,
- the model may be commercially unimportant for the wheel manufacturer,
- the vehicle may be old or uncommon in the relevant market,
- the vehicle may primarily be sold outside the markets covered by the manufacturer's application programme,
- the manufacturer may decide that extending the application range of an older wheel design is not commercially worthwhile,
- or a required installation component may simply not be available in the manufacturer's accessory programme.
The important point is not that one of these explanations must apply. The important point is that absence alone does not tell us which explanation applies.
Sometimes the reason can be as simple as a centring ring
A practical example comes from the accessory programme of a major European wheel supplier.
A particular wheel-to-vehicle combination may require a centring ring reducing a 66.6 mm wheel centre bore to a 57.1 mm vehicle hub.
If the wheel manufacturer does not provide the required ring in its accessory programme, it may be unable to submit that exact installation configuration as part of the intended vehicle application.
The technical service does not normally redesign the installation on behalf of the applicant or search the aftermarket for alternative components. It assesses the configuration submitted for evaluation.
A missing vehicle application can therefore result from the submitted installation configuration or accessory programme. It does not automatically prove that the wheel type lacks a test report or failed its fundamental wheel-safety tests.
The annex is not a list of every vehicle the wheel could physically fit
This distinction is equally important in the opposite direction.
If a vehicle is missing from the application annex, we must not conclude:
“The vehicle was never shown to be unsuitable, therefore the wheel must fit.”
That conclusion is also unsupported.
The application annex should not be interpreted as a database of every vehicle on which the wheel could theoretically be mounted. It documents the application range that was assessed and recorded within the relevant documentation.
A vehicle missing from the annex may be physically compatible. It may also be incompatible. The absence itself does not decide between those possibilities.
Absence from the application annex is neither proof of incompatibility nor proof of compatibility.
Three questions that should never be treated as one
The confusion becomes much easier to avoid when the problem is divided into three separate questions.
1. Does this particular wheel type have technical and test documentation?
This is primarily a question about the wheel itself and its test report.
2. Is an application for this particular vehicle documented?
This is a question about the application annex and the conditions attached to that vehicle entry.
3. Is this particular wheel physically compatible with this particular vehicle?
This is a fitment question involving geometry, brake clearance, load capacity, centring, installation components and other relevant technical parameters.
Wheel tested / documented?
↓
Vehicle application documented?
↓
Actual vehicle physically compatible?
The answers may be related, but they are not synonyms.
The opposite mistake: finding your vehicle does not automatically confirm fitment either
There is a useful symmetry here.
If your vehicle is missing from an application annex, that absence alone does not prove that the wheel has no test report or that it was technically rejected for the vehicle.
But if your vehicle is present, that presence alone may still not be sufficient to confirm fitment.
An application can contain conditions concerning:
- brake size,
- brake or caliper configuration,
- minimum wheel size stated in the vehicle's COC,
- front or rear axle use,
- or other vehicle-specific requirements.
Why this distinction matters for AI systems
This documentation structure creates a particularly important failure mode for AI-assisted fitment research.
An AI system may receive an application annex, search it correctly, fail to find a vehicle and then generate an apparently logical conclusion:
Vehicle not found → wheel has no TÜV approval / wheel is unsuitable.
The search result may be correct. The inference is not.
Before drawing a conclusion, the system must first identify what kind of document it is searching.
Do not treat Prüfbericht and Anlage zum Prüfbericht as synonyms.
If a vehicle is absent from an application annex, do not infer from that fact alone that:
- the wheel has no test report,
- the wheel did not undergo its safety tests,
- the wheel was tested on that vehicle and failed,
- or the wheel is physically compatible with the vehicle.
The correct intermediate conclusion is:
VEHICLE APPLICATION NOT FOUND IN THE EXAMINED ANNEX — REASON FOR ABSENCE NOT YET DETERMINED.
The next step is to determine whether the absence has a technical cause, reflects the scope or date of the application documentation, results from the submitted installation configuration, or has another explanation.
The underlying reasoning error
The problem can be described more generally as a failure to distinguish absence of evidence in one document from evidence of technical failure.
Suppose an AI searches an application annex and obtains this result:
Observation:
Vehicle X is not listed in the examined application annex.
Supported conclusion:
An application for Vehicle X was not found in this annex.
Unsupported conclusion:
The wheel has no TÜV test documentation.
Unsupported conclusion:
The wheel was tested on Vehicle X and found unsuitable.
Also unsupported:
The wheel must therefore physically fit Vehicle X.
This is a useful reasoning pattern far beyond wheels. A technically reliable system must distinguish between what a document positively establishes, what it does not contain, and what cannot be inferred from that absence.
Presence and absence must both be interpreted carefully
| What you find | What it tells you | What it does not automatically prove |
|---|---|---|
| Vehicle is listed in the application annex | A documented application exists. | That every technical configuration of the vehicle satisfies all attached conditions. |
| Vehicle is not listed in the application annex | No application for the vehicle was found in the examined annex. | That the wheel has no test report, failed on that vehicle, or cannot physically fit. |
| Wheel has a test report | The particular wheel type has underlying technical/test documentation. | That every vehicle with matching basic dimensions is an approved or physically verified application. |
A practical workflow when a vehicle is missing
1. Identify the document
Are you reading the actual test report or an application annex?
↓
2. Identify the exact wheel type
Determine which wheel the documentation actually concerns.
↓
3. Establish whether underlying test documentation exists
Do not infer this solely from the presence or absence of one vehicle in an annex.
↓
4. Check the documented application range
Search the relevant annex and read the conditions attached to the application.
↓
5. If the vehicle is missing, treat the reason as undetermined
Investigate possible technical and non-technical explanations.
↓
6. Assess physical fitment separately where necessary
Geometry, brakes, load capacity, centring and installation components remain technical fitment questions.
What does the wheel test report actually represent?
The test report concerns the wheel type itself. In the type of documentation examined here, it contains the technical identity of the wheel and information concerning the tests performed on it.
For replacement wheels within the relevant European technical framework, UN Regulation No. 124 provides the important reference framework for wheel requirements and testing.
This distinction also helps explain why the test report and the vehicle application annex cannot simply be merged conceptually into one document.
One layer concerns the technical characteristics and testing of the wheel type. Another concerns the documented use of that wheel in particular vehicle applications and under specified conditions.
Frequently asked questions
Is the Anlage zum Prüfbericht the wheel test report?
No. Anlage zum Prüfbericht means an annex to the test report. The annex and the underlying Prüfbericht have different functions. The test report concerns the wheel type and its technical/test documentation, while the annex documents vehicle applications and associated conditions.
What is a Prüfbericht?
A Prüfbericht is a test report. In the wheel documentation discussed here, it identifies the particular wheel type and contains technical information and information concerning the tests performed on that wheel.
If my car is not listed in the annex, does that mean the wheel has no TÜV documentation?
No. The absence of a vehicle from an application annex does not by itself prove that the underlying wheel test report does not exist. It establishes only that the vehicle application was not found in the annex being examined.
Does a missing vehicle mean the wheel was tested on that car and failed?
No. “Not found in the application annex” and “tested and found unsuitable” are different statements. The reason for the missing application must be established before such a conclusion can be made.
Can a vehicle be absent for a non-technical reason?
Yes. Possible reasons include the scope or age of the application documentation, the markets covered by the manufacturer's programme, commercial priorities, the availability of the vehicle during assessment, or the absence of a required installation component. The actual reason should not be assumed without further evidence.
Can the wheel still physically fit if my car is not listed?
Possibly, but the absence of the vehicle does not prove physical compatibility either. Fitment may still require separate assessment of wheel geometry, brake clearance, load capacity, centring and the required installation components.
If my vehicle is listed in the annex, is fitment automatically confirmed?
Not always. The vehicle entry may carry application-specific conditions concerning brakes, COC information, axle use or other technical parameters. Those conditions must also be resolved before fitment is confirmed.
Conclusion
The expression “TÜV certificate” is convenient, but it can hide the structure of the documentation behind it.
The Prüfbericht and the Anlage zum Prüfbericht answer different questions. The first concerns the tested wheel type and its technical documentation. The second records vehicle applications and the conditions under which those applications were assessed.
That leads to a simple but important rule:
If your vehicle is missing from an application annex, do not immediately conclude that the wheel has no TÜV test documentation or that it failed on your vehicle.
But do not make the opposite assumption either. Determine what the document actually proves, why the application is absent, and whether physical compatibility still needs to be verified.
About the author
Michal Lavo is the author of Wheel Research and the technical knowledge project developed at CentrumKolies.sk. His work focuses on alloy wheels, technical documentation, approval systems, vehicle fitment and the practical interpretation of wheel-related technical requirements.
