schultetable
Progress dataTracker metricsComparable attempts

How to Read Schulte Table Progress Data

Learn what personal best, average, median, recent average, mistakes, and consistency mean in the Schulte Table Progress Tracker—and why each metric should stay within comparable task conditions.

By schulte-table.org editorial team ·

If you have several results, there is no single number that always deserves attention. The Progress Tracker describes the records selected by its filters. Personal best answers “what was the shortest completed duration?”, median describes the middle completed duration, average uses every completed duration, and recent average narrows the view to the latest seven completions.

Those summaries answer different questions, so disagreement among them is expected. The first check is not which card looks most favorable. It is whether the records behind the cards used the same grid, mode, input method, completion rule, and practical setup.

1. What each Tracker card actually calculates

The current Tracker applies date, size, mode, completion, and input filters, then selects one complete comparison group. The default is the newest such group. Duration formulas below use completed records within that group, not all filtered tasks together. Best is the minimum, average is sum divided by count, and median is the middle sorted duration or the average of the middle pair. All-records view preserves counts and exports without a combined time summary.

Recent average uses up to the latest seven completed records. Records are stored and read newest first, so this is not a random sample and not the first seven ever recorded. Mistakes are incorrect selections already recorded by the originating task rules. The Tracker also displays average mistakes and the share of completed records with zero mistakes; it does not reinterpret what counted as an error in the source tool.

Consistency is the coefficient of variation for completed durations. The implementation uses population variance: it divides the squared deviations by the number of included durations, takes the square root, then divides by the mean. A smaller percentage means the selected times are closer together relative to their average. It says nothing about psychological stability or a person's attention outside this browser task.

Schulte Table Progress Tracker metrics guide explaining personal best, average, median, recent average, mistakes, and consistency coefficient of variation
The tracker summarizes only the attempts included by the active filters. Read each metric together with grid size, mode, input method, completion state, and mistakes.
mean = sum(completed durations) / completed count
CV = population standard deviation / mean × 100%
recent average = mean(latest 7 completed attempts)
How to use the current Progress Tracker summaries
MetricWhat it summarizesUseful forMain limitation
Personal bestFastest completed round in the filtersRemembering a shortest local attemptCan be an outlier
AverageMean of all filtered completed timesLocating the center of the whole included setSensitive to unusual rounds
MedianMiddle filtered durationA center less changed by one extreme valueStill depends on which records were included
Recent averageLatest 7 completed attemptsReviewing recent local resultsA small set can move quickly
MistakesIncorrect selections recorded by source rulesKeeping accuracy context next to timeRules must match before comparison
Consistency (CV)Relative spread of filtered durationsSeeing how tightly times clusterNot a psychological measure

2. Worked example: why best, median, and average differ

Take five comparable completed times: 31.2, 32.1, 31.8, 49.5, and 31.7 seconds. Sorting them gives 31.2, 31.7, 31.8, 32.1, 49.5. Personal best is therefore 31.2 seconds and the middle value is 31.8 seconds.

The total is 176.3 seconds, so the average is 176.3 ÷ 5 = 35.26 seconds. The 49.5-second round raises the average, but it does not change the median by the same amount. Using the Tracker's population formula, the standard deviation is about 7.1259 seconds and CV is about 20.21%. That relatively wide spread is a description of these five durations, not a reason to erase the slower one.

Five-round calculation
Raw timesPersonal bestMedianAveragePopulation CV
31.2, 32.1, 31.8, 49.5, 31.7s31.2s31.8s35.26s20.21%

3. Filters determine whether a summary is interpretable

The Tracker filters by preset or custom date range, size, mode, completion, and available input method. Attempt counts include all filtered rows; time metrics use the chosen complete comparison group. A record can remain listed and exportable without qualifying for strict time statistics.

Select one grid size and one mode before treating a median or CV as a comparison series. A 3×3 round and a 10×10 round have different target counts. Standard ascending, descending, letter, red-black, and alternating number-letter records use different sequences. Mouse, touch, and keyboard activations create different interaction paths. Interrupted records should not be silently treated as completed durations.

The schema stores gridSize, mode, completed, durationMs, mistakes, optional inputMethod, identifiers, and timestamps. New classic results also store timingPolicy, errorPolicy, sourceKind, replayKind, pauseUsed, and displayProfile. The latter includes viewport dimensions, pixel ratio, and appearance settings. These local details help group conditions but do not identify or calibrate a physical device; keep actual device and viewing distance stable yourself.

  • Same grid size
  • Same mode and direction
  • Same input method
  • Same completion and error rules
  • Comparable device, zoom, display scale, and orientation
  • No unrecorded interruption

4. Why a best time is not a trend

Suppose the recent list is 34.0, 33.8, 34.2, 24.1, and 34.1 seconds. The 24.1-second entry becomes the personal best immediately, but the other four remain clustered around 34 seconds. The shortest entry may be a valid round. It may also involve a changed setup, a different input path, an interruption handled differently, or a record entered through the calculator with the wrong mode label.

Do not delete it merely because it is unusual, and do not call the full series improved merely because the minimum changed. Inspect the raw JSON or CSV record, its mistakes, mode, gridSize, inputMethod, and timestamp. Then check details the schema cannot hold, such as zoom and device. A trend requires the sequence of comparable observations, not only the most favorable endpoint.

The Tracker's “hide values beyond 3 standard deviations” option changes only the chart display. It does not remove the saved records or exclude them from summary cards.

5. Use exports to inspect, not to manufacture a cleaner story

CSV export includes the original version, ID, time, size, mode, duration, mistakes, completion, input, and challenge columns, plus optional comparison metadata for newer classic rounds. JSON preserves the versioned wrapper, export time, and full records. Import validates records, merges them with current history, and deduplicates IDs. Older files without the added metadata remain readable, with strict comparison unavailable when measurement facts are missing.

An export is useful for checking the exact rows behind a summary or keeping a backup before deletion. It is not evidence that different tasks became comparable. If you split data into groups in a spreadsheet, use the same conditions that the Tracker filters represent and document any extra conditions you add manually.

6. What these data can and cannot support

The cards can describe shortest time, central values, recent values, recorded mistakes, and duration spread for the selected local task records. They can help you notice a questionable entry, compare two like-for-like personal sets, or decide that a setup change needs its own group.

They cannot diagnose a health condition, determine attention, assign intelligence, place a result in a population rank, or guarantee a transfer to reading or study. The site has no matched population dataset behind these cards. The safest reading remains literal: these are summaries of the current browser's included task records.

Related tools

Site references