为荣耀而战,捐兵2000长老,捐兵5000给副手,五本以下可以不捐兵。禁止捐炸弹,哥布林,除非特殊情况可以,发现踢。
Level | Name | Donations | Received | Trophies | |
---|---|---|---|---|---|
26 | Charlie rohit Leader | 0 | 0 | 705 |
Clan | Result | Opponent | Date | ||
---|---|---|---|---|---|
War clan
荣耀部落
0 xp 0 % 0 |
tie
5 vs 5 |
™•Dragon•™
0 0 % |
2019-04-06
1884d ago
|
||
War clan
荣耀部落
6 xp 24.1 % 6 |
lose
10 vs 10 |
NEPALI HUNTERS
27 94 % |
2019-02-18
1930d ago
|
||
War clan
荣耀部落
108 xp 80.9 % 24 |
win
10 vs 10 |
The S.H.I.E.L.D
9 30 % |
2019-02-15
1934d ago
|
||
War clan
荣耀部落
12 xp 36.4 % 11 |
lose
10 vs 10 |
Sl Drak Night
17 61.3 % |
2019-02-13
1936d ago
|
||
War clan
荣耀部落
70 xp 52.8 % 7 |
win
5 vs 5 |
Assam clan
6 40 % |
2019-01-30
1949d ago
|
||
War clan
荣耀部落
23 xp 60.8 % 8 |
lose
5 vs 5 |
黑暗城堡
13 94 % |
2019-01-28
1951d ago
|
||
War clan
荣耀部落
28 xp 45.7 % 13 |
lose
10 vs 10 |
MEISYA KLAN
18 67.1 % |
2019-01-26
1953d ago
|
||
War clan
荣耀部落
19 xp 40 % 12 |
lose
10 vs 10 |
HEROSMITH
25 93.9 % |
2019-01-24
1955d ago
|
||
War clan
荣耀部落
66 xp 73.9 % 32 |
lose
15 vs 15 |
太平天国
33 76.6 % |
2019-01-22
1957d ago
|
||
War clan
荣耀部落
121 xp 80.3 % 35 |
win
15 vs 15 |
夜狼族
17 41.9 % |
2019-01-20
1959d ago
|
||
War clan
荣耀部落
19 xp 61 % 8 |
lose
5 vs 5 |
FTWinc
10 78 % |
2019-01-18
1962d ago
|
||
War clan
荣耀部落
119 xp 84 % 34 |
win
15 vs 15 |
sedeh
25 58.7 % |
2019-01-07
1972d ago
|
||
War clan
荣耀部落
0 xp 0 % 0 |
lose
5 vs 5 |
Навеки друзья
15 100 % |
2019-01-05
1974d ago
|
||
War clan
荣耀部落
117 xp 94 % 28 |
win
10 vs 10 |
سلطان غم ها5
23 82.5 % |
2019-01-03
1976d ago
|
||
War clan
荣耀部落
7 xp 44.4 % 5 |
lose
5 vs 5 |
Fallback15
13 95.6 % |
2019-01-01
1978d ago
|
||
War clan
荣耀部落
72 xp 67.4 % 8 |
win
5 vs 5 |
new gudmarani
0 0 % |
2018-12-20
1990d 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.