Days Inn by Wyndham Hardy

Suiteness Logo

The only place to book connecting hotel rooms and suites. Here's how.

With a stay at Days Inn by Wyndham Hardy in Hardy, you'll be within a 5-minute walk of Loberg Park and Main Street of Hardy. This hotel is 0.4 mi (0.7 km) from Time and Place Clock Museum and 0.5 mi (0.8 km) from Dr. Thompson Park.

6 suites at Days Inn by Wyndham Hardy

6 suites

25 amenities at Days Inn by Wyndham Hardy

  • 24-hour front desk
  • Assistive listening devices available
  • Braille or raised signage
  • Conference space
  • Daily
  • Designated smoking areas
  • Free breakfast
  • Free breakfast to go
  • Free self parking
  • Free WiFi
  • Internet access in public areas - high speed
  • Internet access - wireless
  • Number of outdoor pools - 1
  • Outdoor seasonal pool
  • RV, bus, truck parking
  • Safe-deposit box at front desk
  • Uncovered parking
  • Upper floors accessible by stairs only
  • Well-lit path to entrance
  • Wheelchair accessible (may have limitations)
  • Wheelchair-accessible on-site restaurant
  • Wheelchair accessible parking
  • Wheelchair accessible path of travel
  • Wheelchair-accessible registration desk
  • Wheelchair-accessible van parking

4 images of Days Inn by Wyndham Hardy

  • Exterior | Days Inn by Wyndham Hardy
  • Exterior | Days Inn by Wyndham Hardy
  • Lobby | Days Inn by Wyndham Hardy
  • Pool | Days Inn by Wyndham Hardy

Days Inn by Wyndham Hardy reviews

2.9
546 reviews

Days Inn by Wyndham Hardy Location

4213 Hwy 63 and 62-412

Hardy, AR 72542 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. #}