Farm Rate Sheet

Time it, count it, and check you measured long enough. Storage constants below.

BFCBrilliance · bfcbrilliance.com/tools/minecraft-farm-rate-calculator

The numbers

ITEMS AN HOUR: count ÷ minutes x 60
Margin of error: 100 ÷ √(count)
For ±10% / ±5% / ±1%: 100 / 400 / 10,000 items
Single chest, barrel, shulker: 27 slots
Double chest: 54 slots
Double chest at stack 64: 3,456 items — worth memorising
Double chest at stack 16: 864 items
⚠ Fill time: assumes the rate HOLDS — it often will not
⚠ Count what ARRIVES: despawns and strays are already losses

Farms measured

Farm	Items	Minutes	Per hour	± %	Hrs per dbl chest

This measurement

Farm
Date
Item
Stack size
Started at (empty chest)
Minutes run
Items collected
ITEMS PER HOUR
STACKS PER HOUR
MARGIN OF ERROR
Long enough?
HOURS TO FILL

Measuring a farm honestly

Chest emptied before starting the clock
Time recorded, not estimated
Stayed in range the whole time — chunks unload when you leave
Collected at least 400 items for a ±5% figure
Stack size set correctly before reading fill times
Counted what ARRIVED, not what the farm theoretically produced
Two farms measured the same way before comparing them
Difference between farms checked against BOTH margins of error

Measure longer, do not argue

Two players with identical farms reporting different rates is almost always a measurement-length problem rather than a build problem. At 100 items the figure carries about ±10%, which is easily enough for two honest measurements to disagree by a fifth. Four hundred items halves that. Ten thousand gets you to about ±1%. The disagreement is in the stopwatch, not the redstone.

Measured beats designed

A measured rate already contains your chunk loading, your mob caps, your hopper throughput and whatever is quietly going wrong. A design figure contains none of it. Work out what the build SHOULD do from its redstone timing, measure what it DOES with this, and the gap between them is your bug list.