How do I calculate the hash rate of a mining rig?

GlobalPublished 6 October 2026 · Written by BuyMeWhiskey Editorial Team · How we check facts

A mining rig’s hash rate is the number of hash attempts it can perform per second. Use a manufacturer benchmark, a pool’s measured worker rate or a timed local test, then convert the result into one unit before comparing equipment or modelling output.

Next question: Is a Bitcoin USB miner worth using today? →

Benchmark the rig over a meaningful period and record power draw beside the hash rate if you are assessing whether mining is economically worthwhile.

See how Bitcoin Core estimates network hash rate

Run your own numbers: Compound interest and savings calculator.

Hash rate is throughput, not income

If a machine performs one million hash attempts each second, its raw throughput is 1 MH/s. Larger miners are commonly discussed in GH/s or TH/s. The number describes computational speed; it does not directly state how many coins the machine will earn.

When people say “my rig hashes at 500,” the missing unit matters. 500 MH/s and 500 GH/s differ by a factor of 1,000. Record the unit next to every benchmark and do not strip it out when moving numbers into a spreadsheet or mining calculator.

Three ways to get a rig’s rate

The simplest source is the hardware manufacturer’s rated performance, although real-world output can differ. A second option is the mining software dashboard, which may report an instantaneous or short-term speed. A third is the mining pool’s measured worker rate, which usually reflects accepted shares over a time window.

A timed local test can be useful when you want to compare configurations. Run the same workload for long enough to smooth out short-term noise, note rejected or stale shares where relevant, and record the temperature and power conditions under which the result was produced.

Adding several devices together

If a rig contains several devices using the same algorithm and you want a simple theoretical total, you can add their individual rates after converting them to a common unit. This works as a first approximation. Actual pool results can be lower because of downtime, rejected shares, thermal throttling and other overheads.

Do not add figures that refer to different algorithms as though they were interchangeable. A SHA-256 rate belongs to one computational problem, while a Scrypt or another algorithm’s hash rate is measured against a different workload. The unit suffix alone does not make two mining figures comparable.

How network hash rate is estimated

Bitcoin Core provides a getnetworkhashps RPC that estimates the network’s hash rate based on recent blocks. The default method uses a recent block window, so the result is an estimate rather than a sensor reading from every miner. Users can also request estimates over different block ranges or historical heights.

That network number is useful for mining calculations because it puts your rig into context. If your own hash rate stays constant while the network estimate rises, your share of the total computational work falls. The expected share of rewards therefore changes even if your machine itself has not.

Why pool rate and miner rate can disagree

Mining software can show a local rate calculated from successful hashing work, while the pool sees submitted shares that arrive over a network connection. Short-term variance means the pool’s displayed number can move around more than a hardware benchmark. A stale share or rejected share can also affect what the pool counts as useful work.

When comparing two miners, use the same measurement method. Comparing a manufacturer’s peak number for one machine with a pool’s long-term average for another creates a false impression of precision.

Connect hash rate to electricity, not a fantasy daily payout

To assess mining economics, pair hash rate with electrical consumption. A rig producing 100 TH/s at one power level can be a very different business from another rig producing 100 TH/s at a much higher power draw. Electricity price converts the wattage into a recurring cost.

Also remember that network conditions change. Difficulty and competing hash power can move, while pool fees and Bitcoin’s market price affect the value of the reward. A hash-rate benchmark is therefore the starting point of the calculation, not the answer to the profitability question.

For repeated testing, keep the same algorithm, miner configuration, clock settings and observation window. Changing several variables at once makes it difficult to tell whether a higher reported rate came from hardware tuning, software changes or ordinary short-term variance.

Worked example

Illustrative rig calculation: a small setup contains three identical devices, each measured at 20 GH/s during a stable test.

Device 1: 20 GH/s
Device 2: 20 GH/s
Device 3: 20 GH/s
Theoretical combined rate: 20 + 20 + 20 = 60 GH/s

If the pool later reports 54 GH/s over a longer window, the two figures are not necessarily contradictory. The local benchmark may represent a near-peak machine rate, while the pool figure incorporates communication delays, rejected shares, temperature changes or periods when one device was not working. The longer measurement is often more useful for a profitability model.

The difference illustrates why a rig should be benchmarked under repeatable conditions. If the machine is throttling or one device is intermittently offline, a peak reading can overstate what the pool will observe over a longer operating period.

What is a megahash per second?#

A megahash per second, or MH/s, means one million hash attempts each second. It is a unit of computational throughput. The same hardware can be expressed in GH/s or TH/s by changing the scale; the underlying hash rate has not changed.

How can I measure a mining rig instead of trusting the advertised rate?#

Run the miner under stable conditions, record its reported rate over a meaningful period and compare the result with accepted-share statistics from the pool if applicable. Record temperature, uptime and power draw as well. A short peak reading can look impressive without representing what the machine actually contributes over a full day.

Can I add the hash rates of multiple GPUs?#

You can add them when they are solving the same algorithm and the rates use the same unit. Convert first, then sum. If the devices are using different algorithms, a simple addition would produce a meaningless number because the underlying workloads are not equivalent.

Why is my pool hash rate lower than my miner’s hash rate?#

The pool and the miner may be using different time windows and measurement methods. Network delays, rejected shares, temporary downtime and natural statistical variation can all create a gap. Compare like with like: a long-run pool average should not be judged against a brief local peak as though they were the same metric.

What does getnetworkhashps calculate?#

Bitcoin Core’s getnetworkhashps returns an estimate of network hashes per second based on a chosen number of blocks or a historical height. It is an inference from observed block-production difficulty and timing, not a centralised meter recording every active mining machine.

Does a higher hash rate automatically mean higher profit?#

No. Higher throughput can increase the miner’s expected share of computational work, but electricity consumption, hardware cost, network difficulty, pool fees and the market value of the reward all affect the financial result. A lower-hash-rate machine with much better efficiency can sometimes be the better business choice.

Keep reading

Next question →Is a Bitcoin USB miner worth using today?

Sources

Figures were checked against these sources before publication. If a rule changes, we update the page and show the new date.

General information, not personal financial advice. Rules depend on your circumstances; check the official source or speak to a regulated adviser before acting.