Volume bot session length sets how long your orders are spread out, from a 15-minute burst to a 10-hour run. It does not change target volume or the fee. It changes pace: 1,000 wallets produce about 1,600 orders, which is roughly 27 orders a minute over one hour but only about 4.4 a minute over six. Pick the length that covers the window you care about.
What the clock actually controls
- Length is free to change: a 250 SOL session costs 2.5 SOL whether it runs 15 minutes or 10 hours.
- Average pace = (wallets x 1.6) / minutes. Doubling the length halves the pace.
- To keep density on a longer run, add wallets. The built-in presets stay between roughly 11 and 17 orders a minute.
- Spacing is uneven, so every per-minute figure on this page is an average.
How many orders per minute does each length produce?
Start from the order count. A session executes roughly 1.6 orders per wallet, so 1,000 wallets on a 0.10-0.40 SOL band produce about 1,600 orders and 250 SOL of target volume. Divide by the minutes in the session and you have the average pace. The table runs that one configuration through every quick pick.
| Length | Minutes | Average orders per minute | Average SOL per hour |
|---|---|---|---|
| 15 minutes | 15 | about 107 | 1,000 (250 SOL in 15 min) |
| 1 hour | 60 | about 27 | 250 |
| 3 hours | 180 | about 8.9 | about 83 |
| 6 hours | 360 | about 4.4 | about 42 |
| 10 hours | 600 | about 2.7 | 25 |
Nothing in the right-hand columns changes the bill. The fee stays at 1% of the 250 SOL target in every row. What changes is what someone sees when they open the token at a random moment: at 27 orders a minute there is almost always a fresh trade; at 2.7 a minute there are quiet gaps.
When does a 15-minute burst make sense?
A burst packs the whole session into a quarter hour. With 1,000 wallets that is more than 100 orders a minute on average, which suits a single moment you already know about: a listing post, a live stream, a partner post going out at a set time.
The cost of a burst is what comes after. The session ends and the page falls back to whatever organic activity exists. DexScreener lists the kinds of inputs behind its trending score, such as volume, transactions and unique makers, without publishing thresholds or weights. Since nobody outside can say how a burst is weighed against steadier activity, treat it as a tool for one moment, not a plan for the day.
What does a one-hour session cover?
One hour lines up with the first stretch after a launch or an announcement, when the people who saw the post tend to open the page. The First hour preset is built for it: 500 wallets, 0.10-0.30 SOL, 60 minutes. That gives about 800 orders, close to 13 a minute, on a 100 SOL target, which is the 100 SOL minimum.
If you want more pace inside the same hour, add wallets rather than widening the band. 1,000 wallets on the same 0.10-0.30 SOL band gives about 1,600 orders, close to 27 a minute, for a 200 SOL target and a 2 SOL fee. The estimated holder count roughly doubles too, to about 620.
What do 3 to 6 hours buy you?
Longer sessions trade intensity for coverage. Three hours spans a full evening in one region; six can stretch from one region's evening into another's morning. The presets show how to keep pace while the clock grows:
- First hour, 500 wallets over 60 minutes: about 800 orders, close to 13 a minute.
- Big prints, 1,250 wallets over 2 hours: about 2,000 orders, close to 17 a minute.
- Slow build, 1,200 wallets over 3 hours: about 1,920 orders, close to 11 a minute.
- Quiet tape, 2,500 wallets over 5 hours: about 4,000 orders, close to 13 a minute.
The pattern is worth copying. Quiet tape runs five times longer than First hour at the same average pace because it uses five times the wallets. Stretching length without adding wallets is how a session ends up thin.
Is a 10-hour session ever too long?
Ten hours suits a team that wants the token page to show activity through most of a waking day. The trap is a small wallet count. 1,000 wallets over 600 minutes averages about 2.7 orders a minute, and with uneven spacing some minutes will be empty.
Holding roughly 10 orders a minute for 10 hours takes about 6,000 orders, which is 3,750 wallets. On a 0.10-0.30 SOL band that is a 750 SOL target and a 7.5 SOL fee. A long run also leaves more time for the bonding curve to complete; if it does, execution follows the token into its pool inside the same session, which raises the question of DexScreener trending after graduation.
How do you match duration to the window you care about?
Work backward from the moment, not forward from a preset. The guide to timing a start covers choosing the moment itself. Once you have it, the numbers follow:
- Write the window down in minutes. A three-hour evening push is 180.
- Choose an average pace. 12 orders a minute sits in the middle of the presets.
- Multiply: 12 x 180 = 2,160 orders.
- Divide by 1.6 to get wallets: 2,160 / 1.6 = 1,350 wallets.
- Pick a band and check the cost: 1,350 x 0.20 SOL = 270 SOL target, so a 2.7 SOL fee.
The same arithmetic works whatever the buy share, though a split reads differently at different speeds, as the buy and sell ratio guide shows. PumpCrest asks for nothing but the fee transfer, so the planning above is the whole job before funding.
Questions and answers
Does a longer session cost more?
No. The fee is a flat 1% of target volume and nothing else, so length is free to change before funding. A 300 SOL session costs 3 SOL at one hour and the same at six hours. What a longer run may need is more wallets to keep the pace up, and wallets raise target volume, which is where cost actually comes from.
Can I extend or stop a session once it is running?
Changes to a running session go through support by email at support@pumpcrest.com. Orders that already settled stay on-chain whatever you decide. Because the fee is not refundable once a session starts, it is simpler to settle the length before funding and to send the config link to a teammate so someone else checks the window first.
Does session length change the holder estimate?
No. The estimated unique-holder count in the console is about 62% of wallets, so it moves with wallet count, not minutes. A 15-minute session and a 10-hour session with 1,000 wallets both show about 620. Length only changes how gradually those holders appear on the token page across the window.
Is a 15-minute session enough for a first test?
It is enough to see the full flow: the mint check, funding, the confirmed transaction with its Solscan link, the queued start and the saved project moving to finished. For judging how a tape reads on the page, a longer window shows more, because a quarter hour passes quickly if nobody on the team is watching at that moment.
Why are orders not evenly spaced?
PumpCrest varies spacing and draws every size at random inside the band, and orders travel through Jito bundles on a private relay with randomized tips. A perfectly regular rhythm would tend to look mechanical to anyone reading the trade list. The price of that variety is that per-minute figures are averages: a 27-a-minute session has busier and quieter minutes.
Size the session to your window
Enter wallets, band and length in the PumpCrest console, divide the orders by the minutes, and read the exact fee before you send anything.
We build the PumpCrest console and write these guides from the operator side: what a session spends, what settles on-chain and what a visitor sees on the board. Corrections are welcome at support@pumpcrest.com.