Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland

When you stay at Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland in Douglas, you'll be within the region of Fort Fetterman State Historic Site.

7 suites at Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland

15 amenities at Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland

  • 24-hour fitness facilities
  • 24-hour front desk
  • Breakfast available (surcharge)
  • Fitness facilities
  • Free self parking
  • Free WiFi
  • Laundry facilities
  • Luggage storage
  • Number of meeting rooms - 2
  • Number of restaurants - 1
  • RV, bus, truck parking (surcharge)
  • Wheelchair accessible (may have limitations)
  • Wheelchair-accessible on-site restaurant
  • Wheelchair accessible parking
  • Wheelchair-accessible registration desk

6 images of Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland

  • Exterior | Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland
  • Exterior | Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland
  • Lobby | Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland
  • Restaurant | Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland
  • Health club | Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland
  • Meeting Room | Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland
    See More...

Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland reviews

3.7
232 reviews

Travelodge by Wyndham Bill WY Thunder Basin Ntl Grassland Location

3522 Highway 59

Douglas, WY 82633 US

1 (855) 282-1325

{# Hotel structured data. Every interpolated value goes through |json, which supplies its own quotes. Do NOT add quotes around a — the filter emits them, and writing them twice produces """value""". The reason is not style. This block used to interpolate values raw, so any hotel whose suite descriptions contained a line break emitted invalid JSON and Google discarded the whole thing — which was seven of our ten highest-impression hotel pages. Names came out with "&" in them for the same reason: HTML escaping applied where JSON escaping was needed. #}