How we measure delivery rates
Every percentage on this site answers one question: of the recent orders placed on this exact option, how many actually received a code?
Every percentage on this site answers one question: of the recent orders placed on this exact option, how many actually received a code? It is a record of what happened, not a forecast and not a promise. The method is written out below so you can judge how much weight it deserves.
What counts as delivered
An order counts as delivered when a message reaches the number and a verification code is extracted from it, before the rental window closes. Anything else — the window expiring in silence, the number being rejected at signup, the order being cancelled — counts as not delivered.
We deliberately do not exclude awkward cases. If a platform refused the number, that failure stays in the denominator, because from your side it is a failure regardless of whose fault it was.
Which time windows
Rates are computed over rolling windows and blended, so that recent behaviour dominates without a single quiet hour distorting the picture:
| WINDOW | WEIGHT | WHY |
|---|---|---|
| Last 3 hours | 30% | Catches a route failing right now |
| Last 24 hours | 30% | Smooths out quiet hours |
| Last 3 days | 20% | Separates a bad day from a bad route |
| Last 30 days | 20% | The long-run baseline |
A one-hour window exists in the raw data but is left out on purpose: with only a handful of orders in it, it swings wildly and would make the ranking jump around for no real reason.
Why the blend, in one example
A real case from the catalogue. One route read 4.8% over three hours but 29.5% over twenty-four and 22% over thirty days. A second route looked better in the short window — 13.6% over three hours — but sat at 1.3% over thirty days.
Ranking on the three-hour figure alone would have buried the first route and promoted the second. Both would have been wrong. The blend puts them in the order the fuller picture supports.
When it says “measuring”
Some options carry no percentage. That means we do not have enough recent orders on that exact combination to state a number we would stand behind — so we say nothing rather than publish a figure that looks precise and is not.
This is most common on newly added routes and on physically-backed lines, which sell in smaller volumes. Where a rate is missing, the other signals on the row — the share of physical SIMs in the pool, and stock depth — are what you have to go on.
What this method cannot tell you
It is backward-looking. A route that delivered 90% this morning can fail this afternoon, and the number on screen will lag that change by minutes.
It is also aggregate. Your individual order either arrives or it does not; a 90% rate does not mean you get 90% of a code. That is exactly why the refund is automatic — the percentage informs your choice, the refund covers the outcome.
Why publish unflattering numbers
Because a rate you cannot trust is worth nothing. Options sitting at 0% stay visible on the page with their real figure attached, rather than being quietly hidden. If the honest number for a cheap route is 4%, that is what it says.