How the TBC Guild Lookup works
One guild, read out of its public logs: which raids it is actually clearing, how fast the bosses fall, where it is wiping, and how long its nights run. This page says which nights the numbers came from, and — more usefully — the several ways a guild can look quieter here than it is.
Everything is scoped to the public logs we could read
This is the sentence to read before any other number on the page. The tool authenticates as itself, so it can only see reports a guild has made public on Warcraft Logs. A guild that logs privately, logs some nights and not others, or has a raider who forgets to hit record produces a thinner page than its raid week deserves.
Absence here is our reporting gap, not their raid week. An attendance row reads "x of N", where N is every public log of theirs this page could read. "0 of 44" means "absent from all forty-four of them", never "does not raid". An officer acting on the second reading would be acting on our blind spot.
The window is stated twice on purpose: in the line under the guild's name, and again under the panel — "Measured over: All 53 raids · 44 public logs". A raid is one visit to one instance, so a log that ran two instances is two raids, and a log is the unit rather than a night because one log can hold more than one night. Every log the guild has made public is read. Where Warcraft Logs says it has more than we could read — a private log, or one whose report would not load — the head says so ("… · 2 more logged we could not read"). A second recording of a raid already counted is not one of those: it was read and folded in, and the line under the panel says how many.
The attendance list — and only that list — can be narrowed, by raid phase and by date. The pills offer the phases this guild actually has a log in and take more than one at a time; the two date boxes are inclusive at both ends, in your own calendar. Its heading then says what it is counted over ("Attendance — 7 BT/Hyjal logs, from Aug 1"), and the address carries it, so a link you copy opens the same numbers. Everything else on the page — the six counts, the progression bars and Recent raids — stays over every log read, because what a guild has cleared is not a question about a date range.
What each number is
| Number | What it means |
|---|---|
| Bosses killed | Every kill in those logs — a kill because Warcraft Logs marked the fight one, not because we judged it. |
| Wipes | Every other pull. Not a score against the guild: it is where the wall is. |
| Perfect clears | Visits that finished a whole instance without a single wipe. Counted per raid, not per log — a log that cleaned out two instances earns two. |
| Raids done | Shown as done / attempted: instance visits that killed every boss, out of every visit read. A log that ran two instances is two raids, and an instance whose boss roster we cannot count is never "done". |
| Avg raid | How long a log runs, start to end, averaged — trash, travel and breaks included. The tooltip also gives the part that was actually boss fights, which is roughly half. |
| Avg wipes / raid | Every wipe read divided by every raid attempted. A guild on farm sits near zero; a guild learning a boss does not. |
| Start | On Recent raids and in each raid's list of runs: when the first boss was pulled, kill or wipe. Not when they entered — the logs record boss fights only, so the trash cleared to reach that boss happened before this time. A night that ran two instances is two rows, each with its own clock. |
| End | The end of the last boss pull. Whatever the raid did after — trash, loot, dailies — the log cannot see. |
| In instance | Start to End. It carries the trash between bosses and the recovery after a wipe, which is why it is longer than Fighting. |
| Fighting | Time inside boss fights only, kills and wipes alike, added up. The gap between this and In instance is everything that was not a boss. |
| Fastest kill | The shortest kill of that boss across the runs we read, to the second. |
Times are exact rather than rounded to the minute, because rounding hid the thing the page is for: kills at 2m 58s, 3m 12s and 3m 47s all printed "3m", so a guild that had cut a fight by a fifth read as a guild that had not moved. Warcraft Logs reports fight boundaries in milliseconds; those seconds are theirs.
Two logs of one raid are one log
When two people in the same raid both log, Warcraft Logs has two reports of one raid. Counted naively that doubles the guild's kills, its wipes and its logs. The tool folds them together when the rosters overlap enough to be the same raid, and says so on the page — "3 extra logs were a second recording of a raid already counted". Two teams raiding the same instance at the same time have nearly disjoint rosters, so they stay two raids.
What this page is not
It is not a gear audit. What a guild is clearing and what its raiders are wearing are different questions, and the other two tools answer the second one — every night here links into the Raid Gear Checker, and any raider can be looked up in the Raider Lookup. It is also not a ranking: there is no score, no grade and no comparison against other guilds.
Ads, and what they pay for
There are two ad slots: one in the side rail on wide screens, one below the results. They are never put between a raider and their data, they hold their space so nothing jumps under your cursor, and the side one disappears on narrow screens rather than squashing the table. All of that describes what happens once an ad unit is approved. None is, so today neither slot is filled and neither one takes up any space at all.
They pay the bills. Simulating a full raid is a couple of minutes of computing time per report, and that costs real money. There is no paywall and no account, and nothing about the audit changes depending on whether an ad loads — block them and the tool works exactly the same.
Credit where it is due
The audits, the checks, and every choice about how a number is read, labelled and shown are this site's own. The raw material underneath has earned its credit: every dps number here is produced by wowsims' simulator — their simulator, their rotations, their talent builds — and the item database comes from them too. It is open source under the MIT licence, which is what makes a tool like this possible at all.
The best-in-slot lists and item scores are wowtbc.gg's. Where their score and their own pick disagree, this tool goes with the pick — they chose that item knowing what it does.
Game data and item art come from Blizzard Entertainment's official API. World of Warcraft and Burning Crusade Classic are trademarks of Blizzard Entertainment. This site is not affiliated with or endorsed by Blizzard, wowsims or wowtbc.gg.
Privacy
No account and no user database; the server keeps one line per request for 14 days, plus a cache of the public Warcraft Logs responses it fetches. The privacy page spells out exactly what is recorded and what is not.