The 2026 Valencia Half Marathon has taken place. The organiser’s 25 October report names Rodrigue Kwizera as the men’s winner in 58:03 and Sheila Chepkirui as the women’s winner in 1:03:51. For an individual runner, the next step is to open the [official 2026 ranking page](https://www.valenciaciudaddelrunning.com/en/half/2026-half-marathon-ranking/) and check the relevant record, not keep refreshing a pre-race entry list.
This guide explains how to use that source, why a race-day tracking display may differ from a result table, and how to avoid confusing bib validation with spectator access. It does not claim to have tested every function inside the mobile app or independently audited every finisher’s result.
Start with the correct event and year
Valencia’s half marathon and marathon have separate event information. Search results can also mix different editions. Before copying a time, check the event name, distance and year at the top of the page. A familiar logo or a runner’s name is not enough to establish that you have opened the right result.
The official 2026 ranking page is linked from the organiser’s own website. Use that route rather than an advertisement or an unsolicited message offering a result certificate. The organiser’s current post-race report confirms that the event has finished; older pages describing the forthcoming start are useful historical information, not a current race status.
If you are helping a friend find a result, ask for the bib number they used and how their name was registered. Do not request their account password or collect a date of birth just to help search a public classification. A public lookup and access to a runner’s account are different tasks.
Tracking and bib validation are different operations
The official app page describes live tracking and public, PIN-protected or hidden profiles. It also says the birth date in a runner’s registration must match the app account when validating that runner’s bib. This is an account-validation instruction; it is not an instruction for spectators to guess someone else’s personal details.
For spectators, the regulations describe lookup by name or bib, subject to the runner’s visibility choice. If a profile requires a PIN, obtain it from the runner. If the profile is hidden, respect that setting. The app’s information page describes its race-day rankings as unofficial and provides a route to results after the race.
The regulations explain another limitation: the default tracking uses chip readings at course sensors and estimates position between them from average speed. GPS tracking is an additional option when a runner carries a device. The moving marker should therefore not be treated as continuous, exact observation of a person’s location.
Are live Valencia Half Marathon rankings official?
The organiser distinguishes unofficial positions during the race from the post-race rankings. Now that the race has taken place, use the 2026 results link rather than an old screenshot of live tracking.
That distinction is useful for both spectators and publishers. A position displayed while waves are still moving through the course may change when timing data is processed. Athletes start in different waves, so a runner crossing the line earlier in clock time may not necessarily lead the net-time ranking. A live board can be incomplete while results are being reconciled, and a tracker can lag if a participant has not yet passed the next timing sensor.
For a final result, look for a classification published by the race organizer after the finish. Confirm the event year, category and whether the time is a gun time or chip/net time before comparing athletes. The event app and organizer’s results page are the primary places to check; a screenshot of a live board is not a replacement for the final table.
Why start waves complicate casual comparisons
The 2026 regulations scheduled waves from 8:25 a.m. through 9:27 a.m. local time. That range explains why two runners could be at very different places at the same wall-clock time without the map establishing which was running faster. The detailed schedule is linked below for historical reference; it is no longer a plan for an upcoming race.
For a worked example, imagine one runner crosses a start mat at 8:35 and finishes at 10:15. The elapsed time between those two passages is one hour and 40 minutes. Measuring from 8:25 instead would produce one hour and 50 minutes. The ten-minute difference comes from the chosen starting point, not from a change in the runner’s speed.
This is a fictional calculation, not a participant’s actual result or a statement about how a particular award is decided. It shows why a time needs a label. Copying the number while dropping the column heading can turn an accurate record into a misleading comparison.
What the course distance means
A half marathon is 21.0975 kilometres, which is about 13.1 miles. Valencia’s event page lists the distance as officially measured. That figure describes the race course, not the exact distance each runner’s watch will record. A GPS watch may show a little more because runners move around other participants, follow turns imperfectly or experience measurement variation in a dense urban setting.
If you are comparing a runner’s watch with an official result, use the organizer’s timing and course distance as the reference. A watch can help an individual manage pace, but small differences between devices do not prove that the official route was longer or shorter. Similarly, a pace estimate shown in an app between timing points is not the same thing as a certified split.
A runner’s watch and a results table answer different questions
A watch log may include the walk to the start, an accidentally delayed stop or an activity paused by the wearer. A result table uses the event’s timing process. Before concluding that either is wrong, check what period each is measuring. The difference may be in the start and stop points rather than the arithmetic.
Suppose a fictional runner starts a watch three minutes before crossing the start mat, then stops it one minute after finishing. That activity will include four minutes beyond the interval between the two mats. It would be misleading to treat the extra four minutes as evidence that the race timing system lost part of the performance.
Distance can cause a similar misunderstanding. If a watch reports a slightly different distance, its average pace calculation will use that recorded distance. The event’s pace calculation may use the official course length. A small difference in displayed pace is therefore not automatically a contradiction in the finishing time.
For a personal training note, keep both records with their labels: the race result as published, and the watch activity as recorded. If there is a substantial unexplained difference, preserve the evidence and ask the organiser for clarification. Do not silently edit one number to make the two agree.
### Gun time and chip time are not interchangeable
Race results can show more than one time. Gun time measures from the start signal for the relevant race or wave; chip time measures an individual runner’s passage across the start and finish timing mats. In a large event with staggered waves, those figures can differ by several minutes for someone who starts behind the first group. When quoting a result, copy the label shown in the organizer’s table instead of shortening every time to “finish time.”
For a spectator, a leaderboard sorted by one timing field may not match the order runners crossed the finish line. For a runner comparing a personal performance, net time may be the useful figure, but the race’s own official result remains the authority. Check the column definitions rather than assuming which field determines an award or category placing.
It is also sensible to wait before sharing a close finish. Timing providers may need to process records, resolve a missed mat or apply a disqualification under the published regulations. A provisional placement can change. Unless the organizer has marked a result final, call it provisional and link to the live source rather than announcing a definitive winner.
How to read a split without inventing an explanation
A split is most useful when you know whether it is cumulative or covers only the preceding section. Imagine a fictional results page shows 25 minutes at five kilometres and 51 minutes at ten kilometres. If these are cumulative times, the second five-kilometre section took 26 minutes, not 51. Subtracting adjacent cumulative values gives the interval.
That calculation shows a one-minute difference between the two sections. It does not establish why the difference occurred. The runner may have changed pace, encountered congestion or stopped briefly; the numbers alone cannot choose among those explanations. Ask the runner before turning a split into a story about their tactics or condition.
Check units as well. A pace in minutes per kilometre is different from minutes per mile. A display written as 5:00 represents five minutes, not five decimal minutes followed by an additional fraction. When converting a duration, turn it into seconds first if that helps avoid errors, then convert the result back into minutes and seconds.
For example, 26 minutes over five kilometres is 1,560 seconds divided by five, or 312 seconds per kilometre. That is 5:12 per kilometre. This is an original example for reading a result, not a pace attributed to anyone in the Valencia field.
What to do if a record appears missing or wrong
First, check the filters. A category selection, an event-year setting or a search spelling can hide a record that is present elsewhere in the table. Clear one filter at a time and retry the bib number. Avoid changing several things at once, because then you may not know which setting caused the mismatch.
If the record still appears incorrect, make a short evidence note. Include the event, year, bib, the field you believe needs checking and the value currently displayed. Keep a copy of the relevant page or screenshot with its date. An organiser can investigate a specific discrepancy more easily than a message saying only that the result is wrong.
Use the contact route linked from the official event website. Do not send identity documents or account credentials to an unfamiliar social-media account offering to correct results. If the organiser asks for supporting information, provide it through its stated process and keep your original records.
An unexplained blank should remain an unexplained blank until it is resolved. It does not, by itself, establish a disqualification, a medical problem or a failure to finish. Publishing one of those explanations without evidence could unfairly describe a runner’s experience.
Sharing a result responsibly
A useful result post identifies the event and year, names the timing field and links to the source. If the table is marked provisional, preserve that label. A screenshot can be helpful, but it may omit headings, filters or a later correction. The source link lets someone check the context that the cropped image leaves out.
For another person’s result, ask before adding personal details beyond the public sporting record. A runner may be happy to share a finishing time but not a live location, account screen or private message. Consent to follow someone during a race is not necessarily consent to publish their complete activity history afterwards.
Keep performance and interpretation separate. A time can be verified from a table. Whether it was a personal best, a recovery run or a disappointing day may require the runner’s own account and previous records. Do not supply an emotional story simply because it makes a more dramatic caption.
Entry lists, records and results
An entry list establishes who was expected to take part, not who actually finished. A personal best listed before the race is background, not a time achieved in Valencia. Once the event is over, the result source should take priority for claims about finishing order and performance on the day.
Record claims require the same precision. A season-leading mark, a course record, a national record and a world record are different descriptions. Use the term supported by the responsible source and retain any qualification about confirmation or ratification. Do not shorten every impressive result to “record” and assume the meaning will remain clear.
This guide reports only the two winning times stated by the organiser. It does not independently certify record eligibility or reproduce the full classification. The official result and any relevant governing-body decision should be consulted for those more specific questions.
Conclusion
The race is over, so the official 2026 ranking page is the appropriate starting point for checking an individual result. The app’s live display served a different purpose during the event. Distinguishing those sources, preserving time labels and respecting account privacy will resolve many common misunderstandings before they spread.
When something still does not match, document the exact issue and use the organiser’s contact route. A careful question supported by a bib number and the relevant field is more useful than a confident explanation invented from a delayed dot or a cropped screenshot.
### Sources and research note
Refreshed 26 October 2026, Asia/Dhaka, after the race. Sources: [official 2026 rankings](https://www.valenciaciudaddelrunning.com/en/half/2026-half-marathon-ranking/), [organiser’s 25 October race report](https://www.valenciaciudaddelrunning.com/en/chepkirui-sets-womens-world-leading-mark-2026-valencia-half-marathon/), [official app information](https://www.valenciaciudaddelrunning.com/en/half/descarga-app-medio-maraton-valencia/) and [2026 regulations](https://www.valenciaciudaddelrunning.com/en/half/regulations-valencia-half-marathon/). App instructions were checked as documentation, not by enrolling a runner or accessing private profiles. Worked examples are fictional. The illustration is original AI-generated conceptual artwork, not actual participants or a live race image.