Wipe 101

Thunderstrike Alliance guilds

133 Alliance guilds raid on Thunderstrike, 1,168 of them in the last three weeks. Each was found because it killed a boss in a public log, so this is the realm's actual raiding population rather than a list of guilds that remembered to post. Raid nights are shown in your own timezone.

Raid days UTC
Clear

133 guilds match.

Browse

How this directory is built

Every one of the 133 guilds listed here was found in Warcraft Logs because it killed a boss on the TBC Anniversary realms, and 1,168 of them have raided in the last three weeks. No guild can add itself, so nobody can invent a guild or inflate its progression, and no recruitment post outlives the guild that wrote it. When a guild stops logging kills, it stops showing as active on its own.

Two things here are not measured, and both say so wherever they appear. A guild whose officer has claimed its listing through Battle.net can write its own description. And a guild seen recruiting was advertising for members in trade chat — that note was read out of the advert by a tool, not written by anyone in the guild and not verified by anyone at all, so treat it as a lead rather than a fact. It disappears on its own if the advert stops being heard.

Casual, semi-hardcore or hardcore

Every guild is given a pace from what its logs show — how far into the current tier it has got, and how its kill times compare to every other guild killing the same bosses. Nobody picks their own label, so "hardcore" here means a full clear at speed rather than an ambition. Where a guild has claimed its listing, its own description is shown next to the measured one; when the two disagree, that is worth knowing before you apply.

Dad guilds are self-identified, not inferred. Adults with jobs and bedtimes, a relaxed attendance policy, and usually a late start — but the only honest way to know is for the guild to say so. A measured late start filter sits next to it for guilds that begin at least forty-five minutes after the typical guild in their region.

What you can filter on

Raid days in your own timezone. A raid that starts at 19:00 US Eastern is already Wednesday in UTC, so a directory that filters on the log's own clock gives you the wrong day. Pick the nights you are free and the times shown shift to where you live.

Progression that means something. Bosses down per raid, counted from distinct kills — a guild that killed Hydross eleven times has one boss down, not eleven. Filter to Karazhan, Gruul / Magtheridon, SSC / Tempest Keep, Black Temple / Hyjal and a minimum boss count to find people at your pace.

Realm, faction and raid size. Alliance or Horde, 10 or 25, and every realm with guilds that log — the realm list is built from the data, so it never offers you a filter that returns nothing.

Read the logs before you apply

Every guild page lists that guild's recent kills, and each one opens in the log auditor. Before you transfer a character or spend a week trialling, you can see how long their pulls take, how many people die, and whether the raid turns up enchanted and flasked. That is a better read on a guild than any recruitment post.

Is your guild missing?

Warcraft Logs only ranks the thousand fastest kills of each boss, so a guild that clears content steadily rather than quickly can be absent from the rankings entirely. Those guilds are added from their own uploaded reports instead — if yours is missing, it can be pulled in directly from the logs your raid already uploads.