Runners of the week, Sep 26 to Oct 3: the proven 10x calls

Every week PumpPill logs every Solana call it sees, at the market cap it saw it, and keeps reading the price afterwards. This is what the week of Sep 26 to Oct 3 did, with the peaks we can prove and nothing else.

What the week logged

We logged 1810 calls. 352 went on to double from the market cap at the call, 112 reached 5x, and 46 reached 10x by their stored peak. Those are counts of logged calls, not a rate, and the calls that went nowhere are in the same log: open Every call on the Tables page to see them.

The proven list

A peak only makes this list when our own readings back it: at least two readings within 30% of the peak after the call, no single-reading spike, and no series that flips between two pools. 43 of the 46 stored 10x peaks passed that test this week; the other 3 are counted above and not named here.

| Ticker | Logged | Entry market cap | Proven peak | Multiple | Hours to the peak reading |

|---|---|---|---|---|---|

| $Super Intelligence | Sep 29 | $82K | $8.2M | 100.0x | 37.7 |

| $BABYCALI | Sep 27 | $216K | $19.2M | 88.8x | 23.1 |

| $HOOKED | Sep 28 | $114K | $7.9M | 69.0x | 70.3 |

| $Parasite | Sep 29 | $66K | $3.9M | 58.8x | 15.0 |

| $Agency | Oct 1 | $64K | $3.7M | 57.7x | 15.1 |

| $Stupid Inu | Sep 29 | $50K | $2.8M | 55.1x | 23.4 |

| $JACK | Sep 27 | $64K | $3.1M | 48.8x | 6.1 |

| $world wide web | Oct 2 | $168K | $7.3M | 43.5x | 8.2 |

| $cake.xmr | Sep 27 | $59K | $2.4M | 41.3x | 2.3 |

| $cat wif sword | Sep 28 | $70K | $2.1M | 30.1x | 4.7 |

How fast they ran

The proven runners reached their peak reading a median 4.1 hours after the call. 24 of the 43 peaked inside 6 hours and 37 inside 24 hours. A runner you find a day late is usually a runner you watched from the top.

How to read the table

Entry market cap is the market cap at the moment we first logged the token, not a price anyone paid. Proven peak is the highest reading after the call that our own later readings back up. Multiple is the distance between the two. Hours to the peak reading is how long the token took to get there from the call, which is the number that decides whether a reader who saw the call had time to act. A multiple with no hours beside it is a story; with hours, it is a measurement.

Where to see this yourself

Every call on the Tables page is the same log, misses included, with the line above the table giving the week's counts. The read drawer on any row answers two questions, am I early and what is my risk, and lists the reasons with their time stamp. Paste a contract into the Scanner at pumppill.org/scan for the full read, or into the Trade Bot in Telegram, where Scan gives the same two answers before any buy and the take-profit steps are armed on the price you pay.

What this does not tell you

A proven peak is a reading, not an exit. Nobody sells the top, and the multiple in the table is the distance from the call to the highest reading we can back, not a trade result. The counts are counts of logged calls, not a success rate, and a week is a small sample: next week's log will look different. Our read on each token is as of its time stamp.

Do this

Open Every call on the Tables page and read the line above the table before you look at Top calls. When a token from a list like this crosses your feed, paste its contract into the Scanner or the Trade Bot and read the two answers first: am I early, and what is my risk.