Wavu Wank

TEKKEN® 8 glicko2 Ratings &
Online Ranked Statistics
천마신공비기시체훼손

Ratings

Name history

천마신공비기시체훼손
철권접는 순서는 능지순
천마신공비기시체훼손 vs Hwoarang 88–77 53.33%
천마신공비기시체훼손 vs Kazuya 67–75 47.18%
천마신공비기시체훼손 vs Reina 60–68 46.88%
천마신공비기시체훼손 vs Dragunov 53–73 42.06%
천마신공비기시체훼손 vs Paul 49–58 45.79%
천마신공비기시체훼손 vs King 53–51 50.96%
천마신공비기시체훼손 vs Bryan 57–47 54.81%
천마신공비기시체훼손 vs Asuka 36–53 40.45%
천마신공비기시체훼손 vs Lili 40–44 47.62%
천마신공비기시체훼손 vs Jin 29–48 37.66%
천마신공비기시체훼손 vs Heihachi 33–43 43.42%
천마신공비기시체훼손 vs Feng 37–38 49.33%
천마신공비기시체훼손 vs Victor 37–36 50.68%
천마신공비기시체훼손 vs Azucena 28–32 46.67%
천마신공비기시체훼손 vs Steve 20–39 33.90%
천마신공비기시체훼손 vs Jun 35–24 59.32%
천마신공비기시체훼손 vs Yoshimitsu 19–37 33.93%
천마신공비기시체훼손 vs Law 24–30 44.44%
천마신공비기시체훼손 vs Lee 19–34 35.85%
천마신공비기시체훼손 vs Devil Jin 17–28 37.78%
천마신공비기시체훼손 vs Nina 19–26 42.22%
천마신공비기시체훼손 vs Leo 25–18 58.14%
천마신공비기시체훼손 vs Clive 21–22 48.84%
천마신공비기시체훼손 vs Lidia 18–24 42.86%
천마신공비기시체훼손 vs Eddy 13–25 34.21%
천마신공비기시체훼손 vs Claudio 16–20 44.44%
천마신공비기시체훼손 vs Leroy 17–18 48.57%
천마신공비기시체훼손 vs Alisa 16–17–1 48.48%
천마신공비기시체훼손 vs Lars 13–17 43.33%
천마신공비기시체훼손 vs Xiaoyu 10–16 38.46%
천마신공비기시체훼손 vs Jack-8 10–12 45.45%
천마신공비기시체훼손 vs Raven 5–17 22.73%
천마신공비기시체훼손 vs Kuma 7–13 35.00%
천마신공비기시체훼손 vs Shaheen 1–17 5.56%
천마신공비기시체훼손 vs Zafina 6–9 40.00%
천마신공비기시체훼손 vs Panda 7–6 53.85%

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.