Unusually numbered routes

[TheGrassGuy]

*FL 9336
*Saratoga CR 1345
*Hunterdon CR 751
*Middlesex CR 807
*US Routes 163, 400, 412, and 425
*Interstates 87 (S), 99 and 238

Any others?

[NWI_Irish96]

IN 152.  Not that 152 is such an unusual number for a route, but in Indiana, 3di routes are based on a parent route that is either connecting or parallel, and US 52 doesn't come anywhere near 152.  Based on the state's numbering conventions, it should be an x41.

[Max Rockatansky]

CA 330 and CA 371 are kind of oddballs given they were once two-digit state highways with a "3"  tacked on.  In the early Signed State Route era you had the likes of CA 740 and CA 440 which seemed to be place holder designations for potential US Route corridors.  AZ 24 is totally out of sequence with the 60-99 two digit highway convention and seems to have been randomly drawn from a hat.  NV 28 and NV 88 are continuations of pre-1976 State Highway numbers and have a Californian Counterpart.  FL 300 was once FL G1A. 

[kphoger]

*US Routes ... 400, 412, and 425

Please see below (although the veracity of some of this info has been called into question on these boards, it has not actually been debunked).

US 412 is a NHS/ISTEA High Priority Corridor, and was designated in 1982 (see https://www.aaroads.com/high-priority/corr08.html ). It might become a future Interstate. US 425 was added to the US route system in 1989; this is the preferred corridor for any future extension of I-530 to I-69. Part of US 425 is included in the I-69 corridor (see 6.4 ). US 371 was added as a branch route of US 71 in 1995 in LA and AR. US 400 is also a NHS/ISTEA High Priority Corridor, added to the US system in 1996, the newest US route (see https://www.aaroads.com/high-priority/corr03.html ). The number was picked by Kansas DOT out of a list of available numbers, and agreed to by Missouri and Colorado. US 400 is also planned as a future extension of I-66.

[TheGrassGuy]

*US Routes ... 400, 412, and 425

Please see below (although the veracity of some of this info has been called into question on these boards, it has not actually been debunked).

US 412 is a NHS/ISTEA High Priority Corridor, and was designated in 1982 (see https://www.aaroads.com/high-priority/corr08.html ). It might become a future Interstate. US 425 was added to the US route system in 1989; this is the preferred corridor for any future extension of I-530 to I-69. Part of US 425 is included in the I-69 corridor (see 6.4 ). US 371 was added as a branch route of US 71 in 1995 in LA and AR. US 400 is also a NHS/ISTEA High Priority Corridor, added to the US system in 1996, the newest US route (see https://www.aaroads.com/high-priority/corr03.html ). The number was picked by Kansas DOT out of a list of available numbers, and agreed to by Missouri and Colorado. US 400 is also planned as a future extension of I-66.

But why those numeros? Why not US 402, US 414, or US 426?

[CNGL-Leudimin]

There are two US Routes newer than US 400: US 48 (Corridor H) and US 121 (Schrödinger or Alanland highway, in that it exists and doesn't exist).

As for other unusually numbered US Routes, I'd include US 44 and 46 (too far North), US 59 (too far West), US 33 (nominally North-South but mostly signed East-West), US 220 and former 666 (nominally East-West but signed North-South). US 6 only became an oddball when it was extended all the way to the West coast, its original terminus was Erie, Pennsylvania.

Internationally we have:
- Any freeway numbered A-70 and above in Spain
- A20 in France
- All the Ax(M) motorways in the UK, notably A1(M) and A74(M), as well as A601(M)
- SS 107 bis dir A in Catanzaro, Italy. Italian numbering is really crazy with all those suffixes, but that ramp takes the cake

[MNHighwayMan]

MN-197 in Bemidji. Not related to MN-97, nor is it the route's legislative route number. Just an arbitrary high number (lots of available lower numbers) for a route that should really be a business route of either US-2 or US-71.

[KeithE4Phx]

IN 152.  Not that 152 is such an unusual number for a route, but in Indiana, 3di routes are based on a parent route that is either connecting or parallel, and US 52 doesn't come anywhere near 152.  Based on the state's numbering conventions, it should be an x41.

IN 152 is part of the former US 152, which was the original Lafayette-to-Hammond route in the 1930s (1935-38).  It became IN 152 in 1938.  Most of that old route is now US 231.  The current IN 152 runs from the Borman Expressway (I-80 & 94/US 6 & 41) to US 20, about 2.5 miles.

[KeithE4Phx]

AZ 24 is totally out of sequence with the 60-99 two digit highway convention and seems to have been randomly drawn from a hat.

ADOT apparently is assigning two-digit numbers below 60 to new non-Interstate, non-loop freeways.  AZ 24 is the Gateway Freeway, which will get a new (temporary) non-freeway segment, with construction starting next year.  AZ 30 will be the Durango Freeway/I-10 Reliever, which follows the original planned route for I-10.  AZ 48 was supposed to be the upgraded Fain Rd. around Prescott Valley, but it was never signed.  It's now unsigned AZ 89S. 

Yet to be numbered are the partially completed Northern Parkway in the west valley, which, like the Loop freeways, is being built under MCDOT control and will be eventually turned over to ADOT once it's finished.  My guess is that AZ 50 will be recycled for that road, although nothing official has been said about it, AFAIK.

[Max Rockatansky]

AZ 24 is totally out of sequence with the 60-99 two digit highway convention and seems to have been randomly drawn from a hat.

ADOT apparently is assigning two-digit numbers below 60 to new non-Interstate, non-loop freeways.  AZ 24 is the Gateway Freeway, which will get a new (temporary) non-freeway segment, with construction starting next year.  AZ 30 will be the Durango Freeway/I-10 Reliever, which follows the original planned route for I-10.  AZ 48 was supposed to be the upgraded Fain Rd. around Prescott Valley, but it was never signed.  It's now unsigned AZ 89S. 

Yet to be numbered are the partially completed Northern Parkway in the west valley, which, like the Loop freeways, is being built under MCDOT control and will be eventually turned over to ADOT once it's finished.  My guess is that AZ 50 will be recycled for that road, although nothing official has been said about it, AFAIK.

Is Fain Road actually ADOT maintained East of the AZ 89A split?  I was always sunder the impression that was county maintained. 

[TheGrassGuy]

There are two US Routes newer than US 400: US 48 (Corridor H) and US 121 (Schrödinger or Alanland highway, in that it exists and doesn't exist).

As for other unusually numbered US Routes, I'd include US 44 and 46 (too far North), US 59 (too far West), US 33 (nominally North-South but mostly signed East-West), US 220 and former 666 (nominally East-West but signed North-South). US 6 only became an oddball when it was extended all the way to the West coast, its original terminus was Erie, Pennsylvania.

Internationally we have:
- Any freeway numbered A-70 and above in Spain
- A20 in France
- All the Ax(M) motorways in the UK, notably A1(M) and A74(M), as well as A601(M)
- SS 107 bis dir A in Catanzaro, Italy. Italian numbering is really crazy with all those suffixes, but that ramp takes the cake

Isn't the Ax(M) designation for sections of A roads that have been upgraded to motorway standards, but are still considered part of the motorways? You know, like Interstate 41?

[KeithE4Phx]

AZ 24 is totally out of sequence with the 60-99 two digit highway convention and seems to have been randomly drawn from a hat.

ADOT apparently is assigning two-digit numbers below 60 to new non-Interstate, non-loop freeways.  AZ 24 is the Gateway Freeway, which will get a new (temporary) non-freeway segment, with construction starting next year.  AZ 30 will be the Durango Freeway/I-10 Reliever, which follows the original planned route for I-10.  AZ 48 was supposed to be the upgraded Fain Rd. around Prescott Valley, but it was never signed.  It's now unsigned AZ 89S. 

Yet to be numbered are the partially completed Northern Parkway in the west valley, which, like the Loop freeways, is being built under MCDOT control and will be eventually turned over to ADOT once it's finished.  My guess is that AZ 50 will be recycled for that road, although nothing official has been said about it, AFAIK.

Is Fain Road actually ADOT maintained East of the AZ 89A split?  I was always sunder the impression that was county maintained.

If I read my AZDOT milepost map right, as well as the last time I looked at each end on Google Maps, Fain Rd. is ADOT-maintained (it has ADOT-installed mileposts) between AZ 89A and AZ 69, despite the section directly east of 89A being within the city limits of Prescott Valley.

[Max Rockatansky]

AZ 24 is totally out of sequence with the 60-99 two digit highway convention and seems to have been randomly drawn from a hat.

ADOT apparently is assigning two-digit numbers below 60 to new non-Interstate, non-loop freeways.  AZ 24 is the Gateway Freeway, which will get a new (temporary) non-freeway segment, with construction starting next year.  AZ 30 will be the Durango Freeway/I-10 Reliever, which follows the original planned route for I-10.  AZ 48 was supposed to be the upgraded Fain Rd. around Prescott Valley, but it was never signed.  It's now unsigned AZ 89S. 

Yet to be numbered are the partially completed Northern Parkway in the west valley, which, like the Loop freeways, is being built under MCDOT control and will be eventually turned over to ADOT once it's finished.  My guess is that AZ 50 will be recycled for that road, although nothing official has been said about it, AFAIK.

Is Fain Road actually ADOT maintained East of the AZ 89A split?  I was always sunder the impression that was county maintained.

If I read my AZDOT milepost map right, as well as the last time I looked at each end on Google Maps, Fain Rd. is ADOT-maintained (it has ADOT-installed mileposts) between AZ 89A and AZ 69, despite the section directly east of 89A being within the city limits of Prescott Valley.

It is in ADOT's official map online with mileage and all:

http://adot.maps.arcgis.com/apps/webappviewer/index.html?id=5b7e6ea8aafd4405a4c6d1d17b1a2fdd

I think that must be relatively new the expressway expansion East of AZ 89A.  I could swear that part of Fain Road was county maintained when it was two lanes but has been years since I lived out there.  I recall some of the AZ 48 talk I the Arizona Roads website was the only place that had some sort of documentation about it and page hasn't been updated in over a decade. 

[TheGrassGuy]

How did the 4-digits in FL get their numbers anyway? It's not just 9336, there's also an FL 5054 in Melbourne (Sarno Rd), but it's not signed.

[Max Rockatansky]

How did the 4-digits in FL get their numbers anyway? It's not just 9336, there's also an FL 5054 in Melbourne (Sarno Rd), but it's not signed.

FL 997 and 9336 were part of FL 27 which were renumbered to avoid confusion with US 27. 

[TheGrassGuy]

But the numbers are so bizarre. Perhaps they were originally county routes? I know that county routes in FL sometimes go into the 4 digits.

[ozarkman417]

My thoughts on US 425:
Since 425 ends at 65 near Pine Bluff, and intersects 65 again in Clayton, it could be a 3di of 65 (465?) US 65 currently only has one 3di. At Clayton, 65 goes to what is 425's terminus at Natchez, truncating what would be a 65 3di to the current endpoint of 65. That way, the route won't be an AASHTO violation.

[KeithE4Phx]

It is in ADOT's official map online with mileage and all:

http://adot.maps.arcgis.com/apps/webappviewer/index.html?id=5b7e6ea8aafd4405a4c6d1d17b1a2fdd

I think that must be relatively new the expressway expansion East of AZ 89A.  I could swear that part of Fain Road was county maintained when it was two lanes but has been years since I lived out there.  I recall some of the AZ 48 talk I the Arizona Roads website was the only place that had some sort of documentation about it and page hasn't been updated in over a decade.

Interesting that they still mark the entire length of AZ 87 through Chandler and Mesa, but there are no traces of ADOT markings anywhere along that segment, other than the ramps and overpass at US 60.

They also mark off the yet-to-be-built section of AZ 24 between Ellsworth Rd. and Ironwood Dr., while still keeping the old AZ 153 on the map.  It had been turned over to the City of Phoenix in 2008 and the number was discontinued.  They also do not show the new construction of the South Mountain Freeway (Loop 202), some of which has recently opened.

[Verlanka]

US 33 (nominally North-South but mostly signed East-West)

Not to mention being entirely east of US 31.

[TheHighwayMan3561]

MN-197 in Bemidji. Not related to MN-97, nor is it the route's legislative route number. Just an arbitrary high number (lots of available lower numbers) for a route that should really be a business route of either US-2 or US-71.

Also MN 610, which was numbered as a "3dus" of US 10, but with an insanely high number.

[NWI_Irish96]

IN 152.  Not that 152 is such an unusual number for a route, but in Indiana, 3di routes are based on a parent route that is either connecting or parallel, and US 52 doesn't come anywhere near 152.  Based on the state's numbering conventions, it should be an x41.

IN 152 is part of the former US 152, which was the original Lafayette-to-Hammond route in the 1930s (1935-38).  It became IN 152 in 1938.  Most of that old route is now US 231.  The current IN 152 runs from the Borman Expressway (I-80 & 94/US 6 & 41) to US 20, about 2.5 miles.

Thanks, I wasn't aware of a former US 152, that makes the route number make much more sense.

[GaryV]

US 33 (nominally North-South but mostly signed East-West)

Not to mention being entirely east of US 31.

Not quite entirely.  The original US-33 was co-signed with US-31 from Indiana into St. Joe, MI - so that portion wasn't "entirely" east of US-31.  Then later, US-33 was extended to the northwest, so the extension was fully west of US-31.

Now that the "northern" terminus is in Elkhart, your "entirely east" statement is correct.

That said, I wonder why this diagonal (and US-35 for that matter) wasn't given an even number like US-52 was.  Maybe because the logical numbers, 44 and 46, had already been used up in non-standard places?

[Eth]

AL 605. Where the heck did that number come from? Alabama doesn't typically do state route numbers over ~300 (besides 759, an extension of I-759).

[Mr. Matté]

*Hunterdon CR 751
*Middlesex CR 807

These two don't exist anymore. HuntCo 751 may have just been a typo by NJDOT, the county always considered it CR 621 and the SLDs were recently corrected to that number. CR 807 was never signed, is now just (unsigned) CR 632. There was a reference to a proposed Route 807 freeway in 1973 NYT article running through Essex, Union, and Somerset so that, if it was built, would qualify in this thread.

[paulthemapguy]

Wisconsin 213 near Beloit has a strange number.  I've never seen a successful attempt to explain the number there.  Wisconsin doesn't have state route numbers over 200 unless they're branches of a two-digit route (310's a branch of 10, 241's a branch of 41, etc.).