部落我我们大家一起发展,捐兵600长老1000副首部落长老5个首领加副首领5个(捐兵捐巨人,法,弓箭手 除了首领,副首领,长老))可以给高级兵的是首领,副首领,长老,部落战
Level | Name | Donations | Received | Trophies |
---|
Clan | Result | Opponent | Date | ||
---|---|---|---|---|---|
War clan
朱哥
9 xp 39.6 % 11 |
lose
10 vs 10 |
R we Attakers ?
29 98 % |
2017-04-23
2802d ago
|
||
War clan
朱哥
237 xp 50 % 30 |
win
20 vs 20 |
REQ'N GTFO #10b
27 52.4 % |
2017-04-13
2812d ago
|
||
War clan
朱哥
51 xp 31.4 % 21 |
lose
25 vs 25 |
白色的记忆
63 87.6 % |
2017-04-07
2819d ago
|
||
War clan
朱哥
15 xp 40 % 27 |
lose
25 vs 25 |
Friends of Clan
74 99.6 % |
2017-04-05
2821d ago
|
||
War clan
朱哥
118 xp 66.4 % 46 |
win
25 vs 25 |
¥Zeus¥
17 26.8 % |
2017-04-03
2823d ago
|
||
War clan
朱哥
28 xp 52.1 % 19 |
lose
15 vs 15 |
coc hackers
31 74.7 % |
2017-04-01
2825d ago
|
||
War clan
朱哥
105 xp 80.5 % 35 |
win
15 vs 15 |
gangster panda
3 10.6 % |
2017-03-30
2827d ago
|
||
War clan
朱哥
9 xp 39.3 % 16 |
lose
15 vs 15 |
WORLD WAR
30 70.1 % |
2017-03-28
2829d ago
|
||
War clan
朱哥
9 xp 30.9 % 16 |
lose
20 vs 20 |
VINO TINTO™
60 100 % |
2017-03-26
2831d ago
|
||
War clan
朱哥
19 xp 42.9 % 26 |
lose
25 vs 25 |
CLAN PEMUSNAH!!
71 97.4 % |
2017-03-24
2833d ago
|
||
War clan
朱哥
77 xp 55 % 33 |
win
20 vs 20 |
Rider Boys 100
14 28.8 % |
2017-03-22
2835d ago
|
||
War clan
朱哥
75 xp 60.1 % 23 |
win
15 vs 15 |
ျမန္မာcoc
13 35.2 % |
2017-03-20
2837d ago
|
||
War clan
朱哥
70 xp 50.4 % 21 |
win
15 vs 15 |
少年四大李可
15 37.3 % |
2017-03-18
2839d ago
|
||
War clan
朱哥
100 xp 68.9 % 30 |
win
15 vs 15 |
asean city
8 18.2 % |
2017-03-16
2841d ago
|
||
War clan
朱哥
44 xp 56.9 % 32 |
lose
20 vs 20 |
HH350
50 84.8 % |
2017-03-14
2843d ago
|
||
War clan
朱哥
24 xp 48.5 % 13 |
lose
10 vs 10 |
THE DESTRUCTOR
24 82.8 % |
2017-03-12
2845d 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.