Kalıcı Ve Aktifler katılabilir
Location:
War freq.:
always
Members:
0/50
Level:
2
Win/Tie/Loss:
6/0/8
Points:
343
Streak:
0
Trophies:
400
| Level | Name | Donations | Received | Trophies |
|---|
| Clan | Result | Opponent | Date | ||
|---|---|---|---|---|---|
|
War clan
FETULLAYEV_LTK
0 xp 0 % 0 |
|
lose
10 vs 10 |
|
COCS SLAYER
14 55.2 % |
2020-02-16
1555d ago
|
|
War clan
FETULLAYEV_LTK
68 xp 40 % 12 |
|
win
10 vs 10 |
|
DC COMIX
6 20 % |
2020-02-14
1557d ago
|
|
War clan
FETULLAYEV_LTK
4 xp 17.2 % 4 |
|
lose
10 vs 10 |
|
TPAS #26
18 62 % |
2020-02-10
1562d ago
|
|
War clan
FETULLAYEV_LTK
76 xp 64.5 % 17 |
|
win
10 vs 10 |
|
Titan Family
9 37.5 % |
2020-02-07
1564d ago
|
|
War clan
FETULLAYEV_LTK
0 xp 16.8 % 0 |
|
lose
5 vs 5 |
|
音竹屿
9 68.6 % |
2020-02-05
1566d ago
|
|
War clan
FETULLAYEV_LTK
23 xp 60 % 17 |
|
lose
10 vs 10 |
|
КАК ВАШУ МАМКМ)
26 94.4 % |
2020-02-03
1568d ago
|
|
War clan
FETULLAYEV_LTK
70 xp 49 % 13 |
|
win
10 vs 10 |
|
indian warriors
4 18.1 % |
2020-01-31
1571d ago
|
|
War clan
FETULLAYEV_LTK
106 xp 97.8 % 29 |
|
win
10 vs 10 |
|
恶露（分部）
24 83 % |
2020-01-29
1573d ago
|
|
War clan
FETULLAYEV_LTK
63 xp 49.8 % 6 |
|
win
5 vs 5 |
|
速速请进
0 0 % |
2020-01-27
1575d ago
|
|
War clan
FETULLAYEV_LTK
12 xp 45 % 6 |
|
lose
5 vs 5 |
|
摄氏度℃
14 98.8 % |
2020-01-22
1580d ago
|
|
War clan
FETULLAYEV_LTK
47 xp 72 % 20 |
|
lose
10 vs 10 |
|
PH_GT CLAN
30 100 % |
2020-01-20
1582d ago
|
|
War clan
FETULLAYEV_LTK
48 xp 63.9 % 19 |
|
lose
10 vs 10 |
|
霸道\永久
29 97.3 % |
2020-01-17
1586d ago
|
|
War clan
FETULLAYEV_LTK
43 xp 94.6 % 14 |
|
lose
5 vs 5 |
|
曹文康是坑比
15 100 % |
2020-01-15
1588d ago
|
|
War clan
FETULLAYEV_LTK
62 xp 48.8 % 6 |
|
win
5 vs 5 |
|
勇者军队
0 0 % |
2020-01-11
1591d 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.