Set the counting scope
Define whether the total includes pokies, live tables, virtual games, sportsbook widgets, demo-only entries and duplicate RTP variants. Record date, domain, account state, device and player region.
Live competitors report materially different totals, from roughly five thousand to more than seven thousand. The discrepancy is an intent in itself and requires a reproducible counting method, not a newer headline.
Continue through the verified /play/ routeThis page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Define whether the total includes pokies, live tables, virtual games, sportsbook widgets, demo-only entries and duplicate RTP variants. Record date, domain, account state, device and player region.
Capture category and provider filters, pagination or result totals where exposed. Sample titles to detect repeated entries, unavailable launches and regional placeholders that inflate a visual count.
Compare selected titles with official studio catalogues and the in-game provider attribution. An aggregator label, branded skin or game family should not automatically be counted as a separate studio.
State the observed scope and date, list exclusions and preserve the method. Recount after a major provider, region or lobby change instead of presenting the total as permanent.
Availability of the desired providers, rules and versions matters more than an undifferentiated headline total.
Reviews can use different dates, regions, categories and duplicate rules.
Only if the stated method includes them consistently.
Yes due to region, device or maintenance, so launchability should be sampled.