Refreshed when the site is published. Last counted Tue Nov 10, 13:03 UTC.
Battles
103,511
Jan 3 → Nov 10
Players
68
Clans
11
War weeks
88
past the API’s ten-week window
Daily player records
19,522
Battles by the day they were played
58,270 retained battles in this 120-day window, a mean of
486 a day; the busiest was Oct 29 with
774. The full record holds
103,511 battles across all dates.
The newest day is partial.
26,362 retained battles in this 56-day window, a mean of
471 a day; the busiest was Oct 29 with
774. The full record holds
103,511 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 tracked, and a year after
Player profilesdaily (every 8 h for a player tracked directly), and after a sessionwhile tracked, and a year after
Clanstracked clans every 15 min while members are online, backing off when idlewhile tracked, and a year after
River races (clan wars)every 30 min on war days, 2 h on training days; the race log dailywhile tracked, and a year after
Game eventsonce a game daywhile tracked, and a year after
Decks, cards, matchupsworked out from recorded battlesrecomputed
A player or clan is recorded because an account tracks it (or its clan).
Elixir keeps every battle it records. History stays for at least a year
after the last person stops tracking. 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
JSON API; one battle’s own page is the
only part of it open to anyone.
