Bee Swarm Simulator Hive Planner
Every bee guide ranks bees one at a time. You do not play one bee at a time. Add bees here and see what the hive as a whole gathers, converts, hits for, and eats.
The hive planner totals the wiki's published base stats for whichever bees you add: pollen per second, honey per second, total attack, average speed, the Red/Blue/Colourless split, and how many of each favourite treat the hive needs. All 46 bees are available. Nothing is weighted or scored — the totals are plain sums, with both formulas printed on the page.
Where the numbers come from
Wiki-synced dataEvery stat in the planner is a value the Bee Swarm Simulator Fandom wiki publishes on the bee's own page, synced August 15, 2026.
- Roster: all 46 bees, split 24 Colorless, 11 Blue, 11 Red.
- Gather and convert: the amount and cycle time the wiki publishes per bee, divided into a per-second rate.
- Attack, speed, energy: straight from the infobox, no arithmetic.
- Treats and abilities: the favourite treat and the ability names the wiki links. Effects are not synced, so the planner counts abilities without claiming what they do.
How to read your totals
Strategy — our take, not a published statOur interpretation of the numbers, offered as advice rather than fact.
- Gather rate is the constraint early. Base pollen/sec is the throughput of the loop you spend most of your session in, so a hive that raises it raises everything downstream.
- Convert rate matters in bursts. Honey/sec only applies while bees are converting at the hive, which is why bees with enormous convert numbers and ordinary gather numbers feel situational.
- Colour concentration is a trade. A hive that leans one colour lines up with colour-specific bonuses; a mixed hive is more flexible across fields. The planner shows the split so you can see which one you have actually built.
- A narrow treat bill is cheaper to run. One or two treats across the whole hive is far less upkeep than all 4 that appear on the roster.
All 46 bees ranked by base pollen/sec.
Full stat lines, searchable and comparable.
Treat index, ability index, codes and more.
Planner questions
What does the hive planner calculate?
It sums the wiki's published base stats for the exact bees you add: pollen gathered per second (collectsPollen ÷ pollenSeconds), honey converted per second (makesHoney ÷ honeySeconds), total attack, count-weighted average speed, the Red/Blue/Colourless split, how many bees share each ability name, and how many of each favourite treat the hive eats. Nothing is scored or weighted.
Does it account for bee level, Gifted bonuses or hive multipliers?
No, and that is deliberate. Level scaling, Gifted bonuses, field and hive multipliers, tools and ability effects are not in our synced dataset, so modelling them would mean inventing numbers. The totals are a base-stat floor for comparing one hive composition against another, not a prediction of in-game output.
Should I build a red hive or a blue hive?
That is a strategy question, not a data one. What the data says is that the roster is colour-balanced: 24 Colorless, 11 Blue, 11 Red. So neither colour is short of candidates, and a mono-colour hive means passing on the 24 Colourless bees that work in either.
Why does the planner cap at 50 bees?
Fifty is the hive size players consistently document in-game. It is not part of our synced wiki dataset, so the planner warns you past 50 rather than blocking you — if the cap changes, the tool still works and the warning is the only thing that is wrong.
What is the treat list for?
Feeding a bee its favourite treat is more efficient than feeding it anything else, so a hive concentrated on one or two treats is cheaper to keep working than one spread across all 4 that appear on the roster. The list totals how many bees in your build want each treat, plus how many have no favourite at all — the wiki documents Event bees as having none.