Queue wait
Only shown confidently when queue-tail evidence supports a border-connected queue. If verification is pending or stale, BorderKu says so instead of pretending the wait is known.
Example: None detectedBorderKu now separates Queue wait, Time to border and Road delay. They are three different signals. Read them together — not as one number.
Follow the highlight. Start with direction and status, then move through the evidence from left to right.
This is the most important change from the older guide.
Only shown confidently when queue-tail evidence supports a border-connected queue. If verification is pending or stale, BorderKu says so instead of pretending the wait is known.
Example: None detectedThe directional travel estimate to the checkpoint. This is not automatically the immigration/customs processing time.
Example: 48 min – 1 hr 17 minExtra slowdown observed on the approach road. Junctions, incidents and normal traffic can contribute to this figure.
Example: +6 min road delayUse this sequence every time you check BorderKu.
Make sure the direction matches the journey you are actually taking.
Approach clear, Building, Heavy or Refreshing gives the fast at-a-glance road state.
This is the queue-tail interpretation — not simply the road travel time.
This is the directional approach estimate. Longer values are displayed as hours + minutes.
Use this to understand how much extra slowdown is visible on the road.
Shows how much of the approach road appears affected by the current slowdown.
Fresh evidence deserves more trust than older road observations.
Confirms whether a road slowdown is actually connected continuously to the checkpoint.
High, Moderate or Reduced confidence tells you how much precision BorderKu is willing to show.
Open the corresponding Traffic Map or Details drawer when you need the full context.
The card tint and badge describe the approach-road state, not a guarantee of immigration/customs processing.
Current road evidence does not show a meaningful border-connected slowdown.
A slowdown is developing on the approach. Check delay, affected distance and queue-tail verification.
A stronger approach-road slowdown is visible. Use the evidence age and confidence before acting on the time estimate.
Evidence is too old or incomplete for BorderKu to make a confident current statement.
Freshness now controls how tightly the card speaks.
Fresh road evidence plus recent queue-tail verification can support the normal displayed planning range.
When part of the evidence is aging, BorderKu widens or softens the estimate instead of showing false precision.
If queue-tail evidence is old, a tight range should be replaced by conservative guidance such as “About …”.
If the road sample itself is stale, BorderKu suppresses the confident time estimate until new evidence arrives.
Longer travel estimates are easier to understand in normal time language.
32–58 min→32 min – 58 min48–77 min→48 min – 1 hr 17 min65–95 min→1 hr 5 min – 1 hr 35 min120 min→2 hrThe same reading method applies to every direction.
Use Queue wait for queue-tail evidence, Time to border for the approach, Road delay for road slowdown, then check freshness and confidence before making your travel decision.