Metric Tire Size Comparison

How to use Metric Tire Size Comparison

Enter a baseline short radial size code and candidate codes, plus an indicated speed label. Width, aspect and rim dimensions produce the nominal diameter; the comparison keeps exact dimensional differences and ideal candidate/baseline speed ratios without treating them as a replacement recommendation.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Enter a baseline short radial size code and candidate codes, plus an indicated speed label. Width, aspect and rim dimensions produce the nominal diameter; the comparison keeps exact dimensional differences and ideal candidate/baseline speed ratios without treating them as a replacement recommendation.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• Up to 30 candidates. Short ASCII metric radial codes only: optional P/LT prefix, width 50–500 mm, aspect 1–100%, and rim 5–30 inches in whole/half increments. No service suffix, load/speed index, ZR, flotation notation or fitment validation. Indicated speed 0–1,000 in your selected km/h or mph label; no actual speed measurement.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.