Clen. (3 SCON KING 2) penting kompak aja lahh.
Location:
International
War freq.:
always
Members:
0/50
Level:
2
Win/Tie/Loss:
3/0/10
Points:
359
Streak:
0
Trophies:
1000
| Level | Name | Donations | Received | Trophies |
|---|
| Clan | Result | Opponent | Date | ||
|---|---|---|---|---|---|
|
War clan
3 SCON KING 2
24 xp 42.4 % 19 |
|
lose
15 vs 15 |
|
Bd FiGHTER
37 86.7 % |
2017-03-29
2845d ago
|
|
War clan
3 SCON KING 2
12 xp 36.1 % 14 |
|
lose
15 vs 15 |
|
Erson Abbaco
29 66.3 % |
2017-03-24
2850d ago
|
|
War clan
3 SCON KING 2
61 xp 68.2 % 29 |
|
lose
15 vs 15 |
|
ابطال المعيلق
29 69.5 % |
2017-03-22
2852d ago
|
|
War clan
3 SCON KING 2
114 xp 72.2 % 30 |
|
win
15 vs 15 |
|
BD KING COMILLA
7 14 % |
2017-03-20
2854d ago
|
|
War clan
3 SCON KING 2
37 xp 49.1 % 25 |
|
lose
20 vs 20 |
|
P.E.K.A 05
57 95.8 % |
2017-03-18
2856d ago
|
|
War clan
3 SCON KING 2
77 xp 77.6 % 41 |
|
lose
20 vs 20 |
|
мечь возмездия
56 97.7 % |
2017-03-16
2858d ago
|
|
War clan
3 SCON KING 2
94 xp 72.8 % 49 |
|
lose
25 vs 25 |
|
Pamuda TangguL
74 99.6 % |
2017-03-14
2860d ago
|
|
War clan
3 SCON KING 2
144 xp 90 % 62 |
|
win
25 vs 25 |
|
DHARAHARA
6 8 % |
2017-03-12
2862d ago
|
|
War clan
3 SCON KING 2
112 xp 67.7 % 28 |
|
win
15 vs 15 |
|
藏宝海湾☘
16 37.7 % |
2017-03-10
2864d ago
|
|
War clan
3 SCON KING 2
74 xp 71.7 % 61 |
|
lose
30 vs 30 |
|
♥♥BD KING♥♥
85 95.6 % |
2017-03-08
2866d ago
|
|
War clan
3 SCON KING 2
29 xp 46.1 % 32 |
|
lose
25 vs 25 |
|
SIMPLECLANS
69 94.2 % |
2017-03-06
2868d ago
|
|
War clan
3 SCON KING 2
34 xp 52.5 % 28 |
|
lose
20 vs 20 |
|
bd Knights
59 97.6 % |
2017-03-04
2870d ago
|
|
War clan
3 SCON KING 2
56 xp 88 % 21 |
|
lose
10 vs 10 |
|
Khasi 9trep
27 96.3 % |
2017-03-02
2872d 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.