TestFi Data · Updated 2026-10-01
We looked at 112 Google Play closed tests run on TestFi since May 2026. Finding 12 testers is the fast part. The 14-day clock only starts once 12 of them are actually in, and that took a median of 2.6 days.
Of the 87 tests that reached 12 confirmed installs, the fastest got there in 2.1 hours. The median took 2.6 days, and one test in ten took 12 days or more. That wait sits in front of Google's 14 days, not inside them.
Tests by time from launch to the 12th confirmed install (n = 87).
Each seat passes through two handoffs. First the developer adds the tester's Gmail to the Play Console testers list: a median of 8 hours after the tester claimed the seat. Then the tester accepts the invite, installs, and sends proof: a median of 19.4 more hours. End to end, a single seat took a median of 33.1 hours from claim to confirmed install (1,537 seats since August 2026).
A test needs 12 of those, and the clock waits for the 12th. So the start date is set by the slowest tester among the first 12 and by how quickly the developer works through the list. Adding every email the same day is the one part of this a developer fully controls.
Somewhat. The median time to 12 confirmed installs was 3.0 days for tests launched in August 2026 (42 tests) and 2.1 days in September 2026 (32 tests). Earlier months had too few tests to compare.
About 17 days from launching the closed test to being allowed to apply for production: roughly three days to get 12 testers installed, then 14 continuous days with at least 12 opted in. Keep a spare tester or two above 12, because dropping to 11 restarts the 14 days. To see where your own test stands, use the free closed testing tracker.
If you do not have 12 testers yet
These numbers come from tests we ran. We put 16 testers on your track so 12 are still opted in on day 14, or we run it again at no cost.
Aggregates from TestFi's production database, snapshot taken 2026-10-01. Scope: 112 paid Google Play closed tests launched between May 2026 and the snapshot, with 368 distinct testers from 50 countries. A seat is claimed when a tester takes it on TestFi and gives the Gmail they will install with. An install is confirmed when their install proof has been checked. Tests that had not reached 12 confirmed installs by the snapshot are left out of the install figures.
What this does not measure: opt-in state inside Play Console (Google offers no API for it), whether testers stayed for all 14 days, or whether Google approved production access. We do not publish figures on any of those. You are welcome to cite this page with a link to testfi.app. Questions: contact@testfi.app.