StatTracker has been designed to help you keep track of your Strava activity stats over time and to give you all the tools you need to perform advanced calculations.
The wide variety of filters that are available work together with the various functions, such as, a column graph, scatter graph, data table, histogram and progress chart to facilitate the discovery of unique statistical insights on your Strava history.
To illustrate how StatTracker works, I have described below the steps to getting some interesting facts, follow the instructions with your own stats to see your results.
So, let’s start with a simple but fun example. This isn’t really the hard-hitting analysis that the pro athletes look at, but hey, everyone likes to get some kudos from time to time!
|Data Filters – Activity type/s tab||Select the activity types you wish to view – select them all if you record more than 1 activity type with Strava to get the best results|
|Data Filters – Date Options tab||Select ‘By Weekday’ from the Data Grouping field Then select the date range you wish to view|
|Data Filters – Data Fields tab||Check the ‘Total Kudos Count’, ‘Total Activity Count’ and ‘Average Kudos per Activity’ checkboxes|
|Data Table||The data displayed shows the total kudos count, the total number of activities completed and the average amount of kudos you have received per activity within the date range for each day of the week.
You can infer what you like from the results! I reckon I have done more interesting activities and uploaded photos more often on Saturdays. However, it may be just that the people that follow me on Strava just happen to be more active on Saturdays!
By the way, don’t judge me on the paltry amount of kudos I receive! I’m very selective about who I allow to follow me on Strava and so have very few followers!
My mate Jeff is a runner, he wants to set himself a target for this year and keep track of how he's going with it.
|Data Filters – Activity type/s tab||Select the activity type/s you wish to view. Jeff likes running, so that is what he selected.|
|Data Filters – Attributes tab||Select the attributes of the activities to be included in the stats.
Jeff wanted to make sure all activities were included so selected all attributes, all gear and left the Keyword and minimum / maximum fields empty
Note: The Activity type/s and Attributes filters are the only ones that have any effect on the Progress section
|Progress Section||When you first open the Progress section the options will be set to display Distance for the current year. By clicking OK you will see a solid blue line representing your distance over the year.
The blue dotted line represents projected distance based on how far you travel per day.
Hovering the mouse or touching the graph reveals a marker and some info for the date where the mouse is placed.
In this example I have placed the mouse over the end of the year to see the projected distance that Jeff will achieve if he maintains his daily distance – this is 6638.76 km as at 30th June 2019
|Progress Section||You can change the options:
|Progress Section||By clicking OK on the new selections, a brown line appears which represents the target. From the table below the graph we can see that its is day 181 of the year (as at 30th June 2019), so by hovering the mouse over the graph until you see Days = 181, you can see how much distance you have attained for the year in blue, how much you need to attain by this time to be on target in brown and the difference between the two.
To get on track for this target for the rest of the year Jeff needs to get the blue line on or above the brown line.
|Progress Section||The table below the graph gives some more information that is useful for working out how far behind or ahead of your target you are.
In this example we are half way through the year and Jeff is behind target, the line of text below the table tells us what he needs to do for the rest of the year to catch up.
Once you have defined your target you can save it so that it comes up as an option whenever you log into the application – you can save as many presets as you like and delete them later when they are finished, or you don’t want to see them anymore!
As a cycling commuter I often like to mix up my morning ride by taking a longer route to work. If I am planning a new route that I have never ridden before it’s important for me to plan the route and make an estimation of how long it will take so that I know what time to set off and not be late for work.
I use Stava’s route planner to plot the route and Strava gives me an estimated time, however, the estimated time is based purely on average speed, which is OK, but what if my route takes in more hills than my average ride?
|Strava – Route Builder
You can also use Google maps, Trailforks, ViewRanger, etc.
|Plan the route you intend to take. Strava will let you know the distance and Elevation Gain of the route along with an estimation of moving time.
At this point, use a calculator to work out the average gain by distance – that is, the number of meters climbed per kilometres rode (I unapologetically use metric measurements for this exercise, but feel free to use imperial if that’s your preference)
In this case:
average gain by distance = m / km
= 444 / 17.71
Also, make a note of the distance: 17.71 km
|Data Filters – Activity Type/s tab||Filter by Ride only|
|Data Filters – Date Options tab||Select by activity in the Data Grouping field to display all activities.
Select your desired date range - I selected the last years’ worth of activity data for my date range to give me up to date stats.
|Data Filters – Attributes tab||If you have more than 1 bike, select the one that you will use from the Gear field (I have a specific bike for commuting: a hybrid bike with panniers).
I also filtered by Minimum Distance to take out those pesky 0.5km rides that I have somehow managed to record, these can really mess up your averages
|Data Filters – Data Fields tab||You need to have Average Speed and Average Gain By Distance selected for this exercise|
|Scatter Graph||Change the Y-Axis Data field to Average Speed and the X-Axis Date field to Average Gain By Distance.
The scatter graph displays the data as a collection of points, the value of Average Gain By Distance determines the position on the horizontal axis and the value of Average Speed determines the position on the vertical axis.
The relationship between these two variables is represented visually by the blue line where you can see, for example, that on a ride where I climb 35 metres per km, my average speed will be just a little over 12 km/h.
|Scatter Graph||Beneath the scatter graph is a calculator where you can enter a value for the x-axis variable to calculate the correlational value of the y-axis variable.
In this example I enter the average gain by distance that I got from the Strava route planner in step 1 (25.07)
This tells me that I am likely to have an average speed for this route of 16.26 km/h
So, the estimated time for the route I plotted in the Strava route planner is:
Time = distance / speed
= 17.71 / 16.26
= 1.089 hours
(This roughly equates to 1 hour, 5 minutes and 20 seconds)
|Since plotting this route I have ridden it 5 times and my average time is actually 1 hour 2 minutes and 53 seconds. This is close to the estimated time I calculated using StatTracker, it's certainly a lot closer than Strava's estimated time of 44 minutes!|
I'd love to know how people are using StatTracker, so drop me a line if you have discovered something cool! You can use the Contact section to send me a message and I promise to get back in touch.
Also, drop me a line if you have found a bug or have a suggestion for improvements.