Nevada · in-format generated example
136.X86 — license plate combination
136.X86 is filed as a generated example of the Nevada sequential passenger serial — 999.A99 (1 letter + 5 digits). Letters X sit in positions 4; digits 13686 sit in positions 1, 2, 3, 5, 6. This page does not identify a car, an owner, or a live registration. It measures how the string sits inside a published character map of 2,600,000 slots, adopted in this atlas from 2001 after ABC-123 county coded.
Disclaimer. 136.X86 is not published here as a real vehicle or plate record. It is a generated example of a serial map for teaching and testing.
- Plate text
- 136.X86
- Alphanumeric
- 136X86
- State format
- Nevada · 999.A99
- Character count
- 6
- Letters
- X
- Numbers
- 13686
- Letter positions
- 4
- Numeric positions
- 1, 2, 3, 5, 6
- Combinations in map
- 2,600,000
- Mixed-radix rank
- 355,986
How to read 136.X86
Spoken: one · three · six · X-ray · eight · six. Normalised forms: 136X86, slug 136-x-86, display 136.X86.
Character map
| Position | Glyph | Class | Role |
|---|---|---|---|
| 1 | 1 | Digit | Numeric series glyph (spoken: one). |
| 2 | 3 | Digit | Numeric series glyph (spoken: three). |
| 3 | 6 | Digit | Numeric series glyph (spoken: six). |
| — | . | Separator | Punctuation in the published pattern, not a serial value. |
| 4 | X | Letter | Alphabetic series glyph (NATO: X-ray). |
| 5 | 8 | Digit | Numeric series glyph (spoken: eight). |
| 6 | 6 | Digit | Numeric series glyph (spoken: six). |
Nevada format in brief
Nevada’s dot separator is distinctive. The state rotated away from a simple ABC-123 as Las Vegas and Reno fleets grew.
SPR 9932 has no leading digit block and does not match Nevada’s dotted map. Full essay: Nevada license-plate format.
Combinatorics for 136.X86
Alphabet size 26 × the digit slots in 999.A99 produces 2,600,000 serials. Rank 355,986 is about the 13.6918 percentile of that space (0 = first serial, 100 = last).
States whose map accepts 136X86
Serial neighbours of 136.X86
Deterministic rank deltas. These links do not change on refresh.
Similar combinations (this request)
Same Nevada map, new PHP random draw on every reload — extra internal links, not a new identity for 136.X86.
Why someone might look up 136.X86
| Use | Note |
|---|---|
| Vanity research | People compare a wanted phrase against the sequential map so they can see whether it is a standard serial or a specialty request. |
| Fleet labelling | Inventories and film-unit vehicles often need a plausible unused-looking serial that still obeys a state’s character classes. |
| Fiction and props | Writers and set designers pick a combination that could exist on a given state’s dies without copying a photographed car. |
| Dataset testing | OCR, ANPR and form-validation tests need strings that match a published pattern, including separators. |
| Format teaching | The combination is a worked example of how many plates a map can hold, not a window into a motor-vehicle file. |
Generated example versus a real plate
A real Nevada plate is a physical die issued from a series or a vanity queue. 136.X86 on this URL is a string that fits that series’ character classes. Identical glyphs can exist in both worlds; this website has no feed that would let it tell them apart. If you need an official answer, ask the Nevada motor-vehicle agency, not plates.autos.
Questions about 136.X86
Which state does 136.X86 belong to?
136.X86 is analysed here as a generated example of the Nevada passenger serial (999.A99). It is not assigned to a motorist by this site. The glyphs fit the sequential passenger skeleton used in this atlas.
Is 136.X86 real?
No claim is made that 136.X86 is currently issued, expired, or reserved. The string sits inside a published character map. Whether a DMV ever stamped it is a registration fact this atlas does not observe.
What does 136.X86 mean?
136.X86 is a serial, not a slogan. Letters X occupy positions 4; digits 13686 occupy positions 1, 2, 3, 5, 6. Spoken with the NATO alphabet it reads one · three · six · X-ray · eight · six.
Which state uses 136.X86?
This page files 136.X86 under Nevada because it fits that state’s 999.A99 passenger map. No other jurisdiction in this atlas shares this skeleton for these glyphs. Other states with a different skeleton will reject the same glyphs.
Which vehicle uses 136.X86?
None that this atlas knows of. There is no vehicle make, model, colour, or VIN attached to 136.X86. If you photographed a car, the door-jamb sticker and the registration — not this page — identify the vehicle.
Which state’s format does 136.X86 follow?
Nevada sequential passenger plates are taught here as 999.A99 (1 letter + 5 digits), in use in this atlas from 2001. Earlier Nevada plates used ABC-123 county coded.
Is 136.X86 a vanity plate?
Probably not, as modelled. Sequential passenger serials are issued in series; vanity (personalised) plates are requested strings that often break 999.A99. 136.X86 fits the sequential map, so this atlas treats it as a series example, not a purchased phrase.
How is 136.X86 read?
Left to right as printed: 136.X86. Aloud: one · three · six · X-ray · eight · six. Hyphens and spaces are separators in the published pattern, not extra serial values.
Which letters and numbers are in 136.X86?
Letters: X (1). Digits: 13686 (5). Combined alphanumeric length: 6. Separators in the Nevada display form are taken from 999.A99.
How many combinations can the 136.X86 format produce?
The Nevada map 999.A99 with a 26-letter alphabet yields 2,600,000 distinct serials. 136.X86 sits at rank 355,986 in that mixed-radix order (about the 13.6918 percentile).
Could 136.X86 have been issued before?
It could, mathematically: the string is inside the 2,600,000-slot space. Issuance is a DMV operation (series rolls, skipped blocks, recalls). This page does not query a live file and cannot say whether 136.X86 was ever bolted to a bumper.
Why does 136.X86 appear on Google?
Because plates.autos publishes a stable analysis URL for the combination. Search engines that crawl https://plates.autos/nevada/license-plate-combinations/136-x-86/ are reading an educational combinatorics page, not a leaked registration. Ranking is not a proof of issuance.
Which country or region is 136.X86 from?
The working assumption on this page is the United States, West region, state of Nevada. Other countries use different dies, shields and checksums. A similar glyph string abroad would be a coincidence of alphabet, not a shared registry.
Is 136.X86 a valid US format?
136.X86 is a valid glyph string under the Nevada 999.A99 sequential passenger model used in this atlas. Validity here means “fits a documented sequential passenger skeleton,” not “cleared by a motor-vehicle agency.” Optional, military, and government plates are out of scope.
Which characters can appear on 136.X86?
On the Nevada sequential map: letters from ABCDEFGHIJKLMNOPQRSTUVWXYZ and digits 0–9. Skipped letters in this atlas: none modelled. Separators: whatever 999.A99 prints (space, hyphen, or dot). Decorative dies and stacked graphics do not add serial glyphs.
How might 136.X86 have been generated?
Two honest answers. A DMV would emit it by walking the 999.A99 series. This website can also construct it with PHP by placing letters X and digits 13686 into those slots — which is exactly how a generated example is made. Neither method is a public records search.
Was 136.X86 used in a film or series?
This atlas does not track screen-used plates. Prop departments often invent in-format serials. If 136.X86 appeared on camera, that is outside the dataset here; treat any match as unverified.
Why might 136.X86 be blurred in a photo?
Publishers, Street View pipelines, and news desks often blur plates as a privacy habit, not because 136.X86 is special. A blur is not evidence that the combination is issued, sensitive, or unique.
What are similar plate numbers to 136.X86?
Immediate serial neighbours increment the mixed-radix rank by small deltas (for example 136.X83 and 136.X84). Same-format random draws on this page change on refresh so crawlers can discover more in-class URLs without turning 136.X86 itself into a moving target.
What appears online about 136.X86?
You may find this analysis, forum guesses, or unrelated hits (part numbers, product SKUs). None of those sources, including plates.autos, is a substitute for a state records request. 136.X86 as published here is a generated example combination.