| YaDa419 vs Jin | 27–25 | 51.92% |
| YaDa419 vs Heihachi | 14–30 | 31.82% |
| YaDa419 vs King | 17–26 | 39.53% |
| YaDa419 vs Steve | 25–17 | 59.52% |
| YaDa419 vs Kazuya | 11–27 | 28.95% |
| YaDa419 vs Lars | 17–14 | 54.84% |
| YaDa419 vs Miary Zo | 18–12 | 60.00% |
| YaDa419 vs Bryan | 15–8 | 65.22% |
| YaDa419 vs Reina | 17–6 | 73.91% |
| YaDa419 vs Lili | 8–13 | 38.10% |
| YaDa419 vs Hwoarang | 9–8 | 52.94% |
| YaDa419 vs Xiaoyu | 9–7 | 56.25% |
| YaDa419 vs Yoshimitsu | 1–14 | 6.67% |
| YaDa419 vs Feng | 5–10 | 33.33% |
| YaDa419 vs Lee | 5–10 | 33.33% |
| YaDa419 vs Shaheen | 2–12 | 14.29% |
| YaDa419 vs Eddy | 4–10 | 28.57% |
| YaDa419 vs Paul | 4–8 | 33.33% |
| YaDa419 vs Asuka | 7–5 | 58.33% |
| YaDa419 vs Dragunov | 5–7 | 41.67% |
| YaDa419 vs Armor King | 3–9 | 25.00% |
| YaDa419 vs Law | 4–6 | 40.00% |
| YaDa419 vs Devil Jin | 1–9 | 10.00% |
| YaDa419 vs Victor | 4–5 | 44.44% |
| YaDa419 vs Jack-8 | 4–4 | 50.00% |
| YaDa419 vs Claudio | 3–5 | 37.50% |
| YaDa419 vs Nina | 5–3 | 62.50% |
| YaDa419 vs Kuma | 4–4 | 50.00% |
| YaDa419 vs Lidia | 6–2 | 75.00% |
| YaDa419 vs Clive | 4–3 | 57.14% |
| YaDa419 vs Azucena | 3–3 | 50.00% |
| YaDa419 vs Raven | 1–4 | 20.00% |
| YaDa419 vs Leo | 0–4 | 0.00% |
| YaDa419 vs Alisa | 0–4 | 0.00% |
| YaDa419 vs Jun | 3–0 | 100.00% |
| YaDa419 vs Fahkumram | 2–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.