Lowest-numbered route you haven't been on an independent section

[DandyDan]

I believe this falls for me down to 68. I have only been on MN 68 for its overlap with MN 19 in Marshall and its overlap with US 14 between New Ulm and Sleepy Eye. I also believe the times where I encountered US 68 didn't involve me exiting onto it.

[74/171FAN]

Technically this drops back back down to 47; however, I remember driving a short section of NJ 47 north of US 322 as a result of missing my turn.  Otherwise I would still be at 89.

I am not affected by this condition at all now as I drove a solo piece of WV 47 on Thursday.

[Hobart]

I've hit rock bottom.
The lowest numbered route that I haven't been on an independent section of is North Dakota Route 1.

It is concurrent with Interstate 94 and US 52 between exits 283 and 288. I have been on no other section of this route.

[hotdogPi]

I've hit rock bottom.
The lowest numbered route that I haven't been on an independent section of is North Dakota Route 1.

It is concurrent with Interstate 94 and US 52 between exits 283 and 288. I have been on no other section of this route.

Since this is a spinoff of another thread, and the disclaimer is only in the other thread, here it is:

The thread title is slightly misleading taken literally. Taken literally, it would be 1 for everyone except those that have been on every single Route 1, but that's not what I meant.

If you've been on an independent section of any Route 1, it counts.

[paulthemapguy]

I already discount silly short concurrencies from my count in the original thread.  Silly short sections of standalone routes, however, are a different story.

[Rothman]

Looks like I'm okay and my lowest numbered "independent" route matches what I've got in the main thread: 288.  Had I not taken some local trips over the past couple of years, I might have been stuck at 38 (IA 38's concurrency with I-80), but I've been on independent 38s now.

That said, I only have a 325 due to TN 325 having a short concurrency with TN 111...I think.  I should check on that.

Anyway, my concurrency touches:

325 (TN 325/TN 111).  NY 325's easy enough to get to.
333 (KY 333/US 60).  Biggest pain of the three.  PA 333 is far enough to be annoying.
555 (OH 555 with OH 37 or OH 78).  I'll get I-555 someday.

That's it.  Got a lot of holes between 288 and whatever anyway where I haven't touched anything.

Got NY 325, so my route touches due to concurrencies drops to just 333 and 555.

[74/171FAN]

Technically this drops back back down to 47; however, I remember driving a short section of NJ 47 north of US 322 as a result of missing my turn.  Otherwise I would still be at 89.

I am not affected by this condition at all now as I drove a solo piece of WV 47 on Thursday.

I think my number with this condition is currently 108.  I have only been on PA 108 when it is concurrent with PA 18 and/or PA 168, and TX 108 when it is concurrent with I-20 and US 380.

[formulanone]

I drove on about 7 miles of New York 265 in Tonawanda today, so now it's 393.

(Next missing number would be 469, since all of I-469 is concurrent with another US Route.)

[74/171FAN]

Technically this drops back back down to 47; however, I remember driving a short section of NJ 47 north of US 322 as a result of missing my turn.  Otherwise I would still be at 89.

I am not affected by this condition at all now as I drove a solo piece of WV 47 on Thursday.

I think my number with this condition is currently 108.  I have only been on PA 108 when it is concurrent with PA 18 and/or PA 168, and TX 108 when it is concurrent with I-20 and US 380.

I recently clinched MD 108 so I think I am moved up to 266 since I consider myself as having driven a solo portion of US 127 in the midst of the Chattanooga lack of signage chaos.

[JayhawkCO]

Looks like my number is 107.  I've only been on NH107 when it is concurrent with US4.

I was on NS107, so now my number is... 108, which I've only been on TX108 when it's concurrent with I-20.

[74/171FAN]

I am currently unaffected with this condition at 427.  Though if I get 426-428 and 430, I would be at 429 as I only traveled the NY 429 concurrency with NY 31.

[MATraveler128]

I think mine is 26. I've only been on ME 26 along the I-295 concurrency in Portland.

[flan]

Looks like it's 17 for me. I've only been on ND 17 as it was concurrent with U.S. 81 in Grafton and ND 20 in Starkweather.

[Rothman]

Looks like I'm okay and my lowest numbered "independent" route matches what I've got in the main thread: 288.  Had I not taken some local trips over the past couple of years, I might have been stuck at 38 (IA 38's concurrency with I-80), but I've been on independent 38s now.

That said, I only have a 325 due to TN 325 having a short concurrency with TN 111...I think.  I should check on that.

Anyway, my concurrency touches:

325 (TN 325/TN 111).  NY 325's easy enough to get to.
333 (KY 333/US 60).  Biggest pain of the three.  PA 333 is far enough to be annoying.
555 (OH 555 with OH 37 or OH 78).  I'll get I-555 someday.

That's it.  Got a lot of holes between 288 and whatever anyway where I haven't touched anything.

Got NY 325, so my route touches due to concurrencies drops to just 333 and 555.

Hm.  Not sure what I was thinking here.  Looking at 333, 371, 377, 467 and 555.  Somehow missed those three in the middle as only being touched through concurrency.  Whatever.

[74/171FAN]

My number here with this condition now should be 429 (only portion is NY 429's concurrency with NY 31).