Americas Best Value Inn Lebanon, MO

Suiteness Logo

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

A stay at Americas Best Value Inn Lebanon, MO places you in the heart of Lebanon, within a 5-minute drive of Boswell City Park and Kenneth E. Cowan Civic Center. This hotel is 27.4 mi (44.2 km) from Lake of the Ozarks and 2 mi (3.3 km) from Route 66 Museum.

8 suites at Americas Best Value Inn Lebanon, MO

11 amenities at Americas Best Value Inn Lebanon, MO

  • 24-hour front desk
  • Daily
  • Designated smoking areas
  • Free breakfast
  • Free continental breakfast
  • Free self parking
  • Free WiFi
  • Internet access in public areas - high speed
  • Laundry facilities
  • Vending machine
  • Wheelchair accessible – no

11 images of Americas Best Value Inn Lebanon, MO

  • Exterior | Americas Best Value Inn Lebanon, MO
  • Exterior | Americas Best Value Inn Lebanon, MO
  • Lobby | Americas Best Value Inn Lebanon, MO
  • Exterior | Americas Best Value Inn Lebanon, MO
  • Exterior | Americas Best Value Inn Lebanon, MO
  • Exterior | Americas Best Value Inn Lebanon, MO
    See More...
  • Exterior | Americas Best Value Inn Lebanon, MO
  • Exterior | Americas Best Value Inn Lebanon, MO
  • Exterior | Americas Best Value Inn Lebanon, MO
  • Laundry Room | Americas Best Value Inn Lebanon, MO
  • Laundry Vending Facility | Americas Best Value Inn Lebanon, MO

Americas Best Value Inn Lebanon, MO reviews

3.8
302 reviews

Americas Best Value Inn Lebanon, MO Location

1830 W Elm St

Lebanon, MO 65536 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. #}