SQL-662 — license plate combination

SQL-662 is analysed here as a generated example of the Minnesota passenger serial (AAA-999). It is not assigned to a motorist by this site. The glyphs fit the sequential passenger skeleton used in this atlas.

No claim is made that SQL-662 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.

SQL-662 is a serial, not a slogan. Letters SQL occupy positions 1, 2, 3; digits 662 occupy positions 4, 5, 6. Spoken with the NATO alphabet it reads Sierra · Quebec · Lima · six · six · two.

This page files SQL-662 under Minnesota because it fits that state’s AAA-999 passenger map. The same alphanumeric string also fits Hawaii, Iowa, Louisiana, Mississippi, Nebraska, Oklahoma, South Carolina, Vermont. Other states with a different skeleton will reject the same glyphs.

None that this atlas knows of. There is no vehicle make, model, colour, or VIN attached to SQL-662. If you photographed a car, the door-jamb sticker and the registration — not this page — identify the vehicle.

Minnesota sequential passenger plates are taught here as AAA-999 (3 letters + 3 digits), in use in this atlas from 2009. Earlier Minnesota plates used ABC-123 county and lake graphics.

Probably not, as modelled. Sequential passenger serials are issued in series; vanity (personalised) plates are requested strings that often break AAA-999. SQL-662 fits the sequential map, so this atlas treats it as a series example, not a purchased phrase.

Left to right as printed: SQL-662. Aloud: Sierra · Quebec · Lima · six · six · two. Hyphens and spaces are separators in the published pattern, not extra serial values.

Letters: SQL (3). Digits: 662 (3). Combined alphanumeric length: 6. Separators in the Minnesota display form are taken from AAA-999.

The Minnesota map AAA-999 with a 26-letter alphabet yields 17,576,000 distinct serials. SQL-662 sits at rank 12,595,662 in that mixed-radix order (about the 71.664 percentile).

It could, mathematically: the string is inside the 17,576,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 SQL-662 was ever bolted to a bumper.

Because plates.autos publishes a stable analysis URL for the combination. Search engines that crawl https://plates.autos/minnesota/license-plate-combinations/sql-662/ are reading an educational combinatorics page, not a leaked registration. Ranking is not a proof of issuance.

The working assumption on this page is the United States, Midwest region, state of Minnesota. Other countries use different dies, shields and checksums. A similar glyph string abroad would be a coincidence of alphabet, not a shared registry.

SQL-662 is a valid glyph string under the Minnesota AAA-999 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.

On the Minnesota sequential map: letters from ABCDEFGHIJKLMNOPQRSTUVWXYZ and digits 0–9. Skipped letters in this atlas: none modelled. Separators: whatever AAA-999 prints (space, hyphen, or dot). Decorative dies and stacked graphics do not add serial glyphs.

Two honest answers. A DMV would emit it by walking the AAA-999 series. This website can also construct it with PHP by placing letters SQL and digits 662 into those slots — which is exactly how a generated example is made. Neither method is a public records search.

This atlas does not track screen-used plates. Prop departments often invent in-format serials. If SQL-662 appeared on camera, that is outside the dataset here; treat any match as unverified.

Publishers, Street View pipelines, and news desks often blur plates as a privacy habit, not because SQL-662 is special. A blur is not evidence that the combination is issued, sensitive, or unique.

Immediate serial neighbours increment the mixed-radix rank by small deltas (for example SQL-659 and SQL-660). Same-format random draws on this page change on refresh so crawlers can discover more in-class URLs without turning SQL-662 itself into a moving target.

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. SQL-662 as published here is a generated example combination.