How many simulators do I need
In shortQueue tolerance, not headcount. A trade show visitor waits a few minutes. A party guest waits twenty. The same crowd needs different builds.
This is the most common question we get and the one most vendors answer with a number that happens to match what they want to sell you.
The real driver is not headcount. It is how long your particular crowd will stand in a line before they walk away.
Queue tolerance is the variable
Three hundred people at a trade show and three hundred people at a company party are not the same sizing problem, even though the headcount is identical.
At a show, your guest has somewhere else to be and a hall full of alternatives. They glance at the queue and keep walking. At a party, they have nowhere else to be and the queue is where their colleagues are standing, so waiting is part of the evening.
| Event type | Queue tolerance | Implication |
|---|---|---|
| Trade show | Low. A few minutes | More rigs, shorter sessions |
| Auto show | Low | Two is the floor, four is common |
| Conference | Medium, spiking at breaks | A running leaderboard smooths the spike better than extra rigs |
| Company party | High | Two rigs is enough for most rooms |
| Hospitality | Not applicable | One rig, long sessions |
Where the number actually comes from
One rig
Hospitality, small groups, photo-led activations, and any build where branding matters more than throughput.
Two rigs
The floor for anything with head-to-head. Brackets, finals, company parties, most conferences.
Four or more
Trade shows and auto shows at scale, where queue tolerance is low and the leaderboard needs volume to stay competitive.
Fewer than you think
A common recommendation from us. Two well-run rigs beat four under-staffed ones, and the second rig costs less than the first.
What we cannot tell you yet, precisely
A proper sizing calculation needs measured throughput per configuration, and the right way to measure it is cycle time, seat to seat, including briefing, exit and reset. That is always longer than session length, and the gap is exactly what makes most planners' estimates wrong.
We are measuring it across three events per configuration with different crowd types, and we will publish ranges with the method and the drivers named. Competitors publish a single round number with no method. A stated method beats a bigger number.
Until then we size from experience, and we tell you that is what we are doing.
What people ask about sizing
How many racing simulators do I need?
The honest answer is that it depends on queue tolerance rather than headcount. A trade show visitor waits a few minutes and walks. A party guest waits twenty. The same 300 people need a different number of rigs at those two events.
Is one rig ever enough?
Often. For hospitality with twenty guests, one is usually better than two, because two splits a small group. For a photo-led brand activation, one well-branded rig beats two plain ones.
When do I definitely need two?
Any time head-to-head racing is part of the format. A bracket, a final, a race between two executives. You cannot run those on one rig, and they are usually the part people remember.
Does the second rig cost the same as the first?
No, it costs less. One crew and one freight movement cover both, and the saving is quoted per build because it depends which configurations you combine.
How do I work out throughput?
Properly, you measure cycle time, which is seat to seat rather than session length. We are measuring ours per configuration and will publish ranges with the method. Until then we size from experience and say so.
What if I guess wrong?
Too few is worse than too many, and not symmetrically. A queue that is too long disperses and does not come back; a rig with spare capacity is just a shorter wait.
Get a quote
Tell us about your event.
Tell us the event type, the headcount and the hours. We will give you a rig count and the reasoning, including when it is fewer than you expected.
No newsletter, no drip sequence. One reply from a person. Open the form in a new tab if it does not load.