We look at the road.
BorderKu checks traffic approaching the selected checkpoint and direction.
ACCURACY LAB
How BorderKu estimates your border wait.
BorderKu helps travellers plan better. It does not receive an official live border waiting-time feed. Instead, it combines road conditions, recent border behaviour, direction-specific patterns and later checks.
- Road traffic is one signal. It is not the whole border story.
- Traveller reports can add context, but they are not official measurements.
- BorderKu checks itself later by comparing earlier estimates with what happened next.
Roadapproach traffic
→
Borderextra delay estimated
→
Resultplanning estimate
SIMPLE EXPLANATION
What BorderKu does, step by step
Plain English. No jargon. Just the main idea.
We estimate the part Google cannot see.
A calm road does not always mean a fast border. BorderKu estimates extra checkpoint delay from recent same-route behaviour.
We compare with recent patterns.
Time of day, return-home traffic, holidays and recent behaviour help shape the estimate.
We show a planning estimate.
Road delay plus estimated checkpoint delay becomes the BorderKu number shown to travellers.
We check ourselves later.
BorderKu compares earlier estimates with what happened 30, 60 or 120 minutes later.
TRANSPARENCY
What BorderKu can and cannot directly see
This is the clearest way to explain the system honestly.
What BorderKu can see
- Approach-road conditions before the checkpoint
- Travel direction for each border
- Recent same-direction patterns
- Time-of-day and operating context
- Later observed outcomes used for validation
- Traveller/community reports as extra context
What BorderKu cannot directly see
- Exact live immigration processing time
- How many counters are open right now
- Exact cars inside the checkpoint
- Official queue-clearing time from border systems
- Unexpected manual checks before they happen
Important:
BorderKu does not receive an official live border waiting-time feed.
It provides a planning estimate, not an official border measurement.
VISUAL FLOW
How the estimate is built
A quick summary of the method.
Input 1
Live road conditions
What the approach road is doing now.
→
Input 2
Recent same-route behaviour
What this border and direction have been doing recently.
→
Estimate
Estimated checkpoint delay
The extra border delay road traffic alone cannot explain.
→
Result
BorderKu wait estimate
The number shown to travellers.
LATEST SNAPSHOT
How the Accuracy Lab reports results
Keep public measures simple and useful.
Technical name: Mean Absolute Error (MAE).
Recommended metric for travellers.
Useful for “Should I go now?” guidance.
Last updated: 27 Aug 2026, 01:43 UTC. Update these metric values with the latest live Accuracy Lab reporting when available.