| tk_Knock vs Paul | 37–12 | 75.51% |
| tk_Knock vs King | 35–8 | 81.40% |
| tk_Knock vs Lee | 29–14 | 67.44% |
| tk_Knock vs Hwoarang | 26–14 | 65.00% |
| tk_Knock vs Kazuya | 26–12 | 68.42% |
| tk_Knock vs Bryan | 26–8 | 76.47% |
| tk_Knock vs Asuka | 25–9 | 73.53% |
| tk_Knock vs Dragunov | 22–12 | 64.71% |
| tk_Knock vs Lars | 24–10 | 70.59% |
| tk_Knock vs Jin | 24–8 | 75.00% |
| tk_Knock vs Law | 25–6 | 80.65% |
| tk_Knock vs Lidia | 16–15 | 51.61% |
| tk_Knock vs Raven | 17–11 | 60.71% |
| tk_Knock vs Nina | 18–9 | 66.67% |
| tk_Knock vs Jun | 14–11 | 56.00% |
| tk_Knock vs Leroy | 11–8 | 57.89% |
| tk_Knock vs Reina | 13–6 | 68.42% |
| tk_Knock vs Azucena | 12–7 | 63.16% |
| tk_Knock vs Jack-8 | 14–4 | 77.78% |
| tk_Knock vs Lili | 9–9 | 50.00% |
| tk_Knock vs Leo | 13–5 | 72.22% |
| tk_Knock vs Zafina | 8–10 | 44.44% |
| tk_Knock vs Steve | 13–4 | 76.47% |
| tk_Knock vs Yoshimitsu | 13–3 | 81.25% |
| tk_Knock vs Eddy | 12–3 | 80.00% |
| tk_Knock vs Alisa | 9–5 | 64.29% |
| tk_Knock vs Claudio | 9–5 | 64.29% |
| tk_Knock vs Victor | 5–7 | 41.67% |
| tk_Knock vs Devil Jin | 7–3 | 70.00% |
| tk_Knock vs Kuma | 9–1 | 90.00% |
| tk_Knock vs Shaheen | 5–4 | 55.56% |
| tk_Knock vs Xiaoyu | 6–1 | 85.71% |
| tk_Knock vs Panda | 5–2 | 71.43% |
| tk_Knock vs Feng | 1–2 | 33.33% |
| tk_Knock vs Heihachi | 2–1 | 66.67% |
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.