ae quang locCrystal I#QRYC9VYL

Clan level 28 · 700 war wins

Synced 17 days ago · updates weekly

ae quang loc coaching focus · Clashalytics

War typeBoth Regular CWL

Window7d 30d 90d All

Clan health score

32 / 100

Scored 0 to 100, higher is better.

▸What goes into it

The mean of the four dimensions that actually decide whether this clan wins wars: Engagement, Usage, War attack, and War defense. War defense is a conceded rate, so a low one counts as a good one here.

Focus firstWar defenseBehind all 15 tracked clans

▸How this is scored

War attack, War defense and Usage are compared against every other daily-tier clan's identical roster-wide number, not a theoretical 100 -- a perfect, 0%-conceded defense is not something even the best tracked clan achieves. "Focus first" is whichever of the three has the worst percentile among real peers, not the worst raw score.

Engagement isn't part of this comparison -- it's the one dimension where 100% is genuinely reachable (real members already hit it), so it's still read against that flat target rather than a peer percentile.

Percentile against tracked clans, not a score

War attack

73%

War defenseFOCUS

Usage

100%

The four focus dimensions

These are this clan's own real rates, not a ranking against other clans, so they will not match the percentile bars above.

▸Why these differ from the bars above

Each is a rate this clan actually produced, on a 0 to 100 scale. Higher is better on three of them; War defense is the share of defences that got 3-starred, so lower is better there. The bars above place the same clan against every other clan tracked here, which is a different question and a different scale.

Engagement1

On a typical day, 1% of the roster shows real evidence of playing: a battle, a war attack, or a raid weekend, over the last 28 days. Counted from evidence only, so it understates rather than overstates. 20 of 28 members show none at all.

→Raw Stats and the player page show exactly which members have no recent battle, war, or raid evidence.
→A quiet roster spot is worth a direct check-in before it becomes a departure.

▸How this is scored

Days with real evidence that a member played (a battle, a war attack, or a raid weekend), as a share of the days we have been able to watch them. Each member is only measured over their own time in the clan. Evidence only, never a live session log, so it reads low rather than high. Averaged across the roster.

▸Player by player28 needs attention · 0 worth watching · 0 on track

Last

Needs attention (28)

0 of 28 days

No war attack data either.

16 given · 0 received (current)

UsageGathering data

No finished war recorded here yet. Overview's record comes from the in-game war log, which reaches back further.

War attack63

63% 3-star rate on war attacks.

▸How this is scored

Roster-wide War attack 3-star rate, summed across every real attack in the regular wars in the window.

▸Player by player1 needs attention · 4 worth watching · 3 on track

Last

Needs attention (1)

0 of 2 attacks 3-starred

Getting the reps (100% used) but not converting -- a base-reading or army-composition conversation, not attendance.

Worth watching (4)

On track (3)

War defense69%conceded

69% 3-starred conceded on war defenses.

→Layout review for the bases conceding 3-star at the highest rate.

▸How this is scored

Roster-wide War defense 3-star-conceded rate, summed across every real defense in the regular wars in the window. Lower is better, the same way this number reads on Overview, Rankings and the player page.

▸Player by player8 needs attention · 1 worth watching · 1 on track

Last

Needs attention (8)

1 of 1 defense 3-starred

Attack is also soft (0%) -- a broader coaching conversation, not just base layout.

Worth watching (1)

On track (1)

Also tracked

▸What these two are

Progression and Retention are TH and membership signals, shown here at their real current values alongside the four dimensions above.

ProgressionGathering data

TH history spans under 14 days. Scores at day 14.

RetentionGathering data

0 of 3 membership events logged. Scores at 3.