Location:
International
War freq.:
always
Members:
3/50
Level:
1
Win/Tie/Loss:
3/0/10
Points:
1026
Streak:
0
Trophies:
200
| Level | Name | Donations | Received | Trophies | |
|---|---|---|---|---|---|
|
22 | hola Elder | 0 | 0 | 765 |
|
25 | roma18 Leader | 0 | 0 | 702 |
|
16 | luc Elder | 0 | 0 | 587 |
| Clan | Result | Opponent | Date | ||
|---|---|---|---|---|---|
|
War clan
llumapeal 2009
0 xp 4.8 % 0 |
|
lose
5 vs 5 |
|
история о драго
10 68.4 % |
2019-03-08
1909d ago
|
|
War clan
llumapeal 2009
0 xp 14 % 0 |
|
lose
5 vs 5 |
|
CLASHERS
12 90.4 % |
2019-01-27
1950d ago
|
|
War clan
llumapeal 2009
66 xp 50.6 % 8 |
|
win
5 vs 5 |
|
The Hell-riders
6 40 % |
2019-01-19
1958d ago
|
|
War clan
llumapeal 2009
0 xp 12.6 % 0 |
|
lose
5 vs 5 |
|
БоЙцЫ КВ
13 89.4 % |
2019-01-16
1961d ago
|
|
War clan
llumapeal 2009
64 xp 58 % 6 |
|
win
5 vs 5 |
|
SaykQLar
3 20 % |
2019-01-13
1963d ago
|
|
War clan
llumapeal 2009
0 xp 14.4 % 0 |
|
lose
5 vs 5 |
|
war klan
5 37 % |
2019-01-11
1965d ago
|
|
War clan
llumapeal 2009
4 xp 33.2 % 5 |
|
lose
5 vs 5 |
|
部落冲突游戏解说小号
8 63.8 % |
2019-01-07
1969d ago
|
|
War clan
llumapeal 2009
17 xp 56 % 6 |
|
lose
5 vs 5 |
|
广东人
12 83.8 % |
2019-01-05
1972d ago
|
|
War clan
llumapeal 2009
67 xp 51 % 7 |
|
win
5 vs 5 |
|
Team06
2 13.6 % |
2019-01-03
1974d ago
|
|
War clan
llumapeal 2009
15 xp 49.4 % 6 |
|
lose
5 vs 5 |
|
الإمبراطورية
10 72.6 % |
2018-12-26
1982d ago
|
|
War clan
llumapeal 2009
2 xp 25 % 3 |
|
lose
5 vs 5 |
|
老子天下第一
11 79.8 % |
2018-12-21
1987d ago
|
|
War clan
llumapeal 2009
0 xp 17.4 % 0 |
|
lose
5 vs 5 |
|
ElbetBirGün
14 94.4 % |
2018-12-18
1990d ago
|
|
War clan
llumapeal 2009
4 xp 27 % 3 |
|
lose
5 vs 5 |
|
Т Р О Я
12 88.4 % |
2018-12-12
1995d 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.