| Gekkejsk vs Reina | 24–33 | 42.11% |
| Gekkejsk vs Hwoarang | 17–32 | 34.69% |
| Gekkejsk vs King | 8–38 | 17.39% |
| Gekkejsk vs Law | 13–26 | 33.33% |
| Gekkejsk vs Jin | 11–25 | 30.56% |
| Gekkejsk vs Kazuya | 15–21 | 41.67% |
| Gekkejsk vs Bryan | 14–21 | 40.00% |
| Gekkejsk vs Yoshimitsu | 17–16 | 51.52% |
| Gekkejsk vs Steve | 11–19 | 36.67% |
| Gekkejsk vs Heihachi | 13–17 | 43.33% |
| Gekkejsk vs Eddy | 6–22 | 21.43% |
| Gekkejsk vs Dragunov | 14–12 | 53.85% |
| Gekkejsk vs Azucena | 9–17 | 34.62% |
| Gekkejsk vs Lidia | 6–19 | 24.00% |
| Gekkejsk vs Xiaoyu | 10–14 | 41.67% |
| Gekkejsk vs Lars | 6–17 | 26.09% |
| Gekkejsk vs Paul | 6–16 | 27.27% |
| Gekkejsk vs Lili | 8–14 | 36.36% |
| Gekkejsk vs Feng | 9–12 | 42.86% |
| Gekkejsk vs Alisa | 7–13 | 35.00% |
| Gekkejsk vs Clive | 5–15 | 25.00% |
| Gekkejsk vs Jun | 5–12 | 29.41% |
| Gekkejsk vs Asuka | 3–13 | 18.75% |
| Gekkejsk vs Leroy | 8–5 | 61.54% |
| Gekkejsk vs Victor | 3–7 | 30.00% |
| Gekkejsk vs Jack-8 | 3–6 | 33.33% |
| Gekkejsk vs Devil Jin | 3–4 | 42.86% |
| Gekkejsk vs Zafina | 1–6 | 14.29% |
| Gekkejsk vs Raven | 5–1 | 83.33% |
| Gekkejsk vs Shaheen | 3–2 | 60.00% |
| Gekkejsk vs Nina | 1–4 | 20.00% |
| Gekkejsk vs Leo | 2–2 | 50.00% |
| Gekkejsk vs Claudio | 0–4 | 0.00% |
| Gekkejsk vs Lee | 0–4 | 0.00% |
| Gekkejsk vs Kuma | 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.