| tom ate vs Jin | 17–31 | 35.42% |
| tom ate vs Hwoarang | 13–23 | 36.11% |
| tom ate vs Miary Zo | 9–24 | 27.27% |
| tom ate vs Reina | 13–19 | 40.62% |
| tom ate vs Steve | 16–15 | 51.61% |
| tom ate vs Jun | 16–15 | 51.61% |
| tom ate vs King | 9–18 | 33.33% |
| tom ate vs Law | 8–16 | 33.33% |
| tom ate vs Bryan | 9–11 | 45.00% |
| tom ate vs Victor | 8–12 | 40.00% |
| tom ate vs Heihachi | 10–9 | 52.63% |
| tom ate vs Azucena | 7–11 | 38.89% |
| tom ate vs Kazuya | 9–8 | 52.94% |
| tom ate vs Asuka | 10–7 | 58.82% |
| tom ate vs Lars | 5–12 | 29.41% |
| tom ate vs Eddy | 5–11 | 31.25% |
| tom ate vs Fahkumram | 6–9 | 40.00% |
| tom ate vs Lili | 4–9 | 30.77% |
| tom ate vs Dragunov | 5–5 | 50.00% |
| tom ate vs Lee | 7–3 | 70.00% |
| tom ate vs Armor King | 3–7 | 30.00% |
| tom ate vs Yoshimitsu | 0–9 | 0.00% |
| tom ate vs Nina | 5–4 | 55.56% |
| tom ate vs Raven | 1–8 | 11.11% |
| tom ate vs Xiaoyu | 2–6 | 25.00% |
| tom ate vs Jack-8 | 4–4 | 50.00% |
| tom ate vs Leo | 2–6 | 25.00% |
| tom ate vs Anna | 2–4 | 33.33% |
| tom ate vs Feng | 2–3 | 40.00% |
| tom ate vs Clive | 3–2 | 60.00% |
| tom ate vs Claudio | 3–0 | 100.00% |
| tom ate vs Zafina | 1–2 | 33.33% |
| tom ate vs Paul | 2–0 | 100.00% |
| tom ate vs Shaheen | 2–0 | 100.00% |
| tom ate vs Panda | 2–0 | 100.00% |
| tom ate vs Leroy | 1–0 | 100.00% |
Limitations
This data is often requested to give insight into which characters you have more trouble with than others, but it is not particularly helpful for that. The main issue is that it is heavily skewed by how strong the opponents you play are.
For example, this data suggests my worst matchup is clearly vs Reina, but that's just because most of those games are vs Yagami.
There is a way to account for this being worked on. The central idea is to assign each matchup a rating vs you which adjusts based on the result, much like the regular rating but also based on the rating of each player. With this, it would give a better summary of how well you perform vs each character.
In the meantime, this page is here to present the data as requested.