参加部落战的一定要打 不打的话飞机票 没有兵可以资源。
Location:
Afghanistan
War freq.:
unknown
Members:
0/50
Level:
2
Win/Tie/Loss:
7/0/8
Points:
454
Streak:
2
Trophies:
0
| Level | Name | Donations | Received | Trophies |
|---|
| Clan | Result | Opponent | Date | ||
|---|---|---|---|---|---|
|
War clan
战神一号
52 xp 20 % 6 |
|
win
10 vs 10 |
|
bourtisandsean
5 25.2 % |
2019-10-30
1789d ago
|
|
War clan
战神一号
100 xp 89.8 % 13 |
|
win
5 vs 5 |
|
Os Vingadores
0 0 % |
2019-10-26
1793d ago
|
|
War clan
战神一号
0 xp 0 % 0 |
|
lose
20 vs 20 |
|
程坑秀的部落
49 85.5 % |
2019-09-25
1824d ago
|
|
War clan
战神一号
18 xp 46.4 % 6 |
|
lose
5 vs 5 |
|
Shmoney gang
12 92.2 % |
2019-09-21
1828d ago
|
|
War clan
战神一号
25 xp 56.4 % 7 |
|
lose
5 vs 5 |
|
Kings2
12 89 % |
2019-09-17
1832d ago
|
|
War clan
战神一号
33 xp 50.8 % 13 |
|
lose
10 vs 10 |
|
raq&blaq
25 89.9 % |
2019-09-14
1835d ago
|
|
War clan
战神一号
31 xp 60.6 % 14 |
|
lose
10 vs 10 |
|
LEGENDA MINANG
24 87.4 % |
2019-09-12
1837d ago
|
|
War clan
战神一号
100 xp 94.8 % 14 |
|
win
5 vs 5 |
|
Kel Johnny
3 28.8 % |
2019-09-10
1839d ago
|
|
War clan
战神一号
99 xp 90.4 % 13 |
|
win
5 vs 5 |
|
Junk Team
6 40 % |
2019-09-04
1845d ago
|
|
War clan
战神一号
12 xp 40 % 6 |
|
lose
5 vs 5 |
|
Surreal Warrior
15 100 % |
2019-08-29
1851d ago
|
|
War clan
战神一号
8 xp 50.8 % 5 |
|
lose
5 vs 5 |
|
淮安.洋河大曲.中国
15 100 % |
2019-08-27
1853d ago
|
|
War clan
战神一号
93 xp 100 % 15 |
|
win
5 vs 5 |
|
Super Cool Kids
6 40 % |
2019-08-25
1855d ago
|
|
War clan
战神一号
93 xp 100 % 15 |
|
win
5 vs 5 |
|
خودی ها
11 78.6 % |
2019-08-22
1858d ago
|
|
War clan
战神一号
94 xp 100 % 15 |
|
win
5 vs 5 |
|
IRAN CITY
0 0 % |
2019-08-16
1864d ago
|
|
War clan
战神一号
42 xp 82.4 % 11 |
|
lose
5 vs 5 |
|
الفقير مايعيش
15 100 % |
2019-08-14
1866d 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.