How do I read the hashrate output in XMRig?

XMRig’s hashrate output tells you how quickly your computer is doing mining work. Start with the line labeled speed 10s/60s/15m: those numbers show your average speed over three different time windows, so you can separate short-term changes from steady performance.

Read the speed line from left to right

You might see a line like this, with a date and time before it:

miner speed 10s/60s/15m 2450.5 2418.2 2396.7 H/s max 2580.1 H/s

These are example numbers, not speeds you should expect from your computer.

Here is what each part means:

• miner identifies this as a mining status message.
• 10s — 2450.5 is your average speed over the latest 10 seconds.
• 60s — 2418.2 is your average speed over the latest minute.
• 15m — 2396.7 is your average speed over the latest 15 minutes.
• H/s means hashes per second. A hash is one calculation used in the search for a valid mining result.
• max — 2580.1 H/s is the highest speed XMRig has recorded during this run, not a speed it promises to maintain.

The three averages all use the unit printed after them. If you compare them with a dashboard, remember that 1 kH/s equals 1,000 H/s, and 1 MH/s equals 1,000,000 H/s.

Choose the right average

The 10-second average responds quickly. Use it to see what happens when you open another program or change a mining setting. It can jump around without anything being wrong.

The 60-second average gives you a more settled view. It is usually a useful number for checking how your miner is doing right now.

The 15-minute average is better for judging sustained performance. Give XMRig time to run before relying on it. Shortly after startup, some averages may show n/a, meaning there is not enough history yet.

For a fair comparison between settings, keep other computer activity similar and allow the machine to warm up. Heat can cause your processor to slow down, so a brief peak is less useful than a steady average.

Check the per-thread breakdown

In XMRig’s interactive console, press h to print a hashrate report. This can show both the total and individual mining threads. A thread is one stream of work running on your processor.

The regular speed line is your combined mining speed. Do not multiply it by your thread count again.

Small differences between threads are normal. A thread that stays at zero, or performs far below the others, deserves investigation. Check the startup messages for errors and whether other software is heavily using your processor.

Separate speed from accepted work

Messages such as accepted and rejected describe shares: mining results submitted to your pool to prove your contribution. They are not hashrate readings.

Your pool estimates speed from submitted shares. XMRig measures work locally, so the two readings will not always match, especially over short periods.

A healthy local hashrate does not guarantee that work reaches the pool. If accepted shares stop or rejections keep increasing, check connection and error messages. Also, diff, meaning difficulty, describes how hard a work target is—not your speed or earnings.

The bottom line

Use the 60-second average for a quick check and the 15-minute average for steady performance. Treat max as a peak, and check accepted shares alongside hashrate to confirm your mining work is reaching the pool.