Clan | Result | Opponent | Date | ||
---|---|---|---|---|---|
War clan
血流千里
0 xp 0 % 0 |
lose
10 vs 10 |
wolf clans
30 100 % |
2019-08-20
1914d ago
|
||
War clan
血流千里
0 xp 0 % 0 |
lose
5 vs 5 |
railla king
6 40 % |
2019-08-18
1917d ago
|
||
War clan
血流千里
6 xp 18.3 % 3 |
lose
10 vs 10 |
Маневичi ITT
20 71.1 % |
2019-06-14
1982d ago
|
||
War clan
血流千里
59 xp 11.5 % 10 |
win
30 vs 30 |
Mammiii 2.0
0 0 % |
2019-06-11
1984d ago
|
||
War clan
血流千里
19 xp 26.1 % 23 |
lose
30 vs 30 |
等王归
29 32.7 % |
2019-05-30
1996d ago
|
||
War clan
血流千里
8 xp 26.3 % 10 |
lose
15 vs 15 |
våran fina clan
12 26.7 % |
2019-05-18
2008d ago
|
||
War clan
血流千里
6 xp 11.8 % 2 |
lose
15 vs 15 |
123(分)
7 16.7 % |
2019-05-11
2015d ago
|
||
War clan
血流千里
76 xp 39.7 % 46 |
win
40 vs 40 |
Black campions
9 9.5 % |
2019-03-29
2058d ago
|
||
War clan
血流千里
4 xp 20 % 3 |
lose
5 vs 5 |
rkp riders
3 29.8 % |
2019-02-26
2089d ago
|
||
War clan
血流千里
2 xp 13.4 % 3 |
lose
10 vs 10 |
ОДинОКий ВОЛК >
28 99.5 % |
2019-02-24
2091d ago
|
||
War clan
血流千里
38 xp 59.8 % 7 |
lose
5 vs 5 |
黄鹤楼
10 77.2 % |
2019-02-22
2094d ago
|
||
War clan
血流千里
104 xp 87.1 % 26 |
win
10 vs 10 |
king fighter
4 16.4 % |
2019-02-19
2096d ago
|
||
War clan
血流千里
0 xp 0.4 % 0 |
lose
5 vs 5 |
机车夹克
12 86.4 % |
2019-02-17
2098d ago
|
||
War clan
血流千里
0 xp 0 % 0 |
lose
5 vs 5 |
Chee Zitz
15 100 % |
2019-02-15
2101d ago
|
||
War clan
血流千里
96 xp 78.8 % 9 |
win
5 vs 5 |
Chung
9 63.8 % |
2019-02-13
2103d ago
|
||
War clan
血流千里
5 xp 31.8 % 5 |
lose
5 vs 5 |
indian warriors
11 74 % |
2019-02-10
2105d ago
|
||
War clan
血流千里
91 xp 80.2 % 10 |
win
5 vs 5 |
ROMAN REINGS
0 0.8 % |
2019-02-08
2108d ago
|
||
War clan
血流千里
91 xp 88.4 % 12 |
win
5 vs 5 |
仙居。
5 38.2 % |
2019-02-06
2109d ago
|
Event | Time |
---|
This content is not affiliated with, endorsed, sponsored, or specifically approved by Supercell and Supercell is not responsible for it. For more information see Supercell’s Fan Content Policy: www.supercell.com/fan-content-policy. This website uses cookies and may store your personal information, more details in Privacy Policy.