Running pace is a way to describe how long you take to cover a unit of distance. A display of 7:00 min/km means seven minutes for each kilometre at that moment or across the measured activity, depending on the screen. A display of 11:16 min/mi represents approximately the same speed in miles. The number is useful, but it is not a grade, a definition of who counts as a runner, or a complete description of effort.
Beginners often meet pace in several places at once: a watch shows current pace, an app shows average pace, a training plan says “easy,” and an event asks for an estimated finish time. Those values can disagree without any one of them being dishonest. GPS movement, hills, weather, pauses, unit settings, treadmill calibration, and the difference between moving and elapsed time all influence what appears.
The useful principle: use pace as one piece of information alongside breathing, perceived effort, conditions, and the purpose of the session. A faster number is not automatically better, and no pace guarantees completion, safety, fitness, proof approval, or a particular result.
Running pace in one minute
- Pace is time divided by distance. If 5 kilometres takes 35 minutes, average pace is 7:00 min/km.
- Lower pace numbers are faster. Six minutes per kilometre is faster than seven minutes per kilometre because each kilometre takes less time.
- Speed reverses that relationship. Higher kilometres per hour or miles per hour are faster.
- Average pace summarizes a whole recorded period. Current or instant pace estimates what is happening now and can fluctuate sharply.
- A split is one segment. Kilometre, mile, or lap splits show how pace changed across an activity.
- Easy is an effort, not one universal number. A conversational pace can vary by runner, route, weather, fatigue, disability, and day.
- Event pace needs context. Course, cut-off, proof field, timing method, and whether the activity is virtual or onsite can all matter.
Start with the arithmetic, then compare it with how the session felt. If you are choosing an event as well as learning pace, use the distance-choice guide and browse current Events.
How this guide was prepared
This guide was reviewed in July 2026 using documented guidance from the US Centers for Disease Control and Prevention, the American College of Sports Medicine, the UK National Health Service, World Athletics, and Strava, together with documented HelloRun event and result behavior. It is general educational information, not individualized coaching, medical advice, a laboratory test, or a claim that one device was independently tested against another.
CDC and ACSM describe the talk test and perceived exertion as practical ways to assess relative intensity. NHS Couch to 5K uses a flexible walk-run progression rather than requiring a starting pace. World Athletics advises adjusting pace for extreme weather and using perceived effort when conditions make pace misleading. Strava documents how moving time and elapsed time can produce different calculations.
These sources explain useful principles; they do not provide a universal pace chart for every person. Training response, disability, age, pregnancy, health conditions, medication, recent illness, and injury history can affect what is appropriate. Seek qualified guidance when your circumstances warrant it, and use local medical or emergency services for severe or unexplained symptoms.
What running pace means
Pace answers the question, “How much time did each unit of distance take?” Running apps commonly express it as minutes and seconds per kilometre or per mile. If you cover 1 kilometre in 8 minutes 30 seconds, the pace is 8:30 min/km. If you cover 1 mile in 12 minutes, it is 12:00 min/mi.
The slash can be read as “per.” The unit matters: 8:00 min/km is not the same as 8:00 min/mi. A kilometre is shorter than a mile, so copying a number without its unit can create a large misunderstanding. Keep the unit beside the value in a plan, screenshot, message, or event estimate.
Pace may refer to an entire activity, a segment, or an estimate at one instant. Read the label before comparing screens. “Average pace” across a run can include different segments depending on how the platform treats pauses. “Lap pace” covers the current or completed lap. “Grade-adjusted pace” is a model, not the actual time per unit measured on level ground.
Pace, speed, effort, and finish time are different
Pace
Pace is duration per unit distance. A smaller time per kilometre or mile represents faster movement. It is especially convenient for planning splits and estimating how long a known distance could take if the pace were maintained.
Speed
Speed is distance per unit time, such as kilometres per hour. A larger speed is faster. Treadmills often display speed while outdoor running apps emphasize pace. The two describe the same movement from opposite directions, but conversion errors are common.
Effort
Effort describes how demanding the activity feels or how the body responds. Two runs at 7:00 min/km can have different effort because of heat, hills, wind, sleep, surface, or accumulated fatigue. Two runners at the same effort can have very different pace numbers.
Finish time
Finish time is the total duration for the event distance under its timing rules. It can be estimated from pace, but a prediction assumes that the pace is maintained and the distance is accurate. Water stops, congestion, hills, navigation, pauses, and fatigue can change the result.
How to calculate pace
The formula is simple: divide total time by distance. The careful part is converting time into one consistent unit before dividing.
Example: 5K in 35 minutes
- Total time is 35 minutes.
- Distance is 5 kilometres.
- 35 divided by 5 equals 7.
- Average pace is 7:00 min/km.
Example: 5K in 37 minutes 30 seconds
- Convert the 30 seconds to half a minute: 37.5 minutes.
- Divide 37.5 by 5: 7.5 minutes per kilometre.
- Convert the decimal half-minute back to seconds: 30 seconds.
- Average pace is 7:30 min/km.
Example: 3.1 miles in 40 minutes
Divide 40 by 3.1 to get about 12.903 minutes per mile. The decimal .903 is not 90 seconds. Multiply .903 by 60 to get about 54 seconds, producing approximately 12:54 min/mi. Small differences can appear if the displayed distance was rounded.
A calculator or trusted app is convenient, but understanding the steps helps you spot a unit mistake. Do not round every split before calculating an overall average; use the original total time and distance where possible.
How to convert pace and speed
For metric pace, speed in km/h is 60 divided by minutes per kilometre. A pace of 6:00 min/km corresponds to 10 km/h. A pace of 7:30 min/km is 7.5 minutes per kilometre, so 60 divided by 7.5 equals 8 km/h.
To convert speed to metric pace, divide 60 by km/h. A treadmill set to 9 km/h corresponds to about 6.667 minutes per kilometre. Convert .667 minutes to about 40 seconds, giving roughly 6:40 min/km.
For miles, pace in minutes per mile is 60 divided by miles per hour. A speed of 5 mph corresponds to 12:00 min/mi. Converting between kilometre and mile pace also requires the distance conversion: one mile is about 1.609 kilometres. Use a calculator rather than relying on a memorized approximation when an event field must be accurate.
Treadmill belt speed, watch estimates, and footpod readings can disagree. The conversion only translates the displayed number; it does not prove that the machine or device measured distance perfectly.
Average, current, lap, moving, and elapsed pace
Current or instant pace
Current pace reacts to recent location samples. Consumer GPS does not know your position with perfect continuity, so the number can jump when turning, passing buildings, moving under trees, or starting from rest. Chasing every fluctuation can create erratic running. A smoothed lap or rolling pace may be easier to use when the device supports it.
Average pace
Average pace divides a selected duration by a selected distance. The key question is which duration the platform selected. A watch may show the average while its timer is actively running; an app may later recalculate using moving time.
Lap or split pace
Lap pace summarizes one kilometre, mile, track lap, or manually marked segment. It responds more slowly than instant pace and makes changes across the activity visible. Auto-lap depends on device distance, so a GPS kilometre may not line up exactly with a physical course marker.
Moving pace and elapsed pace
Moving time attempts to count periods of movement. Elapsed time includes the full span from start to finish, including stops. Strava explains that its calculations can depend on activity type, recording method, and whether an activity is treated as a race. An event may rank elapsed time, imported moving time, chip time, gun time, or another configured field. Do not substitute one for another without checking the rules.
Read splits without judging every kilometre
Splits reveal the shape of a run. If five kilometre splits are 7:20, 7:15, 7:10, 7:05, and 7:00, the runner gradually became faster. This is often called a negative split because the later portion is quicker than the earlier portion. If the later splits slow, it is a positive split. Even splits stay relatively consistent.
Those labels describe the data, not whether the session succeeded. A hill in kilometre four can make the split slower at the same effort. Waiting at a crossing can affect elapsed time. A planned walk break can be appropriate. Trail kilometres should not be judged as though they were identical track laps.
Look for patterns across comparable runs rather than treating one split as a verdict. Ask whether the early pace matched the plan, whether effort rose sharply, whether conditions changed, and whether the final part remained controlled. Splits are most useful when paired with notes about route, weather, pauses, and perceived effort.
Use the talk test and perceived effort
CDC describes the talk test as a way to assess relative intensity: during moderate activity, a person can generally talk but not sing; at vigorous intensity, only a few words may be possible before pausing for breath. ACSM also presents steady conversation as a practical signal associated with moderate aerobic effort.
For a beginner's easy session, comfortable sentences are often more useful than forcing a pace copied from another runner. “Easy” can slow on an uphill, in humidity, after poor sleep, or while returning from a break. Walk breaks can keep the intended effort manageable. The pace may improve over time, but improvement is not guaranteed and should not be forced from one session to the next.
Perceived effort can use plain language: very easy, easy, steady, hard, and very hard. Numbers can be added, but avoid turning a subjective scale into a medical measurement. If the session calls for easy running and talking becomes difficult, reducing speed, walking, or stopping may be the appropriate response.
Common training pace labels
Easy or conversational
An easy run supports repeatable activity at a controlled effort. The runner should not need to prove fitness on every outing. Pace varies substantially among people and across conditions, so this guide does not publish a universal easy-pace table.
Steady
Steady usually means controlled but more purposeful than easy. Its exact meaning varies by coach or plan. Read the plan's definition rather than assuming that every use refers to the same intensity.
Tempo or threshold
These terms are used inconsistently. They often describe sustained work harder than easy pace but below an all-out effort. A beginner does not need to derive a threshold number from a race result without context. When a plan includes this work, follow its effort description and qualified guidance.
Intervals
Intervals alternate defined work and recovery. The appropriate pace depends on interval duration, recovery, purpose, surface, and experience. Short repetitions are not a license to sprint uncontrollably. Warm-up, recovery, and form matter more than matching another person's number.
Event or race pace
Event pace is the planned average for a specific distance and setting. A sustainable 5K pace is not automatically sustainable for 10K or 21K. Virtual routes and onsite courses also differ, so a goal should reflect the actual course, conditions, support, and timing method.
Why the same effort produces different pace
- Heat and humidity: add physiological demand. World Athletics advises slowing and using perceived effort when extreme weather makes normal pace inappropriate.
- Wind: changes the cost of maintaining speed and can make outbound and return splits look very different.
- Elevation: uphill pace usually slows at a similar effort, while downhill running has its own demands and risks.
- Surface: trail, sand, grass, wet pavement, snow, and treadmill belts do not behave like a dry level road.
- Congestion and crossings: alter rhythm and elapsed time even when fitness is unchanged.
- Sleep, stress, and recovery: can change perceived difficulty. A slower easy day may be the correct decision.
- Accessibility and movement pattern: mobility devices, guide support, planned rests, and individual movement strategies affect pace comparisons.
Do not use a warm-weather slowdown, hilly split, or walk break as evidence of failure. Compare like with like where possible, and prioritize current conditions over a target generated on a different day.
GPS and treadmill pace are estimates
Outdoor devices estimate distance from recorded positions and processing rules. Tall buildings, tunnels, tree cover, tight turns, device placement, battery settings, autopause, and signal acquisition can change the track. A small distance difference changes calculated pace even when total time is identical.
Indoor devices cannot rely on a normal outdoor GPS track. A treadmill reports belt-based distance according to its calibration; a watch may estimate from arm movement or a learned stride; a footpod uses another method. Their totals may disagree without proving which one is universally correct.
Test the device before an event, wait for the expected outdoor signal where appropriate, choose the correct activity profile, and preserve the original record. For app options, see Best Apps to Track Your Virtual Run. Never edit evidence merely to make two devices match.
Build a personal pace reference safely
- Choose a familiar, reasonably level route or permitted treadmill setting.
- Record several easy sessions rather than one all-out test.
- Note distance, total time, displayed pace unit, route, weather, stops, and perceived effort.
- Identify the range in which conversation stayed comfortable.
- Repeat under similar conditions before treating the range as useful.
- Update the reference when conditions, health, training, or equipment change.
A personal reference is descriptive, not a permanent prescription. If your comfortable pace varies from 7:40 to 8:20 min/km across ordinary runs, that range may be more useful than forcing 8:00 exactly. Walk-run sessions can be referenced by total average pace while also recording the chosen intervals.
Do not use an exhausting time trial as the only basis for every training pace. Beginners can build a valuable reference from repeatable easy movement and the flexible beginner 5K plan.
Estimate an event pace without making a promise
Begin with recent activities that resemble the event in distance, surface, elevation, and conditions. A comfortable 3K on a cool flat route is incomplete evidence for a hot hilly 10K. Consider whether the goal is completion, consistent effort, or performance.
To estimate finish time, multiply pace by distance. At 7:30 min/km, a mathematically even 5K is 37:30 and a 10K is 1:15:00. That does not mean both distances are equally sustainable. The calculation is arithmetic, not a physiological prediction.
Allow for the event setting. Onsite starts can include crowding and course markers; virtual runs can include crossings, navigation, and runner-managed support. If an organizer asks for an estimated time to assign a start wave, provide an honest, conservative estimate based on recent relevant activity, not an aspirational number chosen to enter a faster group.
A simple pacing plan for a first event
A practical completion plan is to begin controlled, settle into a repeatable effort, and review how you feel after the early section. Starting faster than a recent sustainable effort because of excitement can make the later distance harder. Planned walk breaks can begin before fatigue becomes severe when the event permits them.
- Opening section: use an effort that feels deliberately restrained while the body and route settle.
- Middle section: maintain a conversational or planned effort, adjusting for hills, weather, and surface rather than defending one number.
- Final section: only increase effort if conditions remain safe and the runner still feels controlled. Finishing at the planned effort is also a valid outcome.
This is not a guarantee of an even or negative split. Route and health decisions take priority. If the original event date or distance is no longer realistic, use a permitted later date, shorter category, planned walking, or another event rather than treating a pace target as an obligation.
Virtual and onsite pace are not automatically comparable
An onsite result can use gun time, chip time, officially measured course distance, or another event rule. The course may be certified, but onsite does not automatically mean certified. A virtual result may use consumer-device distance and an approved submitted duration on a runner-selected route.
Different elevation, turns, weather, surfaces, crossings, GPS devices, treadmill estimates, and pause rules make direct comparisons uncertain. A virtual 5K average pace can be meaningful within that event and personal record without becoming a certified qualifying result.
Check whether the event ranks elapsed time or another verified field, whether walking or treadmills are allowed, and what evidence is accepted. Use Virtual Run vs Traditional Race for the broader format comparison.
Pace in HelloRun results and proof
HelloRun events use event-specific categories and rules. Registration can be free or paid; paid registration can involve an external transfer and manual payment-receipt review. HelloRun does not directly process that transfer. Payment evidence is separate from activity proof.
For a result, a runner may submit an accepted screenshot or a supported connected Strava activity. Screenshot entry can use OCR assistance, but the runner must confirm the extracted distance, duration, date, activity type, and other required fields. OCR is fallible and does not prove accuracy. Supported imported activity data is also validated against current eligibility rules.
Some eligible clean submissions may qualify for conditional approval; others require organizer or admin review. Pending is not an approved result. Configured race-result leaderboards can rank approved elapsed time within relevant groups, while accumulated leaderboards rank approved distance rather than pace. Certificates are event-dependent and are not guaranteed by displaying a pace.
Keep the original activity and read What Counts as Valid Run Proof? and How to Submit Run Proof Correctly. For standings, use the leaderboard guide.
Four practical pace examples
Example 1: a walk-run 5K
Lea completes 5K in 42 minutes using planned run and walk intervals. Her average is 8:24 min/km. That average describes the full session; it does not show that every kilometre or every running interval occurred at 8:24. She records the interval pattern and conversational effort so the number has context.
Example 2: hills change the splits
Omar's first two kilometres are 6:55 and 7:00 on level ground. The third climbs steadily and takes 7:50 at a similar effort. He does not accelerate dangerously to rescue the average. The slower split reflects the route demand, and the descent is approached with control rather than treated as free time.
Example 3: moving and elapsed time
Priya's app reports 30 minutes moving and 33 minutes elapsed for 4 kilometres after a safe stop at crossings. Moving pace is 7:30 min/km; elapsed pace is 8:15 min/km. Neither number should silently replace the other in an event field. She follows the event's required duration and preserves the source record.
Example 4: treadmill disagreement
Daniel's treadmill shows 5.00 km in 35 minutes, while his watch estimates 4.72 km. The treadmill pace converts to 7:00 min/km, but that calculation does not certify the machine. He checks the event's treadmill and evidence policy, keeps both originals, and submits the accepted source without altering either value.
Beginner pace mistakes to avoid
- Copying another runner's easy pace without considering relative effort.
- Confusing min/km with min/mi or pace with km/h.
- Reading 7.5 minutes as 7 minutes 5 seconds instead of 7 minutes 30 seconds.
- Chasing instant GPS pace through every fluctuation.
- Starting every run at an event effort and leaving no truly easy sessions.
- Using one exceptional workout as a guaranteed prediction.
- Ignoring heat, humidity, wind, hills, surface, pain, illness, or poor visibility to protect an average.
- Pausing or editing a record to produce a more attractive result rather than following event rules.
- Assuming a watch, app, treadmill, or calculator is perfectly accurate.
- Believing that a slower pace removes the need for route and personal-safety planning.
Before-run pace checklist
- Define the session purpose: easy movement, intervals, event practice, or completion.
- Choose kilometres or miles and confirm every device uses the intended unit.
- Check weather, air quality, route, surface, elevation, visibility, and local warnings.
- Choose an effort range and walk-break plan rather than one number that must be defended.
- Confirm GPS signal, battery, activity type, autopause choice, and treadmill mode.
- Know which screen shows current, lap, average, moving, or elapsed information.
- For an event, confirm the timing and proof field the organizer will review.
- Prepare a safe option to slow, shorten, stop, or reschedule.
After-run review checklist
- Save the original activity once and allow synchronization to finish.
- Compare total time, distance, unit, average pace, elapsed time, and splits.
- Add context: effort, weather, elevation, surface, stops, walk breaks, and device used.
- Look for broad patterns rather than judging the slowest split in isolation.
- Ask whether the session matched its intended purpose and left reasonable recovery.
- Do not diagnose a health problem or change an entire plan from one unusual reading.
- For virtual proof, retain readable required fields while protecting unnecessary route and profile data.
- If a result is pending or rejected, follow the displayed review or correction path rather than editing evidence.
When to stop focusing on pace
Stop watching the number when it distracts from traffic, crossings, an uncertain surface, severe weather, pain, dizziness, faintness, chest discomfort, severe or unusual breathing difficulty, confusion, or another concerning symptom. Reach safety and obtain appropriate medical or emergency help through local services when needed.
Also set pace aside during an easy day when the device number is causing you to run harder than the intended effort. A watch can be covered, alerts can be widened, or the activity can be guided by conversation and time. Technology should support the session, not override judgment.
For route, low-light, weather, and emergency preparation, read the running safety guide. General guidance cannot guarantee safety or replace individual professional advice.
Frequently asked questions
What is a good running pace for a beginner?
There is no universal good number. A useful beginner pace supports the intended session and a manageable effort. For easy activity, the ability to speak in comfortable sentences is more informative than matching another person's pace.
Why does a lower pace number mean faster?
Pace measures time required for one unit. Taking six minutes for a kilometre is faster than taking seven. Speed uses the opposite direction: more kilometres per hour is faster.
Should I use min/km or min/mi?
Use the unit required by your plan or event and one you understand consistently. Keep the unit visible whenever sharing a value.
Is average pace the same as moving pace?
Not always. Average pace depends on which time the platform divides by distance. Moving pace can exclude detected non-moving periods; elapsed pace includes the entire start-to-finish span.
Why is instant pace unstable?
It relies on recent position and timing estimates. GPS noise, turns, signal obstruction, and changes in speed can cause large short-term jumps. Lap pace or effort may be easier to follow.
Do walk breaks ruin average pace?
No. They become part of the overall result when included in the timing method. Planned walking can be an appropriate pacing strategy, although event rules decide whether the activity type is accepted.
Can I predict a 10K by doubling my 5K time?
The arithmetic gives a hypothetical time at identical pace, not a reliable guarantee. Maintaining the pace for twice the distance may be unrealistic, and course or weather differences matter.
Why do my treadmill and watch disagree?
They estimate distance differently and may have different calibration. Follow the event's accepted evidence rule and keep the original readings instead of forcing agreement.
Does faster pace mean better fitness?
Not by itself. Route, conditions, effort, recovery, device behavior, and session purpose matter. Fitness change is better considered across comparable repeated observations.
What pace should I use in hot weather?
This guide does not prescribe a number. Heat and humidity increase demand, so reduce effort, use local warnings, reschedule when appropriate, and prioritize symptoms and safety over a target.
Will HelloRun calculate an official qualifying pace?
No. HelloRun records event-specific reviewed results. A leaderboard is not certified timing, course measurement, a World Athletics ranking, or a qualifying result unless an accepting organization explicitly says otherwise.
Where should I start if I have not run before?
Use the beginner 5K plan, which starts with flexible walk-run sessions, or read first virtual-run preparation. Ask a qualified professional when your health circumstances call for individual guidance.
Official and platform sources
- CDC: Measuring Physical Activity Intensity
- American College of Sports Medicine: Monitoring Aerobic Exercise Intensity
- NHS: Couch to 5K
- World Athletics: Running Through Extreme Weather
- World Athletics: Advice for Beginner Runners
- Strava: Moving Time, Speed, and Pace Calculations
- HelloRun: How It Works
- HelloRun FAQ
- HelloRun Privacy Policy
Apps, devices, source guidance, and event rules can change. Recheck the live event page, recording interface, and linked sources before relying on a pace or submitting a result.
