How the numbers changed across scans, with method changes marked.

How to read it: Each point is one scan. Points on either side of a marked method change were measured differently.

Words used here:

History

Chrome (Chromium) series

1 Chrome (Chromium) scan on 2026-11-12; no methodology breaks.

Scans
1
First scan
2026-11-12
Latest scan
2026-11-12
Methodology breaks
0

History of Noxtica in Chrome (Chromium). Each scan is one browser, one egress region and one method version. Browsers are never merged: the Firefox series is a separate view.

Method versions
NR-v0.3.0
Chrome (Chromium) versions
153.0.8010.12
Egress regions
tr-workstation
Dataset kinds
Production measurements
Not enough scans for a trend
Only one scan so far: trends need at least two matched scans. The scan is listed under Scan records with its before-choice counts.

Between scans

What changed between scans

For each pair of neighbouring scans of this browser: what appears in one and not in the other, where the two were measured the same way.

This browser has one scan, so there is no pair of scans to compare.

Every scan

Scan records

One row per scan, with the measurement context that decides comparability. Count columns are before-choice means over the valid repeats of each scan (one repeat is one page load). Valid / total runs counts every scenario; runs that are not valid are never merged into comparisons.

Scan records of the Chrome (Chromium) series
Chrome (Chromium) versionRegionMethodDataset kindValid / total runsSignal familiesAPI eventsThird-party destinationsData-flow-linked transmissions
NR-SC-01M78Z5AJYGGGCT488SE7AQK3NSelected153.0.8010.12tr-workstationNR-v0.3.0Production measurements12 / 121317,87310