Across the closed tests run on TestFi so far, the median time to fill every tester seat was about two hours from the moment the campaign went live. The fastest filled in six minutes. The slowest took a day and a half. That is the number nobody publishes, and it is the one people actually want, because "go find 12 testers" is advice, not a timeline.
What these numbers measure, and what they do not
This is worth being exact about, because it is the difference between a useful number and a misleading one. What we can see is when a tester claims a seat on our side and hands over the Gmail address they will install with. What we cannot see is Play Console. Whether a tester stays opted in for the full 14 days is decided inside Google's system, and there is no API that reports it back to us. So nothing below says these tests passed Google's review. It says they filled their seats, and how fast.
We publish this distinction because we got it wrong once. An earlier version of our data pages reported a drop-out rate that was really measuring who replied to our own check-in emails. Someone could be perfectly compliant in Play Console and still show as dropped. We pulled the number rather than keep explaining it.
Measured across every Google Play closed-test campaign run on TestFi, comparing each campaign's publish time to the moment its 12th tester opted in. Recomputed from the production database daily.
The waiting is not where you think it is
Finding testers is the part everyone worries about, and in practice it is the part that resolves fastest. The step that actually costs days is the one in the middle: every tester has to be added to your closed testing Google Group before they can install anything. Until that happens they are sitting on a claimed seat, ready, unable to move.
We watch this happen on almost every campaign. Seats fill in an afternoon, then nothing moves for two days because the developer has not pasted the addresses into Play Console yet. If you are running your own test with people you found yourself, the same trap applies and nobody warns you about it. Add addresses in batches as they arrive rather than waiting for a full list.
A live example from the day this was written. Reva runs My Petaverse, a diary app, and needed six testers. Her campaign went live at 11:08 and the sixth seat was claimed at 11:14, so six minutes end to end. At the time of writing, several hours later, not one of those six has installed anything, because the Gmail addresses are still waiting to be added to her testing group. The recruiting was never the hard part.
Country selection is the lever that decides your speed
A closed test is only available in the countries you enable on the track, and a tester in a country you did not enable cannot install even after you add them to the group. This is the single most common reason a test that looks staffed goes quiet. Adding countries is also not instant: the change goes through review before it takes effect, so do it before you go looking for testers, not after.
Where testers actually are matters more than where you wish they were. On our side the tester base concentrates in the United States, India, Kenya, Nigeria and the Philippines, in that order. Campaigns that enable several of those fill in minutes. Campaigns restricted to one small market wait, and no amount of money changes that, because the people simply are not there.
That six-minute campaign is the same point from the other direction. Reva had opened her track to Nigeria, India and Kenya, three of those five, before recruiting started. She had worried that adding countries would make her test look less legitimate to Google, which is a fear worth putting down: it does not, and the wider list is why her seats filled while she slept.
Enabling more countries does not make your test look less legitimate. A closed test is not publicly browsable, so nobody outside your tester list ever sees the country list. What Google reviews is the app against its policies.
Doing this without paying anyone
You do not need a service for this, and it would be dishonest to pretend otherwise. Developers trade testers in swap groups on Telegram and elsewhere: you join someone's test, they join yours. It costs nothing and it works often enough to be the default advice.
The failure mode is worth knowing before you rely on it. Swaps run on reciprocity, so you get a burst of installs on day one from people who want their own count to go up, and a much smaller number still opted in on day nine. Google counts 12 testers held for 14 consecutive days, not 12 installs. If you go this route, over-recruit, and check the count mid-window rather than at the end when there is no time left to fix it.
FAQ
How long does it take to find 12 testers for Google Play closed testing?
On TestFi the median is about two hours from publishing the campaign to the last seat being claimed, with the fastest at six minutes and the slowest at a day and a half. Recruiting yourself through swap groups is usually measured in days rather than hours, and the variance is much wider because it depends on how many people reciprocate.
Does filling the seats mean I passed the 14-day requirement?
No. Filling seats means you have testers ready to install. The requirement is 12 testers opted in for 14 consecutive days, which is tracked in Play Console. A tester who installs and then opts out mid-window still breaks the count, and that state lives in Google's system rather than in ours.
Why is my test stuck even though I have enough testers?
Two usual causes. Either the testers are not yet in your closed testing Google Group, so they cannot install, or your track is not available in their country. Both look identical from the outside: people signed up and nothing happened.