What this panel cannot measure

Each point comes with the reason and with how it is shown on screen.

1. Anyone's real score. Everything shown is what each person claimed when submitting. The program's review is yearly and manual, and may change it. None of this is a “result” nor “official”: every score carries the word “claimed” and the snapshot date; 2025 figures are called “published” because the program published them after review.
2. On-air activity. Only what was submitted is visible. Someone who works a hundred entities and never uploads is invisible, and that hurts precisely those who are not in the habit of re-uploading.
3. History before 2026-08-12. The public list only keeps each person's last upload date. Anything before the first stored snapshot is not measured: what the Growth page draws for those months is a lower bound reconstructed from that timestamp, and its error is known only on the days that do have a snapshot. Days without a snapshot since then are named in red on the front page.
4. Anyone's QSOs. There is no access to individual logs: only entity and zone totals.
5. Real club membership. Each person types the club name by hand. Obvious spellings are merged with a mechanical key and a hand-written alias table (datos/alias_clubes.txt), and each club shows its original spellings; what a person wrote differently in their class entry and in their Challenge appears in both places.
6. Who to credit for a sign-up. There is no way to know why someone registered.
7. Whether someone stopped operating. “Not resubmitted for N days” means only that: no new upload. They may be very active on the air. The stamp does not state its time zone either; measurement says it is almost certainly UTC, which is why it is called a “stamp” and not “UTC time”.
8. What the Challenge mixes. The Challenge is a separate submission, with its own club field and another scale; it is shown in its own column and never added to the class total. The “last month” reference is the most recent snapshot at least 30 days old; until one exists, the oldest, and every page says which one it uses.
9. The lower bound is not an estimate. It reconstructs how many people were there at an instant by counting the timestamps earlier than it. Someone already present who re-uploaded carries a later timestamp and is not counted, so the reconstructed figure is always less than or equal to the real one, never more. There is a second reason for the same thing: an entry withdrawn or rejected is gone from today’s list, and the reconstruction cannot see it.
10. What “re-upload” means here. That the set of timestamps for that person changed between two snapshots. It may be an extended log, a correction or an identical resend: the source does not tell them apart. And the instant of a backfilled snapshot is kept exactly as it came; when it carried no time, the row says so.