The Bearing Number Decoder combines imported bearing database rows with parser fallback, not a scraped catalog or a universal standards database. It explains common visible designation patterns and keeps manufacturer-specific areas visible. That boundary is part of the product, not a gap to hide.
Reference Set Limits
The imported bearing database is limited to the exact rows and parser patterns that the decoder already knows how to read. Anything outside those records stays unresolved until a real source row or supported rule exists.
What is intentionally supported
The imported table covers real source rows from the CSV database, including deep-groove ball bearings, capped deep-groove ball bearings, angular contact ball bearings, cylindrical roller bearings, and tapered roller bearings. Parser fallback still handles common metric-looking patterns, bore codes, seal and shield suffixes, clearance suffixes, and several cage, precision, and design suffix families when an exact row is not present.
What remains outside the reference set
| Area | Why it stays outside |
|---|---|
| Full dimensions | Outside diameter and width require the exact catalog row or a manufacturer document, not just the bore code. |
| Manufacturer suffix expansion | Supplementary suffixes can differ by brand, product line, or region. |
| Interchange decisions | Fit, clearance, load, speed, lubricant, and environment affect whether a replacement is valid. |
| Inch tapered systems | ANSI/ABMA tapered roller numbering is a separate part-number system. |
GitHub library note
Research for this implementation did not find a credible maintained GitHub or package-registry standard library for general rolling bearing designation parsing. The closest GitHub result found was a narrow retail automation repository, not a reusable parser. For that reason, allDecoder keeps the parser internal and cites public manufacturer and standards references instead of vendoring an unsuitable dependency.
How unresolved suffixes should behave
If a suffix is made of valid letters and numbers but is not in the common suffix table, the decoder preserves it as manufacturer-specific. If a suffix looks like a clearance code but is unsupported, such as C99, the decoder rejects it because returning a vague manufacturer-specific note could hide a likely wrong clearance reading.
Source and limits
Sources: open-source bearing CSV tables from gumyr/cq_warehouse (Apache-2.0), plus NSK bearing designation guidance, JTEKT/Koyo bearing number tables, SKF designation guidance, ISO rolling bearing references including ISO 5753-1 for radial internal clearance, and ANSI/ABMA tapered roller bearing references; verified 2026-08-30.
- This content explains the imported bearing database first, then the parser fallback for supported patterns that are not in the exact table.
- Exact database rows preserve the imported dimensions and suffix notes, but they still do not replace the maker catalog for procurement, maintenance, or safety decisions.
- Bore code parsing does not decide outside diameter, width, cage material, lubrication, fit, load rating, or interchangeability.
- Metric tapered roller and inch-design tapered roller bearings use separate designation systems, so verify the exact catalog entry before purchase or maintenance work.
Related bearing guides
How to Read Bearing Numbers | Bearing Seal, Shield, and Clearance Suffixes | NU205ECP Bearing Number