| DNASIREN vs Lidia | 34–43 | 44.16% |
| DNASIREN vs Hwoarang | 26–32 | 44.83% |
| DNASIREN vs Reina | 21–34 | 38.18% |
| DNASIREN vs Steve | 18–25 | 41.86% |
| DNASIREN vs Kazuya | 12–29 | 29.27% |
| DNASIREN vs Lili | 15–24 | 38.46% |
| DNASIREN vs King | 9–26 | 25.71% |
| DNASIREN vs Jin | 9–26 | 25.71% |
| DNASIREN vs Jun | 15–17 | 46.88% |
| DNASIREN vs Heihachi | 19–12 | 61.29% |
| DNASIREN vs Dragunov | 6–20 | 23.08% |
| DNASIREN vs Lars | 9–17 | 34.62% |
| DNASIREN vs Eddy | 8–18 | 30.77% |
| DNASIREN vs Yoshimitsu | 9–16 | 36.00% |
| DNASIREN vs Nina | 11–14 | 44.00% |
| DNASIREN vs Bryan | 7–17 | 29.17% |
| DNASIREN vs Paul | 7–13 | 35.00% |
| DNASIREN vs Asuka | 6–14 | 30.00% |
| DNASIREN vs Devil Jin | 9–11 | 45.00% |
| DNASIREN vs Law | 3–16 | 15.79% |
| DNASIREN vs Lee | 5–14 | 26.32% |
| DNASIREN vs Feng | 3–14 | 17.65% |
| DNASIREN vs Azucena | 9–8 | 52.94% |
| DNASIREN vs Alisa | 2–12 | 14.29% |
| DNASIREN vs Victor | 4–10 | 28.57% |
| DNASIREN vs Xiaoyu | 3–10 | 23.08% |
| DNASIREN vs Leroy | 3–9 | 25.00% |
| DNASIREN vs Jack-8 | 2–9 | 18.18% |
| DNASIREN vs Claudio | 3–5 | 37.50% |
| DNASIREN vs Shaheen | 6–2 | 75.00% |
| DNASIREN vs Leo | 2–5 | 28.57% |
| DNASIREN vs Zafina | 4–1 | 80.00% |
| DNASIREN vs Panda | 1–2 | 33.33% |
| DNASIREN vs Kuma | 1–1 | 50.00% |
| DNASIREN vs Raven | 0–2 | 0.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.