1.招收八本以上打手。2.活跃者或者捐兵多的都可以升长老或副手。3.全天活跃者，或捐兵多者，都可升长老。4.只需八分以上捐兵，八本以下无需捐兵。5.看表现给副手。6.不强制要求打部落战，当然，联赛还是要打的。
Location:
International
War freq.:
always
Members:
0/50
Level:
3
Win/Tie/Loss:
6/0/8
Points:
475
Streak:
0
Trophies:
0
| Level | Name | Donations | Received | Trophies |
|---|
| Clan | Result | Opponent | Date | ||
|---|---|---|---|---|---|
|
War clan
龙形无敌
26 xp 21.7 % 17 |
|
lose
30 vs 30 |
|
怡红院
28 32.6 % |
2019-04-26
1831d ago
|
|
War clan
龙形无敌
47 xp 43.8 % 23 |
|
lose
25 vs 25 |
|
BD REAL TIGER
75 100 % |
2019-04-19
1838d ago
|
|
War clan
龙形无敌
159 xp 82.1 % 56 |
|
win
25 vs 25 |
|
大唐传奇
55 78.9 % |
2019-04-12
1845d ago
|
|
War clan
龙形无敌
169 xp 78.3 % 60 |
|
win
30 vs 30 |
|
揽胜丶不落皇朝
31 41.3 % |
2019-03-29
1859d ago
|
|
War clan
龙形无敌
92 xp 65.6 % 70 |
|
lose
40 vs 40 |
|
皇城
74 67.3 % |
2019-03-22
1866d ago
|
|
War clan
龙形无敌
120 xp 85.3 % 69 |
|
lose
30 vs 30 |
|
无情的地狱
74 87.2 % |
2019-03-15
1873d ago
|
|
War clan
龙形无敌
96 xp 45.4 % 35 |
|
lose
30 vs 30 |
|
geng benhol
87 97 % |
2019-02-24
1892d ago
|
|
War clan
龙形无敌
118 xp 45.8 % 47 |
|
lose
40 vs 40 |
|
只爱丶南方阁
82 70.2 % |
2019-02-22
1894d ago
|
|
War clan
龙形无敌
142 xp 72.3 % 62 |
|
win
30 vs 30 |
|
King of clan
15 22.3 % |
2019-02-17
1899d ago
|
|
War clan
龙形无敌
153 xp 82.9 % 70 |
|
win
30 vs 30 |
|
vi rykker kbh
27 38.5 % |
2019-02-14
1902d ago
|
|
War clan
龙形无敌
132 xp 69.8 % 62 |
|
win
30 vs 30 |
|
Mlang♡Pohar
37 47.5 % |
2019-02-12
1904d ago
|
|
War clan
龙形无敌
107 xp 64.3 % 41 |
|
win
25 vs 25 |
|
违背的青春
36 53 % |
2019-02-10
1906d ago
|
|
War clan
龙形无敌
70 xp 79 % 39 |
|
lose
20 vs 20 |
|
КРУШИТЕЛИ ☆☆☆
45 78.6 % |
2019-01-31
1916d ago
|
|
War clan
龙形无敌
47 xp 85 % 11 |
|
lose
5 vs 5 |
|
BD WARRIORS
14 97.8 % |
2019-01-29
1918d 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.