A wait-time site lives or dies on one thing: are the numbers real? Anybody can type "20 minutes" into a box from their sofa, three countries away. Until now, we simply had to hope nobody did.
From today we don't have to hope. Reporting a wait time on CustomsWait is location-verified — and better still, in most cases you don't have to type a number at all. We measure it for you.
Two taps, and we do the timing
When you reach the back of the queue, open CustomsWait and tap I've arrived at the queue. Then put your phone away and wait, like you were going to anyway. Once you're through and rolling on the other side, tap I've crossed.
That's the whole thing. We work out the minutes ourselves.
Both moments are stamped on our server at the instant you tap, so nothing depends on your phone's clock and there is no number for anyone to guess, round up, or misremember. While you're waiting, a small banner keeps you company — You're waiting at Nădlac II · 47 min so far · Crossed yet? — and it follows you around the site, so you can browse other crossings and still finish your report with one tap.
A few things that make it forgiving in real life:
- Close the tab, close the app, lock the phone. The timer lives on our side, not inside the page. It's still there when you come back, for up to 24 hours.
- Signed in? It survives anything. A flat battery, a different phone — pick the report up wherever you are.
- Changed your mind? Cancel this report throws the arrival time away. Nothing is recorded.
- We find the crossing for you. Open the site at the border and we'll ask "You appear to be at Nădlac II. Report for this crossing?" — so picking the wrong one from a list isn't a mistake you can make any more.
Already across? Just type it in
Plenty of people only reach for their phone once they're safely parked on the other side, and that's fine — the familiar form is still there. Open the crossing, tell us how long the whole thing took, send.
One thing has changed: you need to be past the border and still fairly close to it — within about 18 km. That isn't a rule to keep people out; it's an accuracy limit. At motorway speed, 18 km keeps a report within roughly ten minutes of the moment you actually crossed, which is close enough for the number to still mean something.
What a "wait time" actually means
This one is worth thirty seconds of your attention, because it's the single biggest source of bad data on any site like ours.
A wait time is the total time from joining the back of the queue until you had passed to the other side.
It is not "I've been sitting here 45 minutes so far." That feels like a smaller version of the same thing — but it isn't the same thing at all. A partial wait and a total wait are simply different quantities, and quietly mixing them together drags every average on the site in the same direction: too low. Which is exactly the direction that hurts, because it sends people to a crossing promising an hour and delivers three.
So we ask for the whole journey through, every single time. And if you use the timer, you don't have to think about it — the arrival tap and the crossed tap define it for you.
What you get out of it
Everything on CustomsWait is built out of these reports, so making them better makes the whole site better:
- A current wait you can act on. Choose a crossing, decide when to set off, or pull over for a coffee instead of joining a four-hour queue.
- Honest averages. The heatmap, the best-day-and-hour panel, "best time to arrive" — all of it is only as good as the raw numbers behind it. Feed it measured waits and it starts telling you something genuinely useful about next Saturday, not just about today.
- Less noise. Reports from people who weren't there, and half-finished waits counted as whole ones, both quietly disappear.
- It costs you seconds. Two taps while you're sitting in a queue with nothing else to do.
And there's a nice symmetry to it: the ten seconds you spend reporting are paid for by the traveller who did the same an hour before you.
Your location, and what we do with it
Let's be completely straight about this, because "allow location access" deserves a plain answer.
To report a wait time, you have to let your browser share your location. Your browser will ask, once. If you say no, you can still use every other part of CustomsWait exactly as before — every crossing, every map, every wait time, no account, no permission. You just can't send a report.
One practical note: this needs a phone. Laptops and desktop computers work out where they are from wifi networks and your IP address, which is typically accurate to tens of kilometres — nowhere near precise enough to tell which side of a border you're standing on. A report from a computer will be turned down.
Here is precisely what happens to your coordinates when you do allow it:
- They are sent to us inside the request, never in the web address — a location in a URL would end up written into server logs, and that would quietly rebuild the location history this whole design exists to avoid.
- We use them to answer three questions, right there and then: how far are you from this crossing?, which side of the border are you on?, and how precise is this fix?
- Then they are thrown away. Your coordinates are never written to our database, never logged, and never shared with anyone.
What we keep alongside your report is a distance, the accuracy of the reading, and a label saying how the wait was established — measured with the timer, or typed in after crossing. That's enough to judge whether a report is trustworthy, and not nearly enough to follow anybody around.
Why we ask what you're driving
Before you start the timer we ask a one-tap question: car, van, truck or bus? It isn't a survey — it sets how far from the barrier we'll accept an arrival.
Car queues rarely run more than a few kilometres, so a car can start the timer within about 8 km. Truck queues at places like Kapitan Andreevo, Horgoš or Preševo routinely stretch for ten or twenty, so lorry drivers get 25 km, vans 10 and buses 12. If that ring were drawn too tightly, drivers wouldn't be blocked — they'd simply tap "arrived" later, once they crawled inside it, and we'd record a wait shorter than the one they actually served. Better generous than wrong.
A word on what this doesn't do
Location verification is a quality filter, not a lie detector. Somebody determined enough can still fake a position, and a local who lives near the border could in principle tap through a crossing they never made. We know. This step raises the cost of nonsense from zero to actual effort, which is worth a lot on its own — and the next piece of work, cross-checking reports against each other so one odd number can't move the picture, builds directly on top of it.
For now: if you're crossing a border this week, open CustomsWait when you join the queue and tap once. The person twenty cars behind you will be glad you did.