Location:
War freq.:
unknown
Members:
0/50
Level:
1
Win/Tie/Loss:
4/1/11
Points:
464
Streak:
1
Trophies:
0
| Level | Name | Donations | Received | Trophies |
|---|
| Clan | Result | Opponent | Date | ||
|---|---|---|---|---|---|
|
War clan
弑神领地
66 xp 59.4 % 8 |
|
win
5 vs 5 |
|
™chinini jijiji
4 37 % |
2020-03-21
1699d ago
|
|
War clan
弑神领地
14 xp 40 % 6 |
|
lose
5 vs 5 |
|
Universal Thugs
9 66.8 % |
2020-03-15
1705d ago
|
|
War clan
弑神领地
44 xp 72.2 % 10 |
|
lose
5 vs 5 |
|
Øg Gøatzz
11 88 % |
2020-03-13
1707d ago
|
|
War clan
弑神领地
93 xp 76.4 % 11 |
|
win
5 vs 5 |
|
Simpson
4 33.8 % |
2020-03-11
1709d ago
|
|
War clan
弑神领地
14 xp 40 % 6 |
|
lose
5 vs 5 |
|
凤舞玖天
12 80 % |
2020-03-08
1712d ago
|
|
War clan
弑神领地
4 xp 39 % 5 |
|
lose
5 vs 5 |
|
我很6
12 93.4 % |
2020-01-03
1777d ago
|
|
War clan
弑神领地
0 xp 0 % 0 |
|
lose
5 vs 5 |
|
صقور النورس
10 76.2 % |
2019-12-28
1782d ago
|
|
War clan
弑神领地
2 xp 20 % 3 |
|
lose
5 vs 5 |
|
special force
4 41.2 % |
2019-12-26
1785d ago
|
|
War clan
弑神领地
2 xp 20 % 3 |
|
lose
5 vs 5 |
|
Donating clan
9 65.6 % |
2019-12-22
1788d ago
|
|
War clan
弑神领地
17 xp 63.6 % 8 |
|
lose
5 vs 5 |
|
elite game..
14 90.8 % |
2019-12-20
1790d ago
|
|
War clan
弑神领地
91 xp 74.8 % 11 |
|
win
5 vs 5 |
|
海的永恒
0 0 % |
2019-12-16
1795d ago
|
|
War clan
弑神领地
43 xp 80 % 12 |
|
tie
5 vs 5 |
|
火影
12 80 % |
2019-12-14
1797d ago
|
|
War clan
弑神领地
0 xp 6.6 % 0 |
|
lose
5 vs 5 |
|
十六班
4 30.6 % |
2019-12-08
1803d ago
|
|
War clan
弑神领地
41 xp 65.6 % 9 |
|
lose
5 vs 5 |
|
Best attack
15 100 % |
2019-12-05
1805d ago
|
|
War clan
弑神领地
1 xp 28.8 % 3 |
|
lose
5 vs 5 |
|
君临天下
15 100 % |
2019-12-03
1808d ago
|
|
War clan
弑神领地
65 xp 59 % 8 |
|
win
5 vs 5 |
|
clash of clans
6 40 % |
2019-12-01
1810d 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.