| 风林火山 vs Jin | 94–91 | 50.81% |
| 风林火山 vs Kazuya | 84–88 | 48.84% |
| 风林火山 vs King | 48–59 | 44.86% |
| 风林火山 vs Reina | 56–51 | 52.34% |
| 风林火山 vs Steve | 46–42 | 52.27% |
| 风林火山 vs Hwoarang | 43–44 | 49.43% |
| 风林火山 vs Law | 43–42 | 50.59% |
| 风林火山 vs Eddy | 37–43 | 46.25% |
| 风林火山 vs Bryan | 27–52 | 34.18% |
| 风林火山 vs Yoshimitsu | 30–41 | 42.25% |
| 风林火山 vs Paul | 30–34 | 46.88% |
| 风林火山 vs Asuka | 30–32 | 48.39% |
| 风林火山 vs Heihachi | 35–27 | 56.45% |
| 风林火山 vs Dragunov | 22–34 | 39.29% |
| 风林火山 vs Xiaoyu | 23–32 | 41.82% |
| 风林火山 vs Nina | 22–30 | 42.31% |
| 风林火山 vs Devil Jin | 19–31 | 38.00% |
| 风林火山 vs Lili | 25–23 | 52.08% |
| 风林火山 vs Jun | 20–27 | 42.55% |
| 风林火山 vs Feng | 14–28 | 33.33% |
| 风林火山 vs Victor | 19–23 | 45.24% |
| 风林火山 vs Azucena | 19–21 | 47.50% |
| 风林火山 vs Lidia | 21–19 | 52.50% |
| 风林火山 vs Lars | 13–25 | 34.21% |
| 风林火山 vs Leo | 19–18 | 51.35% |
| 风林火山 vs Claudio | 14–21 | 40.00% |
| 风林火山 vs Alisa | 9–20 | 31.03% |
| 风林火山 vs Lee | 16–12 | 57.14% |
| 风林火山 vs Leroy | 10–16 | 38.46% |
| 风林火山 vs Shaheen | 13–12 | 52.00% |
| 风林火山 vs Zafina | 6–19 | 24.00% |
| 风林火山 vs Raven | 15–9 | 62.50% |
| 风林火山 vs Jack-8 | 12–11 | 52.17% |
| 风林火山 vs Kuma | 9–9 | 50.00% |
| 风林火山 vs Panda | 2–5 | 28.57% |
| 风林火山 vs Clive | 3–2 | 60.00% |
| 风林火山 vs Fahkumram | 5–0 | 100.00% |
| 风林火山 vs Armor King | 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.