Jiri Lehecka and Rafael Jodar play Sunday, October 11, 2026, with a 10:00 PM ET start in Shanghai. The market has Lehecka at -112, which is close to a coin flip with a small vig attached. Any Jiri Lehecka vs Rafael Jodar prediction has to start with the obvious complication: Jodar already beat Lehecka once this year, on this same hard-court surface.
That was Montreal, August 8, a 6-3 6-3 win that still shapes how bettors see this rematch. But two months is a long time on tour, and both players have played a lot of tennis since then. The model takes a side here. It just does not take a swing.
Why the model leans Lehecka
Lehecka's last three weeks have been a run, not a blip. He reached the Tokyo final, beating Zizou Bergs, Ugo Humbert, qualifier Adolfo Daniel Vallejo and Valentin Vacherot before losing a tight two-setter to Carlos Alcaraz, 6-7(4) 4-6, after leading 4-2 in the first-set tiebreak. He hit seven aces in that final and was broken only twice. Against Vacherot in the semifinal he faced zero break points.
His Shanghai opener kept that going. Lehecka beat Nuno Borges 6-3 3-6 6-3, winning 80% of his first-serve points and 63% on his second, while facing just one break point across the match. That is a clean, earned result against a capable opponent, not a walkover.
The case for Jodar
The Montreal result is the reason this line is close at all. Jodar's path there was built on holding behind his own serve and finishing points with his forehand from mid-court, where he won 13 of 17 such points, while his return broke Lehecka two or three times over the match. If Jodar reproduces that pattern, mid-court forehand and a return that finds Lehecka's serve, the rematch looks a lot like the first meeting.
The problem is recency. Since late September, Jodar is 1-3 at tour level on hard courts, including a lopsided Tokyo exit to the same Vallejo that Lehecka also beat. His Shanghai opener was his first tour-level win since mid-August, and it was not comfortable: he faced 10 break points against the No. 54 and saved nine of them, winning the total-points count by just 83-78. He did beat Alexander Bublik in the Laver Cup in late September, so the level can resurface. It just has not shown up consistently since Montreal.
The number that matters
Zoom out to twelve-month hard-court form and the gap is modest but real. Lehecka holds serve 86% of the time to Jodar's 77%, and gets broken 20% of the time to Jodar's 28%. Lehecka has also done it against a tougher slate of opponents by the model's opponent-quality measure. The serve-return matchup favors him too: Lehecka is 10-3 on hard against low-serve baseliners, holding 85% and breaking 26% in those matches, while Jodar is 2-4 against first-strike servers and has broken only 17% of their service games. With a 10.8% ace rate, Lehecka fits that first-strike profile, and Jodar's hard-court losses have tended to cluster against exactly that kind of server.
Workload cuts against Lehecka on paper. He has played six matches in eleven days to Jodar's two in ten. But his three matches in Tokyo before the final were short, and he had three days off heading into Shanghai, so the physical case is not as lopsided as the raw count suggests.
The verdict
Put together, the fresher evidence favors Lehecka over the Montreal result, and the market price of -112 reflects how close the book still sees it. This is a PASS. No official card action is going out on this one, and that is not a soft lean or a quiet preference, it is simply not a bet we are making tonight. The reasoning above explains the lean; it does not explain the price, and we are not going to guess at the second part.
- Event · Shanghai · ATP (2026) · Sunday, October 11, 2026 · 10:00 PM ET
- Market · Jiri Lehecka -112 — recorded when the pick was posted
- Model · T Money, Botcappers' AI Tennis model — how it is built and what it does not know
- Record · every pick is timestamped before the event and graded in public, win or lose
- Statistics · the model's own match/game database, current to the posting time above. Figures a reader cannot open here are internal to that database, not published third-party data.

