March 1

The 2018 Shenandoah Half Marathon is Cancelled


We’re extremely sad to announce that we are cancelling the 2018 Shenandoah Half Marathon. We love this park and were very happy with the inaugural race last year. Unfortunately there just doesn’t seem to be enough interest in this event to hold it annually. We opened registration with high hopes that everyone who had a great time in 2017 would be back and bring friends, but our numbers have shrunk from last year and we just haven’t been able to grow enough excitement around this race.

We put off this decision as long as we could, but we wanted to make the decision with enough time for people to adjust their travel plans. We’re very sorry for any disappointment this announcement may cause. If you were registered for this event, you will receive a refund in the next few days, if you haven’t already.

It is possible this race could come back in the future in some form, but we will not be able to hold the race in 2018 or 2019.

We are grateful to the towns of Luray and Stanley as well as Page County who were incredibly helpful in putting the race on last year. We really hope to be back in the future, but for now we will have to focus on other parks.

If you have any questions or concerns about the cancellation, please comment below or email us at


Will I get my money back?

Absolutely. If you’re registered for the 2018 Shenandoah Half, Bobcat Double, or Appalachian Triple, you’ll see a refund hitting your bank account in the next 48 hours (if you haven’t already) for the Shenandoah portion of your registration.

Will this event come back in the future?

It’s very possible. 2017’s event went well and we got lots of positive feedback (despite rainy conditions). We’re not writing it off completely, we just don’t think there’s enough demand to hold it annually.

Are any other races being cancelled?

No. There is no threat of cancelling any other event in the 2018 calendar.


You may also like

Subscribe to our newsletter now!

Success message!
Warning message!
Error message!