2016 - Tough Mountain Challenge
2016 distances
Obstacle race
8:00 AM Wave
8:15 AM Wave
8:30 AM Wave
8:45 AM Wave
9:00 AM Wave
9:15 AM Wave
9:30 AM Wave
9:45 AM Wave
10:00 AM Wave
10:15 AM Wave
10:30 AM Wave
10:45 AM Wave
11:00 AM Wave
11:15 AM Wave
11:30 AM Wave
11:45 AM Wave
12:00 PM Wave
12:15 PM Wave
12:30 PM Wave
12:45 PM Wave
1:00 PM Wave
1:15 PM Wave
1:30 PM Wave
1:45 PM Wave
2:00 PM Wave
2:15 PM Wave
2:30 PM Wave
2:45 PM Wave
3:00 PM Wave
Race-day weather
Conditions on July 23, 2016 — historical Open-Meteo data.
The sun rises at 5:21 AM and sets at 8:18 PM local time (EDT) in Newry on July 23, 2016 — 14h 57m of daylight.
Course
No course map published yet.
The organizer hasn't released a route for this event, and we don't publish guesses. If you're the organizer, send us a GPX file and we'll draw the profile.
Reviews
Done this event?
If you've participated in this event, share your experience with other runners
2016 results — Tough Mountain Challenge
8:00 AM Wave · 1,883 finishers
| Place | Name | Time | Pace |
|---|---|---|---|
| 1 | James Delorie | 43:25 | 10:52 /mi |
| 2 | Troy Pattison | 45:59 | 11:30 /mi |
| 3 | Nick Huston | 46:34 | 11:39 /mi |
| 4 | Alex Johnson | 48:26 | 12:07 /mi |
| 5 | Greg Goodhue | 48:25 | 12:07 /mi |
Every finisher is on the results page, filterable by distance, gender and age group.
Other races near Newry
Different organizers, within 40 miles, in the next three months
North American Wife Carrying Championship®
New England Cornhole Championships
RiverFire 5K Run/Walk
Waterford Fall Foliage 5K Road Race/Fitness Walk & 1 Mile Fun Run
Where this page comes from. Race details were last updated on . We re-check listings regularly and again in the week before race day.
- Entries, prices, waves and inclusions — the event's official registration page
- Temperature and humidity — Copernicus ERA5 reanalysis via Open-Meteo (CC BY 4.0)
- Elevation and terrain relief — Copernicus DEM GLO-90, ESA (CC BY 4.0)
- Comparisons and counts — Race Discovery calendar, 5 Newry events
Spotted something wrong? Tell us and we'll fix it.