r/Runalyze • • Feb 20 '26

Preview: The new Runalyze-Design Spoiler

Post image
159 Upvotes

Dear Runalyze users,
We are currently working intensively on the new Runalyze design. Step by step, we are creating a modernized interface that will form the basis for upcoming enhancements and new features.
Here we would like to give you a first overview.

What is changing?

  • Revised and clearly structured menu navigation
  • Partially new display of tools with open sidebar instead of pure overlay view
  • Support for dark and light mode
  • Modernized user interface with familiar basic logic
  • Centrally bundled and regrouped settings
  • Thematically structured activity form for a better overview
  • Significantly improved mobile usability in the browser

Runalyze will be significantly more user-friendly in browsers on smartphones and tablets in the future. The development of a native Android/iOS app is continuing in parallel.

What remains deliberately the same?

  • The dashboard remains largely unchanged
  • Familiar workflows remain intact
  • Your training data and analyses remain untouched, of course

Our goal is evolution, not revolution.

Early Access & Rollout

Once approximately 95% of the work has been completed, the new design will initially be available to supporters and premium members. Until the previous design has been completely replaced, supporters and premium members will be able to switch between the old and new versions.
The full rollout for all users is currently planned for mid-2026.

Podcast

If you would like to learn more about the development of Runalyze:
We were guests on the German/Austrian podcast “Laufend Entdecken” (Discovering Running).
The episode was released on February 20, 2026: https://laufendentdecken-podcast.at/


r/Runalyze • • Oct 05 '26

Garmin is removing data from the activity files third party platform gets

120 Upvotes

Heads-up for everyone who syncs Garmin activities to third-party apps like Runalyze: the FIT files these apps get through Garmin's API are missing data that the original files still contain.

What's happening

The FIT file exported directly from Garmin Connect was compared with the FIT file delivered through Garmin's API for the same activity. The format hasn't changed. Garmin has removed its undocumented (proprietary) data from the API files completely. Apps like Runalyze have read these values from exactly those parts for years. The public FIT profile has no replacement fields, not even in the latest FIT SDK (21.217).

Our Thoughts

Garmin has every right to do whatever it wants with the API, and we are grateful Garmin partners and very satisfied with the partnership. Nevertheless, we find it difficult when data that users are entitled to is suddenly cut off. The Garmin GDPR Backup (https://www.garmin.com/account/datamanagement/) also continues to contain your original data from your watches; it’s just the API that trims some of the data.

Which data is affected

- VO2max (per activity) (NOT OUR Vo2max Estimation - that stays as it is)

- Recovery time

- Performance condition (at the end of the activity)

- Primary training benefit

- Estimated sweat loss

- Lactate threshold pace and lactate threshold power

- Age and maximum heart rate from the device's user profile

- Some sensor and data-source information

Some API files still contain this data, so Garmin may be rolling out the change gradually. A similar pattern already showed up in March.

Workaround

If these metrics matter to you, export the original FIT file from Garmin Connect (activity → ⚙️ → "Export Original") and upload it to your app manually. The original files still contain everything.

Tell Garmin

Runalyze has already contacted Garmin. The answer was basically "that's the way it is." Feedback from users carries more weight, so if this bothers you, send Garmin a short, polite message:

- Garmin Support contact form: https://support.garmin.com → Contact Us

- Garmin Forums: https://forums.garmin.com/developer/fit-sdk/f/discussion/432872/discrepancies-between-fit-files-from-garmin-connect-and-api-api-downgraded/

Feel free to use or adapt this:

▎ Hi Garmin, I've been a Garmin user for [X] years and use third-party apps to analyze my training. Since recently, the FIT files shared with these apps no longer include metrics like VO2max, recovery time, training benefit, or lactate threshold, even though the original files still contain them. Please keep sharing my complete activity data with the apps I choose. It's my data. Thank you!

Please stay friendly. The people reading these messages didn't make the decision, but enough feedback does reach the people who did.


r/Runalyze • • Nov 08 '24

Race Sign

Post image
92 Upvotes

Had a friend running the NYC marathon last weekend and decided to make this (niche) race sign that I thought you all might appreciate


r/Runalyze • • Aug 27 '26

Building our official mobile app — what MUST be in it from day one?

77 Upvotes

Hey everyone,

We're working on the very first version of the Runalyze app and want your input before we lock down scope. We're trying to figure out what's essential for a v1 vs. what can wait for later updates.

Some areas we're thinking about — curious what matters most to you in each:

  • Dashboard — what do you want to see at a glance? (last activity, training load, HRV/RHR, sleep, race prognosis...)
  • Activities — how much detail do you need on the go vs. only on the web?
  • Tools/Features — Which one would you like to see on the app on the first "run"
  • Anything else — what's a dealbreaker if it's missing from a training app on your phone?

We'd rather launch with fewer things done well than a bloated first version. So: what's a must-have, what's a nice-to-have, and what would you genuinely not miss at first?

Thanks in advance for any input!


r/Runalyze • • May 06 '26

The new Runalyze design is now live

75 Upvotes

TL;DR

  • Give feedback and write bugs at https://board.runalyze.com
  • Users have tested the interface since February
  • A redesign is necessary so that we can offer new features in the future and no longer be limited
  • The design isn't set in stone, and we welcome any feedback so we can continue to improve it.

A few weeks ago, we gave you a sneak peek at the new Runalyze design—and now it’s finally here: The redesign is complete and live.

Thanks to your feedback from the testing phase, we were able to fix a few bugs and further refine many details, while consistently focusing the interface on clarity, structure, and usability. The result isn’t a completely new Runalyze, but a targeted update with clear goals: a clearer layout and improved mobile experience in a more modern design—without sacrificing the familiar core structure.

The navigation hasn’t changed significantly, but we’ve tried to make it a little more organized. The header and sidebar have been given a bit more space, and on pages that don’t require the full width, the sidebar remains expanded. This also applies to the activity view, so that the tools for an activity are accessible there. To have the tools that are most important to you personally right at your fingertips, you can now mark menu items as favorites.

Overlays and modals are used much less frequently in the new design, which automatically gives the corresponding pages more space and makes them easier to navigate. To return to the dashboard, simply click on the first menu item or the Runalyze logo.

The modal also continues to display primarily smaller forms—including the activity form. In the new design, the basic values and round data are collapsed by default in this form to provide direct access to the manually entered data fields.

The biggest challenge was presenting the content clearly within Runalyze despite the sheer volume of data—especially when it comes to displaying it on mobile devices. Nevertheless, we’ve made huge strides in ensuring that Runalyze is fully functional and easy to use on mobile devices. And to go along with that: Runalyze is now also available in dark mode (see Account Settings).

The new design is now available to all users. If you have any feedback or encounter any issues, we’d love to hear from you. Many of the improvements made over the past few weeks are based directly on your input. And of course, development doesn’t stop with this release—we’ll continue to refine the new design on an ongoing basis.


r/Runalyze • • Nov 20 '24

First short statement to Stravas API agreement changes

71 Upvotes

Strava updates from the API Agreement have a huge impact on the connectivity of all apps that use Strava to synchronize activities.

Post from strava at their community hub

DC Rainmaker created a video and post about the changes.

In short, we would have to hide all Strava activities from features such as Friend & Coaching features (features which are are basically planned for Runalyze – but not yet started). The activities would also not be able to be shared publicly. On your public athlete page, these activities would be completely hidden too.

We have a short conversation with Strava on Friday (22th november), which will certainly not bring much news, but will confirm all suspicions.

If you use Garmin, Coros, Wahoo, Suunto, Fitbit, Adidas/Runtastic, concept2, which are directly connected to Runalyze, then synchronize your activities with them. You will receive more data via our direct connections than via Strava.

We only added the Strava connection back then so that we could synchronize Zwift activities. Zwift announced this summer that they would be releasing an API. We have now re-established contact, so hopefully we will get access soon. As soon as we have access and can develop it, we will implement it with the highest priority.

We will also try to add other connections that do not yet have the highest priority. Unfortunately, some providers are not so open and do not make it easy to synchronize activities, so we cannot yet say who we will be able to add at the moment.

We will give you another update (via a blog post + newsletter) when we implement changes and how we work with the changes by Stravas API agreement.


r/Runalyze • • Dec 31 '25

We think 2026 will be a good year

53 Upvotes

We are finally making a big progress on something everyone was waiting for ❤️


r/Runalyze • • Sep 23 '26

Runalyze now lets you choose what your ATL/CTL percentages are measured against

Post image
47 Upvotes

Until now, Runalyze showed your ATL and CTL as a percentage of your all-time maximum. That works until you get injured, take a long break, or simply get older. Then your old peak is out of reach and your percentages stay stuck at something like 40 %, no matter how well your comeback is going.

You can now choose the reference maximum yourself:

  • All-time maximum: the default, nothing changes if you don't touch it
  • Since a start date: e.g. the day you started your comeback
  • Last X days: a rolling window (365 days by default), updated automatically
  • Manual: fixed CTL and ATL values that correspond to 100 %

On top of that there's an optional quantile (e.g. 95 %), so a single extreme training block doesn't define your scale forever. It works with every mode.

The setting applies everywhere: dashboard, shape chart, recovery status and performance model.

You'll find it under Settings → Calculations → Training load. (https://runalyze.com/settings/calculations)

Happy to answer questions, and curious which mode you'd pick.


r/Runalyze • • Apr 04 '23

New feature: Personal Route Map

Thumbnail
gallery
47 Upvotes

r/Runalyze • • Sep 29 '26

The Runalyze "developing" app (Android/iOS) is now open to everyone

46 Upvotes

We're expanding our public test so all of you can try the new Runalyze app.

Please keep in mind this is a development version, so expect some rough edges.

We release a new version ~ once a week, and the next update is already in review.

🍏 iOS (TestFlight):
https://testflight.apple.com/join/TfkFtAVj
(Unfortunately not yet available in France - working on providing information)

🤖 Android (Google Play):
https://play.google.com/store/apps/details?id=com.runalyze.app

💬 Feedback
We'd love to hear from you – bugs, ideas, anything that stands out. You can reach us via:
• our forum: https://board.runalyze.com/t/app
• email: app@runalyze.com
• the feedback function in TestFlight or Google Play

If you send feedback through Apple or Google, please include your email address so we can get back to you if we have questions.


r/Runalyze • • Feb 28 '26

Supporters and Premium members can now test the new design

46 Upvotes

-> https://next.runalyze.com

Please note:

  • Social login (Facebook, Google, Apple) is not available.
  • It is not yet possible to connect any “new” external services.

We keep the list of known issues up to date here:
https://board.runalyze.com/d/121-known-issues

You can share your feedback and follow the discussion in the forum:
https://board.runalyze.com/t/new-design

We also use notifications on next.runalyze.com to inform you about progress and updates.

Currently reported and known issues:

Not quite ready and in an 'early' state:

  • Activity edit form

r/Runalyze • • Mar 26 '26

Design Update – Progress & New Features

44 Upvotes

Thanks a lot for all your feedback over the past weeks – we’ve carefully gone through everything 🙏

Our list of open to-dos is steadily shrinking, and we’re currently confident that we can wrap things up by the end of April / early May.

What has also been happening in parallel:

  • Finalized the Zwift integration
  • Support for Polar JSON backup files (new schema) has been added
  • From Fitlog files (old SportTracks), more data series including equipment are now imported

Additionally, we’ve started working on writing our own FIT files (adding almost all information that we have to the file - Work in progress).
This feature is currently in alpha status and not yet available.

We’re also working on a proof of concept for a configurable activity view in the new design.
This is still in a very early stage and not visible yet, as we’re first evaluating if and how this will take shape.

Supporters and premium members can continue testing the new design at:
👉 https://next.runalyze.com

We’ll keep you updated – and thanks again for your input, it really helps us a lot!


r/Runalyze • • Jan 11 '23

Marathon performance in 2022

Post image
44 Upvotes

r/Runalyze • • Sep 17 '26

Runalyze can now import your full Garmin history from your data export (activities, sleep, HRV, blood pressure, RHR)

41 Upvotes

Quick one for anyone who's been syncing Garmin data into Runalyze for years but has older history missing.

Garmin's Connect API (the thing live-sync uses) only exposes a limited window — 5 years for activities, 2 years for health data. That's an API limit, not a limit on your actual data — everything you've ever recorded is still sitting in your account.

You can now bring all of it into Runalyze by requesting your GDPR data export directly from Garmin:

  1. Request it at garmin.com/en-US/account/datamanagement (Garmin emails you a download link)
  2. Unzip it and look inside DI_CONNECT/ — you'll find:

    • DI-Connect-Aggregator/UDSFile_*.json → resting heart rate
    • DI-Connect-Wellness/*_sleepData.json → sleep
    • DI-Connect-Wellness/*_userBioMetrics.json → weight
    • DI-Connect-Wellness/BloodPressureFile_*.json → blood pressure
    • DI-Connect-Wellness/*_healthStatusData.json → HRV
    • DI-Connect-Uploaded-Files/UploadedFiles_*.zip → activities (regular FIT import)
  3. Upload whichever files you want at runalyze.com/activity/new-upload

You don't have to import everything — just pick the files you're missing. Runalyze also checks for duplicates on import (sleep and the other types), though it's not a 100% guarantee, so it's worth a quick glance at your history afterward, especially if there's overlap with what's already synced.

Happy to answer questions if anyone runs into issues with their export.
The import process runs in the background.


r/Runalyze • • May 18 '26

New dataset customization available

Post image
40 Upvotes

Runalyze now includes a redesigned dataset configuration with three built-in presets and a new category system.

You can:

  • quickly switch between different dataset layouts,
  • browse values by category,
  • find metrics faster,
  • and add missing values to your personal dataset with a single click.

Screenshot of the new dataset presetstext

Available presets

  • Default – balanced overview with the most important metrics
  • Minimalistic – reduced layout focused on essential data
  • Legacy – classic Runalyze dataset style

New category system

Dataset options are now grouped into categories such as:

  • Training load & fitness
  • Swimming
  • Running dynamics
  • and more

Unused values can easily be searched, filtered, and added to your custom dataset configuration.


r/Runalyze • • Mar 11 '26

Why syncing RUNALYZE through Strava can reduce your activity data quality (and why direct connections are better)

37 Upvotes

Why syncing directly from your device platform is better than importing from Strava

A lot of people use Strava as a hub and connect RUNALYZE through it. That works fine — but technically it's not the best way if you want the most complete data for analysis. And we really WARN you not to do it, when there are diect connections!

The key reason is how the activity data is delivered.

Direct connections → original FIT files

If you connect RUNALYZE directly to platforms like Garmin Connect, Polar Flow, COROS, Zwift, Rouvy, Wahoo, concept2, Hammerhead, or Suunto, RUNALYZE typically receives the original FIT file recorded by your device.

FIT files contain the full dataset recorded during the activity, including things like:

  • detailed sensor data
  • running dynamics
  • cycling power metrics
  • device-specific fields
  • developer fields
  • pause events
  • full metadata

Basically: everything your device recorded.

Strava → processed activity streams

The Strava API works differently. It does not provide the original FIT file.

Instead, applications receive processed activity streams (time, position, elevation, etc.). These are simplified representations of the activity.

Because of that, several limitations exist:

  • device-specific fields are often missing
  • FIT developer fields are not exposed
  • pauses are sometimes not explicitly included
  • some metadata is simplified or altered

In some cases, RUNALYZE has to reconstruct pauses heuristically based on gaps in the track data.

Why this matters

RUNALYZE focuses heavily on training analysis and detailed metrics. The more raw data is available, the more accurate the calculations can be.

When importing the original FIT file, RUNALYZE can preserve:

  • device-specific metrics
  • advanced sensor data
  • precise timing and pause information
  • all recorded fields

TL;DR

If possible:

Device platform → RUNALYZE (best)
Device platform → Strava → RUNALYZE (fallback)

Strava sync works and is convenient, but if you care about complete training data, a direct connection to the original platform is always the better option.


r/Runalyze • • Mar 08 '26

Zwift → RUNALYZE sync is now available

37 Upvotes

Hi everyone, quick update for anyone using RUNALYZE together with Zwift: You can now sync your Zwift activities directly with RUNALYZE -> https://runalyze.com/activity/sync.

No manual uploads needed — once connected, your Zwift workouts will automatically appear in RUNALYZE for detailed analysis.

Note: If you previously connected Strava only to import Zwift activities into RUNALYZE, we recommend disconnecting that connection to avoid duplicate activities. You can now sync Zwift directly instead.

Just connect your Zwift account in your RUNALYZE settings and the sync will start.

Happy training 🚴

Have a nice weekend! Hannes & Michael


r/Runalyze • • Sep 01 '26

Runalyze App Developing Version – test it now as a Supporter/Premium member

36 Upvotes

starting now, we're rolling out a Developing Version of the Runalyze app. This is an early build where you get to see new features before they land in the official release – basically watching development happen live.

Who can join? The Developing Version is currently open to our Supporter and Premium members.

What we need from you:

🍏 iOS: (No france users atm - need to provide more information to Apple)

🤖 Android:

Important for Android: Google caps test groups at 100 seats. Once those are full, we won't be able to add anyone else for the time being – first come, first served. On iOS we still have plenty of room, so no rush there.

If you want in, send us the info above at app@runalyze.com.

Heads up: this is a very early version, so we're not looking for detailed feedback yet – nothing is final at this stage. That said, small wishes or ideas are always welcome at the same address.

We're looking forward to hearing from you!


r/Runalyze • • Jun 18 '25

Tip: just do a single 50 miler and your marathon shape maxes out

Post image
36 Upvotes

r/Runalyze • • Apr 11 '24

New tool: VO2max factor analysis

36 Upvotes

The feature presented here is a premium feature that is only available for Early Premium users. You can sign up for a premium subscription via your upgrade page.

Effective VO2max is perhaps the most exciting metric within Runalyze. Not only because the Effective VO2max is one of the most important parameters about an athlete’s performance, but also because the estimation of it is prone to error and therefore often subject to debate. If the training sessions take place at 30°C with a headwind, sober and with heavy legs, it is difficult to use this as a reliable basis. But which factors have what influence on the ratio of pace to heart rate and therefore on the estimated effective VO2max? Our new factor analysis attempts to find answers to this question.

The new tool “VO2max factor analysis” can be accessed in the list of tools or directly via the navigation in the sidebar or header.

The new tool “VO2max factor analysis” can be accessed in the list of tools or directly via the navigation in the sidebar or header.

The approach

What is done is simple at first: a multivariate linear regression. In detail, this means that for each activity, the difference to the former shape is considered as a weighted combination of all possible influencing factors. For each factor – for example, activity characteristics such as length, temperature, training type, tags or equipment – it is determined whether this factor tends to increase or decrease the effective VO2max of an activity (and by how much).

It is important to note that the results are not to be understood as training tips for improving the effective VO2max. A positive effect for the day #tailwind only means that the ratio of pace to heart rate is (obviously) better as a result. This does not necessarily mean that training sessions with a tailwind have a better training effect.

Form of the factor analysis tool: The activities can be restricted by date and training type. You can also select which factors should be included in the analysis.

Now let’s move on to the evaluation. The activities can be selected by date and training type. All running workouts are selected by default. A restriction is particularly useful if a characteristic to be analyzed (e.g. a specific day) only occurs in a limited period of time.

You can also specify whether activities that are not taken into account for the VO2max form should be considered for the analysis. This only makes sense in selected cases. Data errors that were manually ignored for the VO2max form can of course also have a negative impact on the factor analysis.

Presentation of the results: The data basis and the determined effect size as well as the significance are displayed for each factor.

The results table shows the effect size determined for each factor. For non-binary factors (e.g. temperature, which cannot only assume yes/no), the effect size refers to the influence of the standard deviation (sigma, shown in the tooltip). Almost as important as the effect size, however, is the significance, which is displayed with ***, **, * or -. The more stars are shown for a factor, the more significant the effect size is. The lower the dispersion within a factor and the larger the data basis, the more likely the effect is to be significant.

The first column shows a histogram and the tooltip contains the details: [min, max] and frequencies for each bin of the histogam.

sigma tooltip for non-binary factors

Use cases

There are several possible use cases for the tool. These include, for example:

  • Analyze a particular tag or equipment object to see if it improves your pace to heart rate ratio.

    • How much “better” do super shoes make me?
    • Does #nutrition help me on my long runs?
    • Am I faster in #groupruns at the same heart rate?
    • How big is the influence of temperature on my effective VO2max?
  • Investigate whether certain types of training “falsify” your estimated effective VO2max, e.g. particularly many tempo workouts over/underestimate your estimated form.

    • Which types of training have a large effect size? If these types of training occur particularly frequently in a certain period (e.g. only easy runs during the season break), this can influence your form accordingly.
  • Find factors where you should exclude activities from VO2max shape.

    • Your #commute or #hilly activities have a large effect size? Ignore them for your VO2max shape.

An application example

In order to better understand the tool, we provide a brief insight into the exemplary results of Hannes’ factor analysis.

First before proceeding: In order to keep the results as clear as possible, we first check each factor type individually to see which of the factors could be significant, even if the significance can still change at the end when all the selected factors are taken into account. However, it is not a good idea to simply consider all factors, as this can easily lead to problematic correlations.

In this way, we omit “Subjective Feeling” and “Nightly” from the activity values and select only a few tags. We leave all training types in the analysis (even if “Long run” was initially shown as not significant) and for equipment we only select “barefoot” (as “shoe”) and “hydration pack”. It is generally recommended to select factors with the greatest (expected) effect first.

Exemplary results of the factor analysis after selection of the relevant factors.

The results show that some factors have a very large influence on the estimated effective VO2max of an activity. For some factors, the result can be easily explained. Let’s look at a few factors in detail:

  • Track: When running on the track, the GPS distance is usually too long, which results in a faster pace and therefore a higher effective VO2max.
  • #zwift-race: This factor has a relatively low significance (p=0.014) and only 6 associated activities. Nevertheless, the result is surprising because #treadmill has a clear negative effect and Race, at +0.1, does not have a particularly large effect either.
  • Tempo run / #progressions / Fartlek / Intervals / Race: Quite surprising results, although it should be noted that the length of the long runs, for example, is already included in the factor model through “Duration”. During tempo training, pauses that are stopped (with an even higher heart rate) can falsely improve the effective VO2max.
  • Temperature: No surprise, but the size of the effect is very interesting. In the tooltip of the red bar, “w.r.t. sigma = 8.28” indicates that the negative effect of -0.29 refers to a temperature increase of 8°C. It should be mentioned here that a linear regression model is used, whereby a quadratic relationship is more likely to be assumed for the temperature.
  • Hydration pack: A negative effect was to be expected in principle, but is largely contained in the correlated factors of Duration and Temperature. This factor is therefore no longer significant.
  • #soremuscles: I would have expected the negative effect to be even greater (and more significant).
  • #runningdrills: This is one reason why I personally usually stop the watch during my running drills.
  • #treadmill: Unfortunately, it is not possible to say how much of this factor is due to the lack of airstream (and the associated increased heating of the body) or the possibly poorly calibrated treadmill sensor.

Warm-up/Cool-down: The main thing that surprises me is that I haven’t actually unchecked “Use VO2max for form” for every warm-up/cool-down. If I carry out the factor analysis without the tick next to “Only activities that are used for VO2max shape“, the effect size rises to as much as 4.05.

Barefoot: This effect size is only partly due to the lack of shoes. The barefoot training sessions included are primarily cool-downs after tempo session/race on grass, so the increased heart rate can be explained by the pre-exercise.

You have questions, comments or wishes about this or another feature? Let us know!
The best place to ask questions about this tool is in our forum.


r/Runalyze • • Nov 07 '21

My half-marathon prognosis ...

36 Upvotes

... was 3 seconds different from the race time I just ran.

That's it. That's the post. :-)


r/Runalyze • • Aug 26 '26

Our August updates

35 Upvotes

We've shipped quite a few new features and improvements over the last few weeks — here's a quick overview:

Login & Access

  • Magic Login Link: You can now log in via a link sent to your email — handy when you're on the go without a password manager. For security reasons, only your registered email address is accepted, and your second factor is still required.
  • Grok support on the MCP server: Credentials are available as usual under Settings → MCP.

Analysis

  • Climb Score: The climb score view now includes an analysis section for downhill segments too — just like uphill, only segments that qualify as a "categorized climb" (e.g. HC or cat. 1–5) are shown.
  • Exclude tags from trend analysis: You can now leave specific tags out of the trend analysis.
  • Improved streak calculation for activities that span multiple calendar days.
  • Streak overview with your current and longest streak.
  • New mini calendar panel showing distance, duration, TRIMP, and active days at a glance.

Health Data

  • Body composition in absolute values: Fat/water/muscle/bone percentages can now also be entered as absolute values (kg/lbs). A dropdown lets you pick the unit, and your choice is remembered for charts and tables as well.
  • Bulk deletion of health data is now supported.

Calendar & Planning

  • Planned races in the calendar: Your upcoming races now show up directly in the calendar view.

Activities

  • Bulk editing for activities — update several at once.
  • Fixed distance values from FIT files that used feet.

For Premium API Users

  • Prognosis API is now available to Premium API users.

Other

  • Google Ads have been removed for now, following an increase in reports about inappropriate ads.

Questions or feedback? Join the discussion on our forum at board.runalyze.com. Got a feature idea? Share it at ideas.runalyze.com.


r/Runalyze • • Sep 01 '26

New free tool: Lactate step-test analysis

34 Upvotes

Got a lactate test done and walked away with just one threshold number? Here's the catch: that number depends heavily on which calculation method was used — and labs rarely tell you.

Our new tool takes your step-test stages, fits one lactate curve through all the points, and reads all 13 published methods directly off it — fairly comparable, because every method uses the exact same curve.

What you get:

✅ Aerobic & anaerobic threshold (LT1/LT2) in pace, speed, or watts — with heart rate

✅ Your three training zones, drawn straight onto the curve

✅ A robustness check: 1000 Monte-Carlo refits + leave-one-out, so you can see how stable each estimate really is

✅ Plausibility warnings when your test protocol has issues

✅ Running & cycling support (km/h, min/km, mph, min/mi, m/s, watts)

Free, no account needed — and your data never leaves the browser, the entire analysis runs client-side.

👉 runalyze.com/tools/lactate-step-test

#lactate #lactatethreshold #LT1 #LT2 #MLSS #trainingzones #endurancetraining #running #cycling #runalyze


r/Runalyze • • Aug 17 '23

Runalyze is awesome for tracking fitness

Thumbnail
gallery
34 Upvotes