Name history
| tmxla user | |
| CJFRNJSAKDRPA | |
| 동혁이엄마집가출 | |
| Ravenda85 | |
| ehdgurmother家出 | |
| ...... | |
| 솔로의제왕에디 | |
| Ravenda01 | |
| ㅤㅤㅤㅤㅤ | |
| 鉄拳初心者 | |
| 히트R.K.O | |
| Xarots01 | |
| .... |
| tmxla user vs Reina | 8–7 | 53.33% |
| tmxla user vs Jin | 8–4 | 66.67% |
| tmxla user vs Paul | 2–8 | 20.00% |
| tmxla user vs Devil Jin | 2–8 | 20.00% |
| tmxla user vs Law | 5–3 | 62.50% |
| tmxla user vs Lili | 5–3 | 62.50% |
| tmxla user vs Lars | 4–4 | 50.00% |
| tmxla user vs Jun | 4–4 | 50.00% |
| tmxla user vs King | 2–5 | 28.57% |
| tmxla user vs Xiaoyu | 3–4 | 42.86% |
| tmxla user vs Dragunov | 1–5 | 16.67% |
| tmxla user vs Azucena | 2–4 | 33.33% |
| tmxla user vs Victor | 3–3 | 50.00% |
| tmxla user vs Hwoarang | 2–3 | 40.00% |
| tmxla user vs Steve | 0–5 | 0.00% |
| tmxla user vs Alisa | 1–4 | 20.00% |
| tmxla user vs Claudio | 4–1 | 80.00% |
| tmxla user vs Kazuya | 1–3 | 25.00% |
| tmxla user vs Bryan | 2–1 | 66.67% |
| tmxla user vs Asuka | 1–2 | 33.33% |
| tmxla user vs Nina | 0–3 | 0.00% |
| tmxla user vs Jack-8 | 2–0 | 100.00% |
| tmxla user vs Zafina | 0–2 | 0.00% |
| tmxla user vs Clive | 0–2 | 0.00% |
| tmxla user vs Lee | 0–1 | 0.00% |
| tmxla user vs Kuma | 0–1 | 0.00% |
| tmxla user vs Leroy | 1–0 | 100.00% |
| tmxla user vs Eddy | 0–1 | 0.00% |
| tmxla user vs Heihachi | 0–1 | 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.