Clever Quest Lab ← Labs

Number Sense Test

Pick the colour with more dots after a short flash, then enter how many dots you saw: you get your Weber fraction and subitizing range, each with a 95% interval.

Settings

What to run
Length of task A

This run

No finished task yet. Your result appears here.

History

Tasks you finish on this device are listed here.

See all your results

Slovenčina

Runs on your device. Nothing you type or record is uploaded. Keeps working without a connection while the page is open. Works with touch. Saves each run's trials, Weber fraction and subitizing range with their intervals, and the chosen length and language; Clear history deletes the runs.

Added · Updated : the result line shows the planned flash with the measured mean, chart points are no longer cut off at 100%, and a phone scrolls to This run

What the test asks

Two skills that need no counting. Can you tell which of two sets is larger when there is no time to count? And how many things can you take in at a glance, before counting has to start? Task A measures the first and gives your Weber fraction w; task B measures the second and gives your subitizing range. Either can be run alone, and each is saved as soon as it ends.

Task A: which colour has more

The two counts are in one of five ratios, 1:2, 3:4, 5:6, 7:8 or 9:10, with 5 to 20 dots per colour. In half of the trials both colours have the same mean dot size, so the colour with more dots also covers more of the field. In the other half both cover the same total area, so the colour with more dots has smaller dots. Each dot differs from the average of its colour by up to 35%. Blue and yellow are used because the common red-green types of colour blindness do not confuse them.

Short is 160 trials and Long is 400, split equally among ratios and size rules, with a break every 80 or 100 trials. Your first run starts with 10 easy practice trials that tell you whether you were right; they do not count.

The design follows Halberda, Mazzocco and Feigenson (2008), who tested 14-year-olds with four ratios and 5 to 16 dots per colour, and the web version of Halberda et al. (2012) with 5 to 20. The ratio 9:10 is added here, so that a sharp observer still makes mistakes to measure.

How w is calculated

The model of Halberda et al. (2008) treats each set as a noisy inner estimate whose spread grows with the number: w = 0.2 means that 10 dots feel like anything around 8 to 12. A smaller w is a finer number sense. Comparing two such estimates gives the chance of a right answer:

p = l/2 + (1 − l) · Φ( |n1 − n2| / (w · √(n1² + n2²)) )

Φ is the standard normal distribution; n1 and n2 are the two counts. With 10 against 20 dots and w = 0.2 the second part is Φ(2.236) = 98.73%. Only the ratio matters, so all pairs with one ratio share one point on the curve.

The original model has only w. This page adds a lapse rate l from 0 to 10%: the share of trials where you blinked or looked away and could only guess. Without it those trials are blamed on w: in a simulation with 4% lapses and w = 0.2 at 400 trials, a model without the lapse rate overstated w by about 12%.

The page finds the w and l under which your answers were most probable. The 95% interval holds every w under which they stay nearly as probable: twice the difference in log likelihood is below 3.84, with l refitted for each w. w is searched from 0.02 to 2; a result at either end means the test did not settle, and the page says so.

The effect of area is w (equal area) − w (equal size), with its own interval from the likelihood. It comes from one fit with a shared lapse rate, so it can differ a little from the two separate values on screen. If you lean on how much of the field a colour covers, the equal-area trials are harder and the difference is positive. When the interval includes 0, the run shows no clear effect.

How far to trust w

The page's calculation was run on simulated people (November 2026, 2,000 runs per case). They answer exactly by the model, so tiredness or a bad day are not in these figures:

Real people add more noise. Halberda et al. (2012) report a split-half reliability of w of 0.72 for 300 trials in 10,548 people and 0.56 for 200 trials in another 3,006.

Task B: how many dots

There are 8 trials for each number, 72 in all, in about 4 minutes, plus 9 practice trials on your first run. The timing follows experiment 1 of Leibovich-Raveh et al. (2018): 1 to 9 pictures for 350 ms and a 100 ms mask, with spoken answers.

How the subitizing range is calculated

Small numbers are named almost at once and large ones take longer, with a bend between them. The method of Leibovich-Raveh et al. (2018) finds that bend in the mean time of your correct answers for each number:

f(x) = a + b / (1 + e−k(x − x0))
range = x0 − (f(x0) − f(0)) / f′(x0)

The curve is an S rising from a to a + b, steepest at x0. The range is where the tangent at that steepest point crosses the flat line through f(0), which comes before the steepest point. With x0 = 4.5 and k = 2 it is 3.50. The chart shows both lines.

This page differs from the paper in two places, both because a run has only 8 trials per number. The paper rescales the times to run from 0 to 1 and fits only x0 and k; in simulations with so few trials that pulled the range down by about 0.3, so here a and b are fitted too. The paper drops answers more than 2.5 standard deviations from the mean, which one slow answer among 8 can never reach, so here the limit is 2.5 robust standard deviations (from the median and the median absolute deviation).

For the 95% interval the page draws your answers for each number again at random with replacement 1,000 times, refits the curve and keeps the narrowest range that holds 95% of the results. On simulated people with a true range of 3.5 and noise of 20% of the mean time (November 2026), the median estimate was 3.54, the interval held the true value in 96.9% of 1,000 runs, and it was typically 1.7 wide.

What to look for

Things to try

Comparing your result

History compares runs on the same input whose refresh rates are within 10% (or both below 50 Hz). The page gives no percentile: one run is too short for it, and the published figures come from other procedures. It only shows these next to your result:

Limits

Controls

FAQ

Should I try to count in task A?

You can't: 200 ms is too short for 20 dots. Go by your first impression and guess when you are not sure; near 9:10 the model expects a lot of guessing.

Sources