Refreshed when the site is published. Last counted Sun Nov 15, 15:17 UTC.
Battles
106,774
Jan 3 → Nov 15
Players
74
Clans
13
War weeks
121
past the API’s ten-week window
Daily player records
21,257
Battles by the day they were played
59,510 retained battles in this 120-day window, a mean of
496 a day; the busiest was Oct 29 with
779. The full record holds
106,774 battles across all dates.
The newest day is partial.
27,396 retained battles in this 56-day window, a mean of
489 a day; the busiest was Oct 29 with
779. The full record holds
106,774 battles across all dates.
The newest day is partial.
Days run in UTC. Removed records are left out. The numbers are as of the date shown.
What is recorded, how often, and how long it is kept.
WhatHow oftenKept
Player battle logsevery 30 min while playing, backing off to at most 2 hwhile followed, and a year after
Player profilesdaily (every 8 h for a player followed directly), and after a sessionwhile followed, and a year after
Clansfollowed clans every 15 min while members are online, backing off when idlewhile followed, and a year after
River races (clan wars)every 30 min on war days, 2 h on training days; the race log dailywhile followed, and a year after
Game eventsonce a game daywhile followed, and a year after
Decks, cards, matchupsworked out from recorded battlesrecomputed
A player or clan is recorded because an account follows it (or its clan).
Elixir keeps every battle it records. History stays for at least a year
after the last person stops following. Raw game data is archived when
admitted. Account data is never public. A gap in the record means unknown,
not that nothing happened.
No key needed for any of these. The recorded history itself needs an
account, over MCP or the website; one
battle’s own page is the
only part of it open to anyone.