Mechanical decoder
Bearing Number Decoder
Match common rolling bearing designations against the imported bearing database and fall back to parser rules for unsupported rows.
Inputs
Results
- Decoded result
- Waiting for input
- Confidence
- Waiting for input
Segment breakdown
Matched fields
Use the Bearing Number Decoder to match a real bearing designation against the imported production table first. If the exact row is not present, the decoder falls back to parser rules for common basic designations, bore codes, seals, shields, clearance suffixes, and manufacturer-specific suffix boundaries.
Example database rows
| Input | What the decoder returns |
|---|---|
| NU205ECP | Cylindrical roller bearing, 25 mm bore, 52 mm outside diameter, 15 mm width, ECP suffix. |
| 623-2Z | Deep-groove ball bearing, 3 mm bore, 10 mm outside diameter, 4 mm width, two metal shields. |
| 7200 BECBP | Angular contact ball bearing, 10 mm bore, 30 mm outside diameter, 9 mm width, BECBP suffix. |
| NJ 202 ECP | Cylindrical roller bearing, 15 mm bore, 35 mm outside diameter, 11 mm width, ECP suffix. |
| 30302 J2 | Tapered roller bearing, 15 mm bore, 42 mm outside diameter, 14.25 mm thickness, J2 suffix. |
| E2.608-2Z | Capped deep-groove ball bearing, 8 mm bore, 22 mm outside diameter, 7 mm width, two metal shields. |
How to enter a bearing number
- Enter the complete visible designation, including letters, numbers, seals, shields, clearance, and design suffixes.
- Keep suffixes attached or separated by spaces or hyphens. For example, 6205 ZZ is normalized like 6205-ZZ.
- Read the decoded summary first, then inspect the segment breakdown and reference rows.
- If the decoder returns an exact database row, treat that as a source-backed reference row and still verify the manufacturer catalog before acting.
Output fields
| Output field | What it means |
|---|---|
| Decoded result | Plain-language reading of the exact database row or supported parser pattern. |
| Confidence | A reminder that this is a source-backed lookup or parser read, not an official catalog record. |
| Segment breakdown | Rows for bearing type, series or base, bore code, seal or shield suffixes, clearance suffixes, and unresolved manufacturer-specific suffixes. |
| Reference table | The row source or parser rule behind each decoded field, including bore code and suffix caveats. |
What the parser can and cannot decide
The parser can still read common patterns such as 60, 62, 63, 64, 68, and 69 deep-groove ball bearings; NU, NJ, NUP, N, and NF cylindrical roller bearings; 302, 303, 320, 322, and 323 tapered roller patterns; and 222, 223, 230, 231, and related spherical roller patterns. It cannot produce a full bearing catalog page, certified dimensions, fit recommendation, interchange approval, load rating, or complete manufacturer suffix interpretation.
Sources 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. GitHub and package-registry searches did not reveal a credible maintained general-purpose bearing designation parser library, so this implementation keeps the parser internal and layers it behind the imported database.
Limits: The exact database rows are source-backed reference entries, but they still do not replace the original product label, manufacturer catalog, engineering review, maintenance procedure, or procurement specification.
Related bearing guides
How to Read Bearing Numbers | Bearing Bore Code and Dimensions | Bearing Seal, Shield, and Clearance Suffixes | 6204-2RS-C3 Bearing Number | 6205-ZZ vs 6203-2Z Bearing Number | 608-2RS Bearing Number | NU205ECP Bearing Number | 30205 and 22212 Bearing Numbers | Bearing Number Reference Set Limits
Decode logic
- Normalize the visible bearing number, then resolve it against the imported bearing database before falling back to parser rules.
- Use the exact CSV row when the designation is present in the production table, including the source dimensions and suffix notes.
- Parse recognized seal, shield, clearance, precision, cage, and design suffixes into separate result segments when the code is not in the exact table.
- Preserve manufacturer-specific suffixes as unresolved design suffixes rather than assigning a universal meaning.
- Return a decoded summary, confidence note, segment breakdown, and reference rows; verify full dimensions and suffix meanings in the exact maker catalog.
FAQs
Is this a universal bearing catalog lookup?
No. It uses an imported bearing database for known rows and parser rules for supported patterns. It still does not replace an NSK, SKF, JTEKT/Koyo, Schaeffler, Timken, or other manufacturer catalog.
How does the decoder read bore codes?
Common metric bearing designations use special bore codes 00, 01, 02, and 03 for 10, 12, 15, and 17 mm. Codes 04 through 96 commonly multiply by five, so 06 indicates a 30 mm bore. Exact database rows may also provide the bore directly.
Why are some suffixes unresolved?
Many supplementary suffixes are controlled by the bearing manufacturer or product line. The decoder preserves those suffixes and marks them as manufacturer-specific instead of inventing a universal meaning.
What should I enter?
Enter the complete bearing number as printed, including seals, shields, clearance, precision, and design suffixes, for example NU205ECP, 623-2Z, NJ 202 ECP, or 30302 J2.