Skip to content

What The Telemetry Shows

The Arcade Lab has run and it was recorded. This page reports what the logs contain, counted rather than summarised, including the number that undercuts the whole idea.

The Number That Matters Most

Across eight recorded sessions between 11 and 23 August 2026 the arcade produced 237,951 events. Of those, 170 were a button being pressed.

That is one input for every 1,155 frames observed. Dave watched the games far more than he played them. Any honest reading of this data starts there, because it is the fact most easily hidden by a large event count.

What Was Recorded

What Was Independently Verified

Separately from the event logs, a runtime and browser sweep was run on 22 August 2026 and its receipt is the reason this lane is described as working at all.

Five of five ROMs passed the runtime gates, mean runtime quality 100 out of 100.

Four of four Chrome cases passed, with 50 live frames witnessed at desktop size and 47 at phone size, 0 page exceptions and 0 failed requests.

The verifier deliberately refused to accept an HTTP health response as proof. It required a real game loaded, player-thread activity, frame advance and injected input for each ROM before it would pass. That is the difference between proving a service is up and proving a game is running.

What This Does Not Show

Go Deeper

Dave Arcade Lab, what the lab is for and the five-game tray.

What Dave Is, who Dave is and what he will not do.

How Dave Works, the limits stated up front.