schultetable

7×7 Schulte Table

A 49-target layout for a deliberately longer round where task length and viewport density must be considered together.

Your Time

0.00s

Next

1

Click 1

Task facts

Number range
1–49
Cells
49
Ordered selections
49

Complete this grid

  1. 1

    Select Start and wait for the shuffled grid.

  2. 2

    Select 1 through 49 in ascending order.

  3. 3

    Review completion time and incorrect selections together.

  4. 4

    Repeat only with the same setup when you want a personal comparison.

What is specific to 7×7

A 49-target layout for a deliberately longer round where task length and viewport density must be considered together.

Layout

  • Nearly twice the 25 cells of 5×5
  • Seven rows create a visibly denser page even before the largest sizes

Small-screen behavior

  • A small phone may need more browser zoom or a larger device for comfortable reading
  • Changing orientation also changes target geometry

Mouse and touch

  • More targets increase total pointer movements, so raw total time reflects task length as well as interaction
  • Finger occlusion becomes more noticeable as targets narrow

Readability

  • Inspect the two-digit labels at the chosen viewing distance before starting

Printing

  • A single grid per page usually preserves more useful writing and pointing space than a multi-grid layout

How to compare this size

  • Do not treat a longer raw time than 5×5 as evidence of lower ability
  • Compare 7×7 only with 7×7 attempts under similar display conditions

Choosing a neighboring size

Choose 6×6 for a 36-target task with less density.

Use 8×8 when a four-times-4×4 cell count and print/display scaling are the specific variables you want to examine.

Your comparison context

These values come only from completed ascending rounds stored in this browser for this exact grid. Choose an input method to narrow the set.

No comparable attempts are stored yet. Complete several rounds with the same grid, device, input method, and rules before interpreting changes in your own history.

Device model, orientation, browser zoom, and display scale are not stored. Confirm those conditions yourself before treating two rows as like-for-like.

Continue with a known comparison context

Use the tracker for filters and medians, or read why total times from different conditions should stay separate.