How Hubstaff Activity Tracking Works: The Formula Explained

If your employer or client uses Hubstaff, you have probably noticed a small percentage next to each block of tracked time. Most people assume it measures how hard they are working. It does not. It measures whether your mouse or keyboard moved, second by second, and nothing else.

This guide breaks down the real mechanics: the formula, what registers as input, why genuine focused work often scores badly, and the things the number is structurally incapable of seeing. Everything here applies to the Hubstaff desktop app in 2026.

How does Hubstaff calculate activity?

Hubstaff divides tracked time into 10-minute windows of 600 seconds. For each second it asks one yes or no question: was there at least one mouse or keyboard event during that second? The percentage is the share of seconds that answered yes.

So if 270 of the 600 seconds in a window had at least one input event, your activity level for that window is 45 percent. Whether you moved the mouse once in that second or a hundred times makes no difference. One event marks the whole second as active.

The per-second value stored is effectively a boolean, true or false. This is why the metric cannot be gamed by moving the mouse frantically: intensity is discarded at the moment of measurement. What matters is coverage across seconds, not volume within them.

What counts as activity

Only two categories of input register with the tracker, and both are treated identically.

• •Mouse activity. Movement, clicks, and scrolling all register as input events.
• •Keyboard activity. Any keypress, including modifier keys, arrow keys, and shortcuts.

The content of what you type or click is never part of the percentage. Typing a single space registers exactly the same as writing a paragraph of code. The algorithm is content-blind at this layer, and that is by design rather than by omission.

What does not register

• •Looking at the screen without touching anything
• •Speaking on a call, even a video call using the same machine
• •Reading a long document or reviewing a design
• •Work on a second device, a phone, a tablet, or paper
• •Watching a screen share where the presenter is driving

Every item on that list is real work, and every one of them scores zero. That mismatch is the central problem with input-based measurement, and it is not something Hubstaff can fix without changing what it measures.

How the 10-minute window shapes the number

Because the window is fixed at 600 seconds, short bursts of input spread thinly across a window score better than the same total input concentrated in one stretch. This is counterintuitive and worth an example.

The first row is the case that frustrates people most. Three minutes of intense, valuable typing followed by seven minutes of careful reading is an excellent working pattern, and it scores 30 percent. A colleague idly scrolling for ten minutes scores far higher.

Windows are also independent of each other. A 20 percent window followed by an 80 percent window averages to 50, but reviewers often look at individual blocks rather than the daily average, which makes the low windows more visible than the arithmetic suggests.

What a normal Hubstaff activity level looks like

Genuine knowledge work usually lands between 40 and 70 percent across a full day. A sustained 95 to 100 percent is unusual for humans, because it implies non-stop input with no pauses to read or think.

Ranges vary a lot by role. Data entry and support work naturally run high because the job is continuous input. Engineering, design, writing, and analysis run lower because the job includes long input-free stretches that are not breaks.

We go into the specific numbers, what managers actually look at, and what to do about a low score in Hubstaff activity levels explained.

Idle time and the away threshold

If the tracker sees no input for a sustained period, it flags that stretch as idle and may prompt you to confirm whether to keep or discard the time. The threshold is configurable by the account owner, commonly somewhere in the range of a few minutes.

The underlying logic is the same second-by-second check. Sustained inactivity is just a long unbroken run of inactive seconds, and the idle prompt is a threshold on top of that run rather than a separate detection system.

What happens when you answer that prompt, and whether discarded time affects your percentage, is covered in Hubstaff idle time explained.

Screenshots are a separate system

Hubstaff can also take periodic screenshots, up to three per 10-minute window at randomized moments. These are images, and they have no connection to the activity percentage in either direction.

A high activity score does not produce more screenshots. A low one does not produce fewer. Organizations can disable screenshots entirely while activity tracking continues, which many do. The full detail is in our screenshot guide, and multi-monitor behavior is in the dual-monitor breakdown.

What Hubstaff cannot see

Because the activity layer only measures input timing, there is a great deal it has no visibility into at all.

• •Whether the work you produced was good, relevant, or even real
• •Time spent reading, thinking, or on calls, all of which look inactive
• •Work done on a second device, on paper, or in a meeting away from the keyboard
• •The difference between deliberate work and idle fidgeting, since both are just input events
• •Whether the person at the keyboard is you

That final point is not a security warning, it is a statement about the metric's scope. It measures a machine's input stream. It does not and cannot measure a person's contribution. Anyone treating the percentage as a productivity score is reading more into it than the data supports.

The wider version of this question, across all monitoring tools rather than just Hubstaff, is in what employee monitoring software can actually see.

Why the number matters anyway

None of the above makes the percentage harmless to ignore. On many contracts, particularly hourly freelance work, the number is visible to whoever approves your invoice, and a low score invites questions regardless of how good the underlying work was.

That is the practical bind. The metric is a poor measure of work, and it is also the metric you are judged by. Understanding the mechanism at least lets you see which of your working patterns the number penalizes, and which parts of your day it simply cannot represent.

Keeping a realistic activity level

Because the metric rewards consistent input rather than output, long reading or thinking sessions drag your numbers down even when you are fully engaged. There are workflow changes that help, such as scrolling as you read rather than sitting still, and taking notes in a document instead of on paper.

That is also the problem tools like Ghost Mode are built for. Ghost Mode generates natural, varied mouse movement, window focus changes, and keystroke timing so that genuine work time, including the parts spent reading or thinking, is not misread as idle.

The goal is not a fake 100 percent. That pattern is unnatural, it stands out to a reviewer, and it is the single most common mistake with tools in this category. The goal is a realistic, human-looking level that reflects the fact that you were at your desk working, including during the quiet moments input-based trackers penalize.

If your own score is sitting low, we wrote a practical follow-up on how to increase your Hubstaff activity score. If you are weighing tools, mouse jiggler vs activity simulator covers the technical difference between the two categories.