The average starts again at every gantry, so an easy finish cannot rescue a fast start on the section before it. Limiter is an iOS app that shows the average you have actually driven, and the one speed to hold for the rest of the section.
Limiter is not released. There is nothing to download yet and no date has been set. Leave your email and you get one message when early access opens.
It reads your number plate where the section starts and again where it ends. Your speed is the length of the section divided by the time between those two readings. Nothing in between is measured on its own. That makes three things true that most drivers get wrong.
The A2 southbound looks like one long check. It is five sections of 2.9, 1.7, 4.4, 1.2 and 5.3 km, each measured on its own, each with its own pair of cameras. A careful 80 through section four does nothing about the 120 you drove in section three.
Three kilometres at 130 at the start of a 10 km section uses 1 minute 23 seconds. The remaining 7 km then has to take at least 4 minutes 37 seconds, which means holding 91 km/h. By that point the arithmetic is fixed, and the only open question is what the rest of the road needs.
UN Regulation 39 lets a car read up to 10 percent plus 6 km/h above true speed, and never below it. At a true 107 the dial can legitimately show 121. Limiter shows GPS speed, because that is the number the average is built from.
Where 107 comes from: the prosecutor subtracts a measurement correction from the measured average, 3 km/h up to 100 km/h and 4 km/h from 101 to 133, and does not prosecute until the corrected speed is 4 km/h or more over the limit. Limiter runs its green band on the posted limit rather than on that ceiling, so green means legal and not merely unfined.
The large number is the speed to hold for the rest of the section. The bar at the top is the average driven so far. Every state carries a word and a symbol as well as a colour, so it still reads if you cannot separate red from green.
The app shows the average you have driven and the time you have in hand. There is no target to chase, because nothing needs doing.
The average is above the posted limit but no fine is in reach yet. Hold the speed shown and the section still finishes under the limit.
There is still a drivable target and the app still shows it, but there is nothing left to give. The word is not FINE LIKELY, because at this point a fine is not yet certain.
Bringing the average back would need a speed nobody should drive on a live motorway lane. The app stops issuing a target and shows the average the section is now heading for.
The flashing state is the only one that moves. Everything else holds still, including the width of the words, so a changing number never shoves the rest of the screen sideways while you are driving.
These are not disclaimers at the bottom of the page. They are decisions in how the app is built.
The app computes an average from phone GPS and compares it with the published Dutch threshold. Whether a camera took a reading, and whether anyone decided to prosecute, is not something a phone can see. Limiter will never tell you that you are safe from a fine.
The target speed is clamped at the posted limit. When you are already under it, the app reports the time you have in hand rather than a higher speed you could still get away with. It is a tool for staying legal, not for staying ahead of enforcement.
No account, no ads, no server, no crowd-sourced reports. The zone database ships inside the app and the arithmetic runs on the phone.
The app turns itself off outside the country. It knows the 76 Dutch sections that are mapped in OpenStreetMap, which is every motorway system and roughly eight of the twenty N-road systems.
Limiter is not on the App Store. When there is a build worth handing out, the people on this list hear about it first. One email about early access, not a newsletter.