Start a volume bot when the people you want to reach are most likely to open the token page: right after mint for a launch push, shortly before an announcement goes out, and inside your audience's waking hours. Because a paid session is queued and support confirms the start window, fund it early rather than at the last minute. Graduated tokens follow the same logic on the pair page.
Timing in brief
- Plan backward from one moment: the mint, a post, a stream or a listing.
- Fund ahead. After payment the session is queued and support confirms the start window.
- Cover waking hours. A 10-hour session can span two regions; a one-hour session cannot.
- If the token already graduated, the session trades in its pool, and the DexScreener pair page joins the board as a place people look.
Should the session start right at mint?
The first stretch after mint is when a new token is fresh on the board and early on its bonding curve. A session that starts near mint fills that early trade list instead of leaving it bare, and the First hour preset, 500 wallets for 60 minutes, is shaped for that window.
The catch is order of operations. You cannot paste a mint that does not exist yet, and funding comes after the mint check, so a launch session is always paid after the token goes live. The start then follows the queue and support's confirmation. Shrink that gap by having everything else ready, and see what bonding curve progress means for a launch team for how the curve stage shapes the rest.
How do you time a session around an announcement?
An announcement is easier to plan than a launch because the token already exists, so you can fund well before the moment. The choice is whether the session should already be running when the post lands or should begin right after it. Starting slightly before means the first visitors find trades already printing; starting after means the session meets the later part of the attention rather than its first minutes.
Worked example: a partner post goes out at 18:00 UTC. A one-hour session that begins around 17:45 UTC covers the quarter hour before and 45 minutes after. Fund as soon as the settings are final, tell support the window you are aiming for, and watch saved projects for the status.
Whose waking hours should the session cover?
Orders print whether or not your audience is awake. Convert the waking day of the people you want to reach into UTC before you pick a start. The table treats 08:00 to midnight local time as a rough waking window.
| Audience | UTC offset | Local 08:00-24:00 in UTC |
|---|---|---|
| US East (daylight time) | UTC-4 | 12:00-04:00 |
| US West (daylight time) | UTC-7 | 15:00-07:00 |
| UK (summer time) | UTC+1 | 07:00-23:00 |
| Central Europe (summer time) | UTC+2 | 06:00-22:00 |
| Brazil (Sao Paulo) | UTC-3 | 11:00-03:00 |
| Korea and Japan | UTC+9 | 23:00-15:00 |
Overlaps are where longer sessions earn their length. US East and Central Europe share roughly 12:00 to 22:00 UTC, so a six-hour session starting near 14:00 UTC covers both. Korea and Japan overlap Central Europe only from about 06:00 to 15:00 UTC. A 15-minute burst covers one moment for one region, and choosing how long a session should run turns that window into wallet counts.
What should be ready before you pay?
Most timing problems are really preparation problems. The pre-launch checklist goes further, but these items decide whether a window can be met:
- The mint address, checked against the name, ticker and image the console shows.
- Wallets, band and length chosen, with target volume and the fee written down.
- Comment lines in a .txt file, one per line, under 512 KB, in your audience's language.
- The config link copied and sent to whoever signs off on the plan.
- The exact fee in a wallet you control, ready to send by Solana Pay QR or address.
- The window you want, in UTC, ready to send to support.
None of this involves handing anything over. PumpCrest never asks for a seed phrase, a private key or a wallet connection, so the only action at funding time is your own transfer.
How does the queued start window work?
After you send the fee, the console watches the payment address on-chain and shows the confirmed transaction with a Solscan link. The session is then queued, and support confirms the start window. Saved projects in your browser show the order as awaiting payment, then running, then finished.
Two habits help. Fund earlier than feels necessary, so the queue and the confirmation happen before your moment rather than during it. And state the target in plain terms, such as "start near 17:45 UTC, one hour", by email to support@pumpcrest.com. Support works by email with no phone line, so put the request in writing instead of planning a call.
What if the token has already graduated?
Then the clock is tied less to mint and more to your own news. The session trades where the token trades now: PumpSwap for current Pump.fun graduations, Raydium for older ones, with optional mirroring to Meteora and Orca. DexScreener lists a token once it is in a pool with at least one trade, so a graduated token already has a pair page to time around.
Timing for an older token usually follows a reason: a listing, a partnership, a community event or a quiet stretch you want to fill. Running a session on an older token covers the specifics, from pool depth to band size.
Questions and answers
Can I pay for a session before the token is minted?
No. The first step is pasting a mint, and the console reads that token's public metadata before anything else, so a session needs a live token. You can prepare everything else in advance: settings, the comment file, the fee in your wallet and a note to support describing the window you want once the mint exists.
What if my announcement moves after I have paid?
Email support at support@pumpcrest.com as soon as you know, with the new time in UTC. Changes go through support whether the session is queued or running, and orders that already settled stay on-chain. The fee is not refundable once a session has started, which is one more reason to write the moment the plan shifts.
Is a weekend a good time to start?
It depends on your audience, not on a universal calendar. Some communities are livelier on weekends and some go quiet, and the only dependable guide is when your own followers post and reply. Look at the timestamps on your recent posts, convert the busiest hours to UTC and set the window there.
Should I run two short sessions instead of one long one?
It can cost the same with a different shape. Two First hour sessions are 2 x 100 SOL, so 1 SOL each and 2 SOL total, at about 13 orders a minute in two separate windows. One 10-hour session with 1,000 wallets on 0.10-0.30 SOL is also 200 SOL, but averages about 2.7 orders a minute. Pick the shape that matches your moments.
Does the start need to avoid the moment the curve completes?
No. Execution follows the token into its pool inside the same session, PumpSwap for current launches and Raydium for older ones, so graduation does not need its own timing plan. Read curve progress on the live token page rather than relying on a fixed figure, since Pump.fun has changed its thresholds over time.
Which comment language fits a regional start time?
Match the language to the region you are timing for. The built-in library covers English, Chinese, Korean, Japanese, Spanish, Portuguese, German and Russian, so a window aimed at Korea and Japan can carry Korean or Japanese lines, and a Sao Paulo evening can carry Portuguese. A custom .txt file suits a mixed audience.
Get your session into the queue early
Paste your mint, settle the numbers and fund the PumpCrest session ahead of your moment, then tell support the UTC window you are aiming for.
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.