6 to 35 through Ft Worth

or

6 to 35 through Dallas

or

21 to 45 to 35

http://maps.google.com/maps?f=d&hl=en&saddr=college+station,+tx&daddr=oklahoma+city,+ok&sll=37.0625,-95.677068&sspn=51.355924,82.265625&layer=&ie=UTF8&z=7&ll=33.137551,-96.361084&spn=6.850937,10.283203&om=1

Google says 6 -> 35 through fort worth.

6 to 14 to 45 to 35

6 to 35 through FortWorth

Karrde - I know what Google says. I didn't know if that was the fastest way or not.

I have driven between the two cities many times (I was on assigned to a client in OKC during football season 2 years ago.)

In my experience the fastest route is 6 to I35W through Ft. Worth. I think I35W is actually a couple miles longer than I35E but the traffic is significantly better through Ft. Worth. If you do want to go through Dallas for some reason I think 6 to OSR to 45 to 35 is the best route in that case.

Also, am I going to run into major traffic in OKC around 6-630. The plan is to leave CS around 1230 tomorrow.

airplane

Yeah, that WOULD be the fastest way.

OKC traffic is never that bad if you're used to Dallas or Houston.

When I left there was significant construction going on on I35 which did slow things down, but it's not nearly as bad as say northbound 75 at 6:00 on a Friday in Dallas.

I grew up in Denton, which is where 35E and 35W come back together.

Definitely go 6 to 35 through Fort Worth.

35W is fewer miles than 35E, and the traffic isn't as bad in Fort Worth as it is in Dallas.

Be aware of the construction on I-35 just north of Ardmore. It's rather slow for a couple of miles through there as traffic is down to one lane in each direction.

I wouldn't think it'll cost you more than a few minutes, unless of course you're running late or have to go to the bathroom real bad in which case you can expect to come to a complete standstill for 2-3 hours.

yea the real bad spot with construction is before norman.. me and some friends went to stillwater in the fall and we sat in traffic for about 45 minutes without moving.. its terrible

Like most have said, 6 to 35W thorugh Fort Worth is the fastest way.

I went to the game in Norman last month and the construction didn't seem like a big deal to me. What was a big deal was the traffic just north of Norman when we went to go find food.

quote:

---

6 to 14 to 45 to 35

---

Hell No..avoid HWY 14 AT ALL COST...That road takes forever..I live in Garland and travel to College Station frequently...I promise I have driven every possible route out there..do this
Take HWY 21 TO North Zulch
Then HWY 39 North to Jewitt
Then HWY 79 East to Buffalo
in Buffalo get on 45 North to Dallas and get on 35
I know this has alot of backroads to Buffalo...but unlike HWY 14 these are all 70 MPH roads and not through a bunch of towns.
Do this going 70 on the backroads and at least 75 on I-45 and you will make Downtown from College Station in 2.5 hours
But as others have said 35 through FW may be faster..dont know?

[This message has been edited by victory (edited 3/7/2007 11:31a).]

6 to Waco, 35 through Ft. Worth. I drove it dozens of times going from Aggieland to home (OKC).

Way way way faster than any route that takes you through Dallas (35, 14/45, etc)

is there a race this weekend at Texas Motor Speedway? If not, 35W is the best. Hwy 6 to Loop 340 to I-35, take 35-W through Ft. Worth, merge back up in Denton, follow the signs.

OKC traffic is a joke...and there won't be much Northbound at that time....my Fiancee is from there.

Make sure your not heading thru Fort Worth at rush hour itll take you two hours or more to get thru.

I'll hit Ft Worth around 300. Not rush hour.

There is no traffic in OKC at 630. The biggest slow down you will hit will be the stretch of one lane construction in southern Oklahoma.

What construction is going on south of Norman?

They are doing some median work just south of Norman, but that should not cause any problems. The construction situation between Norman and OKC actually seems a little improved over last year. The only major problems will be just north of the Red River, but at the time of day and the middle of the week it should not be that bad.

^
|
|

I'm surprised a few private pilots haven't posted seats on small planes. There were always at least a couple for football homegames. Guess b-ball's a little different in that regard.

[This message has been edited by Nebules (edited 3/7/2007 3:08p).]

what victory said is the way to go. i drove back adn forth between cs and kansas city before my wife and i got married while dating long distance. i've taken about every route known to man, and i'll vouch for victory's route. while 35 through ft worth is faster than 35E, it doesn't come close to making up for the rest of the route.

definitely 6 to 35W, going through dallas sucks, not to mention Dallas sucks.

Thanks yoshi

HEADING NORTH!!!

[This message has been edited by Spirit of Aggieland (edited 3/7/2007 3:54p).]

Just for everyone's information:

I-35W: 85.203 miles
I-35E: 96.756 miles

(Source: http://www.dot.state.tx.us/tpp/search/query.htm)



I'm beefeater87, and I approve this message.


[This message has been edited by beefeater87 (edited 3/7/2007 3:53p).]

Drive NORTH, (Not in circles)

35W through Ft. Worth. As long as you're through town by 4:30-ish you'll be in great shape. Just make sure you aren't coming into town around 5, avoid that at all costs. Just anything to stay as far away from Dallas as possible...ugh Dallas

35W was a horrible idea today...