一起加油干！本部落支持死鱼🐠，别把自己变死鱼🐠。也不许随便踢人。
Location:
International
War freq.:
always
Members:
0/50
Level:
3
Win/Tie/Loss:
7/0/8
Points:
86
Streak:
0
Trophies:
0
| Level | Name | Donations | Received | Trophies |
|---|
| Clan | Result | Opponent | Date | ||
|---|---|---|---|---|---|
|
War clan
踏雪寻梅
0 xp 0 % 0 |
|
lose
5 vs 5 |
|
战神荣耀
1 7.8 % |
2019-08-09
1869d ago
|
|
War clan
踏雪寻梅
52 xp 14 % 3 |
|
win
10 vs 10 |
|
白鸭子军团
0 0 % |
2019-08-06
1871d ago
|
|
War clan
踏雪寻梅
28 xp 44.2 % 23 |
|
lose
20 vs 20 |
|
占戈——云鬼
58 97.8 % |
2019-07-18
1890d ago
|
|
War clan
踏雪寻梅
41 xp 47 % 25 |
|
lose
20 vs 20 |
|
幼儿园大班
56 96.7 % |
2019-07-16
1893d ago
|
|
War clan
踏雪寻梅
135 xp 67.3 % 60 |
|
win
30 vs 30 |
|
hip hop tamil
9 15.6 % |
2019-07-14
1895d ago
|
|
War clan
踏雪寻梅
155 xp 70.5 % 58 |
|
win
30 vs 30 |
|
COC Players
20 26 % |
2019-07-12
1897d ago
|
|
War clan
踏雪寻梅
67 xp 48.1 % 51 |
|
lose
40 vs 40 |
|
攀登吧，青年
104 90.8 % |
2019-07-10
1899d ago
|
|
War clan
踏雪寻梅
178 xp 63.7 % 75 |
|
win
40 vs 40 |
|
五人开黑
66 65.3 % |
2019-06-30
1909d ago
|
|
War clan
踏雪寻梅
93 xp 57.2 % 56 |
|
lose
40 vs 40 |
|
Slaves-of-Force
94 81.6 % |
2019-06-27
1911d ago
|
|
War clan
踏雪寻梅
69 xp 51.7 % 37 |
|
lose
25 vs 25 |
|
⚡⚡YILDIRIM⚡⚡
59 83.7 % |
2019-06-25
1913d ago
|
|
War clan
踏雪寻梅
85 xp 57.8 % 28 |
|
lose
20 vs 20 |
|
WAR KING
47 84.2 % |
2019-06-23
1915d ago
|
|
War clan
踏雪寻梅
166 xp 80.3 % 57 |
|
win
25 vs 25 |
|
★惩戒之锋♥
25 39.8 % |
2019-06-21
1918d ago
|
|
War clan
踏雪寻梅
141 xp 66.6 % 36 |
|
win
20 vs 20 |
|
@AUS
35 65.3 % |
2019-06-19
1920d ago
|
|
War clan
踏雪寻梅
70 xp 42.6 % 32 |
|
lose
30 vs 30 |
|
13 РАЙОН
63 77.7 % |
2019-06-17
1922d ago
|
|
War clan
踏雪寻梅
101 xp 90 % 13 |
|
win
5 vs 5 |
|
nikos clan
10 69 % |
2019-06-15
1924d 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.