Home Page News Predictions Matches Articles Education
Orlov, V
Finished
2
0
Betov, Sergey
Orlov, V
L
W
W
L
L
Challenger Mexico City
07.04.26
Nicolas Mejia
2–1
Vladyslav Orlov
Challenger Mexico City
06.04.26
Ivan Marrero Curbelo
1–2
Vladyslav Orlov
Challenger Mexico City
05.04.26
Samuel Alejandro Linde Palacios
1–2
Vladyslav Orlov
Challenger San Luis Potosi
31.03.26
Matias Soto
2–0
Vladyslav Orlov
Challenger Floridablanca-Bucaramanga
24.03.26
Vladyslav Orlov
0–2
Nicolas Villalon Valdes
Betov, Sergey
L
L
L
L
L
ATP Challenger Wuning, China Men Singles
05.04.26
Yusuke Takahashi
2–0
Sergey Betov
ATP Challenger Fujairah, UAE Men Singles
02.03.26
Tung-Lin Wu
2–0
Sergey Betov
ITF Tunisia M15 Monastir 6
18.02.26
Ergi Kirkin
2–0
Sergey Betov
ATP Challenger Manama 2, Bahrain Men Singles
23.11.25
Matthew Summers
2–0
Sergey Betov
ATP Challenger Soma Bay, Egypt Men Singles
16.11.25
Sergey Betov
0–2
Ivan Nedelko

Over the last matches Orlov, V holds wins - 2, losses - 3. Betov, Sergey on the other hand holds the following results from the latest games: wins - 0, losses - 5. Based on the games played a conclusion can be made that Orlov, V currently is in better form, unlike Betov, Sergey.

Orlov, V: Nicolas Mejia – (Loss 2:1), Ivan Marrero Curbelo – (Win 1:2), Samuel Alejandro Linde Palacios – (Win 1:2), Matias Soto – (Loss 2:0), Nicolas Villalon Valdes – (Loss 0:2).

Betov, Sergey: Yusuke Takahashi – (Loss 2:0), Tung-Lin Wu – (Loss 2:0), Ergi Kirkin – (Loss 2:0), Matthew Summers – (Loss 2:0), Ivan Nedelko – (Loss 0:2).

Both contenders have moved to the qualification_round_1 while beating strong opponents along the way. In tournaments as Shymkent each event is meaningful which is why a great battle awaits us.

Quick phrases
Go Orlov, V!✊
Orlov, V is on fire!💪
Cheering for Betov, Sergey all the way!📣
Go for it Betov, Sergey!
You're losers Orlov, V 😝
Betov, Sergey sucks 🍭
The game's gonna be hot! 🔥
I'm rooting for Orlov, V
I'm rooting for Betov, Sergey
I'm looking forward to an exciting tiebreak
Share your opinion with quick phrases or pass authorization and write your own
Quick comment (without authorization)