Home Page News Predictions Matches Articles Education
Romano, Filippo
Finished
2
0
Bilozertsev, Nikita
Romano, Filippo
L
W
W
W
W
Challenger Cherbourg
15.03.26
Pavel Kotov
2–0
Filippo Romano
Challenger Cherbourg
14.03.26
Jurij Rodionov
1–2
Filippo Romano
Challenger Cherbourg
13.03.26
Clement Tabur
1–2
Filippo Romano
Challenger Cherbourg
12.03.26
Filippo Romano
2–1
Patrick Brady
Challenger Cherbourg
10.03.26
Raphael Perot
1–2
Filippo Romano
Bilozertsev, Nikita
L
L
W
L
W
ITF Egypt M15 Sharm Elsheikh 8
19.03.26
Bilozertsev, Nikita
1–2
Alessandro Pecci
ITF Egypt M15 Sharm Elsheikh 7
13.03.26
Alessandro Pecci
2–0
Bilozertsev, Nikita
ITF Egypt M15 Sharm Elsheikh 7
12.03.26
Bilozertsev, Nikita
2–0
Aleksandre Bakshi
Challenger Brisbane
02.02.26
Pavle Marinkov
2–0
Bilozertsev, Nikita
Challenger Brisbane
01.02.26
Duje Markovina
0–2
Bilozertsev, Nikita

Over the last games Romano, Filippo holds victories - 4, losses - 1. Bilozertsev, Nikita on the other hand ends the latest games with victories - 2, losses - 3. Based on this data we come to a conclusion that Romano, Filippo currently is in better form, in comparison to Bilozertsev, Nikita.

Romano, Filippo: Pavel Kotov – (Loss 2:0), Jurij Rodionov – (Win 1:2), Clement Tabur – (Win 1:2), Patrick Brady – (Win 2:1), Raphael Perot – (Win 1:2).

Bilozertsev, Nikita: Alessandro Pecci – (Loss 1:2), Alessandro Pecci – (Loss 2:0), Aleksandre Bakshi – (Win 2:0), Pavle Marinkov – (Loss 2:0), Duje Markovina – (Win 0:2).

Both opponents have moved to the qualification_round_1 while beating worthy opponents along the way. In tournaments as Split each event is extremely important which is why a great battle awaits us.

Quick phrases
Go Romano, Filippo!✊
Romano, Filippo is on fire!💪
Cheering for Bilozertsev, Nikita all the way!📣
Go for it Bilozertsev, Nikita!
You're losers Romano, Filippo 😝
Bilozertsev, Nikita sucks 🍭
The game's gonna be hot! 🔥
I'm rooting for Romano, Filippo
I'm rooting for Bilozertsev, Nikita
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)