BTR Pacer

BTR Pacer turns your Garmin watch into a personal race pacer for supported trail races. Instead of following a fixed average pace, BTR Pacer shows where you are compared to a pacing plan built for the actual course profile. The plan takes into account the route, climbs, descents, terrain profile, target finish time, and your selected BTR pacing strategy. During the activity, the data field shows a simple visual race between you and your virtual pacer: - See if you are ahead of or behind the plan. - Track the time gap to your pacer. - Follow your progress without constantly calculating pace in your head. - Get a quick visual cue of whether you should ease off, hold steady, or push. The goal is simple: help you manage your effort better and finish closer to your best possible result. How it works: - Create a pacing strategy in Bulgarian Trail Rating (https://www.my-btr.com). - Get your personal BTR Pacer key. - Enter the key in the data field settings in Garmin Connect. - Start your race or activity. - Let your watch guide you against your planned effort. BTR Pacer is designed especially for trail running, where flat pace is often misleading. A steep climb, fast descent, technical section, or aid station can all change what “good pacing” means. This data field helps you focus on execution instead of guessing. To use this data field, you need an active pacing strategy generated through Bulgarian Trail Rating.

- Improved route recovery after leaving and rejoining the course. - Better handling of shortcuts and route cuts, including reduced false “Off route” flickering after returning to the course. - More reliable matching on looped, out-and-back, and overlapping routes. - Added safeguards to avoid jumping to the wrong lap or a future route segment after GPS gaps. - Improved pacing accuracy when temporarily running extra distance off-course. - Reduced risk of incorrect position matching after tunnels, GPS loss, pauses, or screen changes. - Added and expanded simulator-tested Garmin Connect IQ unit tests for route matching edge cases. - Improved internal test setup to keep test code out of production builds. - Increased off distance to 120 meters