Bitaxe hashrate: what real ones do
The short answer
A Bitaxe is a single-chip Bitcoin ASIC on a desk. Its speed is quoted in terahashes per second — TH/s, a trillion guesses every second. The number on the box is what the chip does at stock settings on a bench. The number that matters is what your unit holds hour after hour in your room, and those are rarely the same figure.
So this page reads a real population instead of a spec sheet. The Solo Mining Census asks Public Pool once an hour how many devices are connected under each name their firmware reports, and how much they hash between them. Public Pool is the pool most Bitaxes ship pointed at, so its device list is a large sample of working machines rather than a handful of review units.
At the census reading of 2026-09-16 15:07 UTC, the 16,820 Bitaxes connected to Public Pool averaged 1.05 TH/s each, and 17.59 PH/s between them.
What the connected miners do
At that reading, Public Pool published 50 different device names. These are the 12 with the most devices connected.
| Device name, as reported | Connected | Combined | Average each | Hardest share |
|---|---|---|---|---|
| bitaxe | 16,820 | 17.59 PH/s | 1.05 TH/s | 79.86G |
| NerdQAxe++ | 1,995 | 9.54 PH/s | 4.78 TH/s | 126.24G |
| NerdMiner | 1,348 | 839.26 GH/s | 622.60 MH/s | 80.77M |
| cgminer | 760 | 6.85 PH/s | 9.01 TH/s | 194.04G |
| LuckyMiner | 672 | 834.44 TH/s | 1.24 TH/s | 2.00G |
| NerdAxe | 507 | 393.54 TH/s | 776.21 GH/s | 15.99G |
| Other | 448 | 89.23 TH/s | 199.17 GH/s | 95 |
| cpuminer | 406 | 9.40 GH/s | 23.15 MH/s | 274.98K |
| NerdOCTAXE | 329 | 3.38 PH/s | 10.28 TH/s | 67.75G |
| bitaxe/sv2 | 258 | 313.73 TH/s | 1.22 TH/s | 30.54G |
| NerdNOS | 250 | 37.70 TH/s | 150.81 GH/s | 320.77M |
| Starminer | 228 | 310.71 TH/s | 1.36 TH/s | 2.47G |
Names are shown as the firmware reports them, merged only where they differ by capital letters; a few are version numbers rather than device names. This is Public Pool's population, not every solo miner. The whole list is in the Solo Mining Census and its CSV. The last column is each name's hardest single share — the figure AxeOS labels Best Difficulty.
What a hashrate figure means for one miner
Bitcoin's difficulty, read from SoloLuck's own Bitcoin node as this page rendered, is 127.45T. A block is one hash that hard, and on average it takes that difficulty times 232 hashes to find one. Divide that by what a machine does per second and you have its average wait.
| Device name, as reported | Average each | Average wait for a block | One year of it |
|---|---|---|---|
| bitaxe | 1.05 TH/s | ≈ 16.6k yr | 1 in 17,000 |
| NerdQAxe++ | 4.78 TH/s | ≈ 3.6k yr | 1 in 3,600 |
| NerdMiner | 622.60 MH/s | ≈ 27.9 million yr | 1 in 28,000,000 |
| cgminer | 9.01 TH/s | ≈ 1.9k yr | 1 in 1,900 |
| LuckyMiner | 1.24 TH/s | ≈ 14.0k yr | 1 in 14,000 |
| NerdAxe | 776.21 GH/s | ≈ 22.3k yr | 1 in 22,000 |
The last column is 1 in how many of a Bitcoin block a whole year at that speed is, at today's difficulty.
The whole Bitcoin network is hashing 876.68 EH/s at that difficulty, so one Bitaxe at the census average is 1 in 838.3 million of it.
Every hash is a fresh draw. A machine that has run for a year stands exactly where one switched on this morning stands: a mean time to a block is an average over many lifetimes of the machine, not a countdown, and nothing is stored up along the way. Put your own figure into the odds calculator.
What moves your own number
The chip. A Bitaxe carries one ASIC, and which one it is sets the ceiling. Nothing in the firmware makes an older chip into a newer one, and a board carrying several chips is a different class of machine again — which is why the census counts every reported name separately instead of lumping them together.
Tuning. AxeOS exposes frequency and core voltage. More frequency is more hashes, more heat and more watts. Push past what the voltage supports and the chip returns hardware errors instead — work already done and thrown away, so the usable figure falls while the clock reads higher. The tested numbers for a Gamma are on the Bitaxe setup guide.
Heat. A hot chip throttles, and a hot voltage regulator fails before the chip does. A warm room is a different machine from a cool one, with the same settings and the same firmware. Watch the regulator temperature, not only the ASIC.
Power. An undersized or noisy supply usually shows up as errors and restarts rather than as a lower clock, so it is easy to blame on the pool.
The window you are reading. A pool cannot see your chip; it counts the shares that arrived and divides by a window. Over a short window that figure jumps around while the machine runs at a steady speed. Over an hour it settles. Neither is wrong; they are different questions.
Where to read your own
AxeOS prints a live figure on the miner's own home screen. Your pool prints its own, computed from the shares that actually arrived — that is the one worth writing down, because it already excludes the work that never landed. On SoloLuck the address page https://sololuck.io/users/your-address lists every worker and its hashrate, and the pool as a whole is on /status.
SoloLuck is one of the pools the census reads, on the same terms as all the others. SoloLuck has not found a Bitcoin block. Point a miner here if the pool suits you, and check the figure yourself either way.
FAQ
How much does a Bitaxe hash?
It depends on the model and how it is tuned, so one printed number would be a guess. This page gives a measurement instead: the average of every Bitaxe connected to Public Pool, read once an hour by the Solo Mining Census. That average moves, and the page reads it again every time it is opened.
Why is my Bitaxe slower than the figure on the box?
Heat, tuning and hardware errors. A hot chip throttles, and a chip pushed past the voltage it has returns errors, which are hashes thrown away. A pool's figure is also an average over a window, so it lags a change you made a minute ago.
Does more hashrate improve my odds?
In proportion, and only in proportion. Twice the hashrate is twice the tickets in the same draw. It is not a different game: every hash is a fresh draw, and the wait for a block is an average over many lifetimes of the machine, not a countdown.
Is a Bitaxe fast enough to solve a Bitcoin block?
Any single hash can solve a block, which is the whole point of solo mining. At today's difficulty the average wait for one small machine is very long, so treat it as a cheap lottery ticket that pays the entire block reward if it lands.
Ready to start solo mining?
Paste your address and copy the config from /setup, find your port and difficulty floor on /connect, watch the pool on /status, and check every claim on /verify. Mine to your own address — that is what makes it truly solo.
Start MiningCalculate Your Odds
Not ready to point a miner yet? Join Telegram for block & record alerts — no rig required.