Stat

A number someone checks, with its unit, how it moved and its trend. With Sparkline, the trend on its own.

A row of stats

A project’s overview in one frame. The change is green only where it’s good news; the temperature’s fall is neither.

Missions this year
17of 20
+2 vs 2025
Surface temperature
9,4°C
−0,6 since last round
Uploads this week
25
5 a day
Open deviations
3 1 overdue
+2 this week
<StatGroup>
	<Stat label="Missions this year" value="17" unit="of 20" change="+2 vs 2025" tone="good" trend={missions} />
	<Stat label="Surface temperature" value="9,4" unit="°C" change="−0,6 since last round" trend={temperature} />
</StatGroup>

In a card

The number a card is about, large, with room for the trend under it.

Surface temperature

AU1, 1 m

Now
9,4°C
−0,6 since last round
Dec 2025Nov 2026

Battery

Otter Pro, the last 14 days

Now
95%
Charged overnight
6 NovNo contact 10–11 NovToday
<Sparkline values={battery} domain={[0, 100]} dot class="h-16 w-full" />

Sparkline

The line on its own: how it reads with each option.

Smooth

Measurements. Never overshoots.

Linear

Counts, which step.

A gap

No contact for two days: the line breaks.

Own extent

Salinity up about 0,5 %, drawn as a cliff.

Pinned domain

The same, on 30 to 35 PSU: barely a rise.

Line only, with dot

In a dense row, or tied to a number.

Columns

Amounts per day: uploads, none at weekends.

Columns, newest

With dot, the newest bar stands out.

Above and below zero

Fuel bunkered, then burnt, by week.

Rules

  • A Stat is a number someone checks. If nobody would act on it moving, it doesn’t belong at the top of the page.
  • The change says what it’s against: "+2 vs 2025", "−0,6 since last round". A bare "+2" leaves the reader guessing.
  • Its colour says whether the move is good news, not which way it went. Fuel down is bad, alarms down is good, a temperature is neither: leave it neutral.
  • The value comes formatted, in the page’s decimal mark: 9,4, not 9.4.
  • A sparkline is the shape, not the values. Its own extent shows any change as a big one; pass a domain when the size of the change matters, as with a battery’s 0 to 100.
  • Columns for amounts that add up (uploads a day, samples a week), lines for measurements. Columns start at zero, always.
  • Linear for counts, which step; smooth for measurements. Smooth never overshoots: no peak higher than the highest value.
  • A missing value breaks the line. Don’t draw across a stretch with no data.
  • Stats go in a StatGroup or a Card, never in a card each in a row: that’s a page of boxes.