When can you apply? Count from your twelfth tester.
Enter when each group of testers opted in and see the earliest date Google's 12-tester, 14-day rule can be met. Free, no sign-up.
Build a cohort-based testing calendar
Use anonymous cohorts, not tester emails. Enter every time in UTC. A cohort contains people who most recently joined at the same time and have stayed opted in continuously.
Participants with valid continuous records: 0
Earliest mathematical checkpoint
Add a valid release time and at least 12 continuously opted-in participants.
The calculation takes the 12th-earliest still-active participant start, waits until the release is available, then adds 14 full days. It does not verify opt-in records, account eligibility or Google review time. If someone rejoins, enter their new continuous start time.
Your upload date is not your start date
Google counts testers who stayed opted in for the last 14 days in a row. The day you uploaded a build does not tell you when each tester joined. Group testers by the day they opted in, and keep anyone who joined later in a separate group.
Times are in UTC so your saved record uses one clock. Play Console is always the final word on whether your account meets the requirement.
What the calendar does
It drops any group that is no longer opted in, puts the rest in order of start date, and finds tester number twelve. It takes that date, or the release date if that is later, and adds 14 full days. If an active group has no start date, it shows no result instead of guessing.
You can add extra days for your own planning. That allowance is yours; it does not predict how long Google takes to review your application.
Worked example with invented dates
Ten testers opt in on 1 November at 09:00 UTC and two more on 3 November at 09:00 UTC. If all twelve stay in, the earliest date is 17 November at 09:00 UTC, because tester number twelve joined on 3 November.
If one of the two late testers leaves, take them out of the group. If they come back, give them a new start date. The others keep their own dates.
Keep your inputs private
Use group names and counts, not tester names or email addresses. Make a new group whenever join times differ or someone leaves.
You can download the calendar with your inputs and result. Drafts are saved only in this browser; if saving is blocked, the tool still works and shows a warning.
The date is only part of the picture
Google also asks how testers used your app and what you changed. Keep a record of tasks, feedback and fixes alongside this date.
Check the current requirement in Play Console before applying. If you want us to run the test, our plans use 14 testers for 16 days. Google requires 12 testers for 14 days (for personal Play developer accounts created after 13 November 2023; organization accounts are exempt); the extra 2 testers and 2 days are our buffer.
Source: Google Play testing and production-access requirements. Verify the current requirements before applying.