Tilghman Beach And Golf Resort

Located in North Myrtle Beach (Ocean Drive), Tilghman Beach And Golf Resort is within a 5-minute drive of Cherry Grove Pier and McLean Park. This family-friendly hotel is 2 mi (3.3 km) from Surf Golf and Beach Club and 4 mi (6.4 km) from Tidewater Golf Club.

3 suites at Tilghman Beach And Golf Resort

3 suites

46 amenities at Tilghman Beach And Golf Resort

  • 24-hour business center
  • 24-hour front desk
  • Accessible bathroom
  • Assistive listening devices available
  • ATM/banking
  • Barbecue grill(s)
  • Bar/lounge
  • Coffee/tea in common areas
  • Complimentary Wi-Fi
  • Computer
  • Computer station
  • Elevator
  • Elevator/lift
  • Fitness facilities
  • Free parking nearby
  • Free self parking
  • Free self-parking
  • Free WiFi
  • Indoor pool
  • In-room accessibility
  • Laundry facilities
  • Lazy river
  • Mobility accessible rooms
  • Number of buildings/towers - 1
  • Number of floors - 15
  • Outdoor pool
  • Picnic area
  • Poolside bar
  • Pool sun loungers
  • Pool umbrellas
  • Restaurant
  • Roll-in shower
  • Roll-in shower
  • Rooftop terrace
  • Sauna
  • Sauna
  • Smoke-free property
  • Terrace
  • Terrace
  • Total number of rooms - 220
  • Tours/ticket assistance
  • Wedding services
  • Wheelchair accessible
  • Wheelchair accessible parking
  • Wheelchair accessible path of travel
  • Year Built - 2008

Tilghman Beach And Golf Resort reviews

461 reviews

Tilghman Beach And Golf Resort Location

1819 N Ocean Blvd

North Myrtle Beach, SC 29582-2744 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. #}