How to Run a Raid Train on Twitch

Almost every raid train that collapses does so for the same reason: it was organized in a Google Sheet and a Discord thread. Slots go stale, nobody knows who is live, and the handoff order stops matching reality by hour three.

R3dLabs is the ultimate raid train organizer, and it has more features than any other platform built for this. Everything the format needs lives in one place:

• Train creation and sign-ups — publish a train, let streamers claim their own slots, and stop chasing people in DMs.
• A real event calendar — every train and community event in one schedule your viewers can actually see.
• OnDeck notifications — streamers get pinged (including by SMS on membership) before their slot so they're live when the raid lands.
• Live-status aware handoffs — the lineup knows who is actually streaming, so !raidnow never sends an audience to a dark channel.
• Organizer announcements — broadcast to every channel in the train at once, live in chat.
• Streamer profiles and discovery — participants get a profile page that keeps paying off after the train ends.

It is free to start, and because R3ddyBot reads directly from it, your calendar, on-deck alerts and raid targets all stay in sync with zero manual work.

Organize your raid train on R3dLabs

Eight to twelve streamers is the sweet spot for a first train. Fewer and there aren't enough handoffs to build momentum; more and coordination overwhelms whoever is organizing.

Mix sizes deliberately. A train where everyone has 3 viewers stays at 3 viewers. One or two larger channels near the start seeds the audience the rest of the train carries.

• One hour per slot — long enough to actually talk to the people who arrive, short enough that nobody drifts off.
• Put a strong host first. The opening slot sets the tone and gathers the initial crowd.
• Vary the content. Four horror games in a row loses everyone who doesn't like horror.
• Avoid dead hours unless the train is deliberately international.

The five minutes around a raid decide whether viewers stay. What works: start hyping the next streamer two or three minutes early, say their name and what they're playing, drop a shoutout in chat with a clip or an overlay card, then raid while chat is still engaged — not after you've already said goodbye and gone quiet.

On the receiving end, greet the raid by name within seconds. An automatic shoutout overlay buys you the moment you need to react properly.

Someone isn't live. Rather than raiding whoever is next on paper, !raidnow targets the next streamer in the lineup who is actually live. The train skips the gap automatically instead of dumping an audience on an offline channel.

Someone forgets their slot. OnDeck notifications ping streamers when their turn is approaching so they're live before the raid arrives.

Nobody knows the schedule. Sync the lineup to a calendar the bot can read, so !calendar answers “who's next?” without anyone hunting through Discord.

All three are R3dLabs integration modules — see the full list.

Raid viewers are passive by default; they were just watching someone else. A single interactive prompt converts far better than “hi raiders.” A check-in map where they pin their location, or a wheel spin they can trigger, gives them a reason to type in the first thirty seconds — and someone who types is far more likely to follow.

Post the full lineup in your Discord and socials with everyone tagged, and follow the streamers you hadn't met. Most of the durable value in a raid train is the other streamers, not the one-night viewer bump — the next train is easier because of who you met on this one.