QUEUE CARD GUIDE · UPDATED FOR V7.7.20

How to read the new Queue Cards

Start with Estimated full crossing, then use the live road evidence underneath to understand what is driving that planning range.

← Back to Live Queues

Anatomy of the current Live Queue card

Read it from top to bottom. The card separates the planning estimate from the road evidence that supports it.

Sungai TujohBrunei → Miri

● Low delay

Little approach delay measured

Current approach-road evidence shows little extra road delay. This road assessment is separate from checkpoint processing.

Estimated full crossing 12–22 min Planning range from the monitored approach through the directional corridor exit.

Drive to first checkpoint 2 min From BorderKu's fixed monitoring point

Approach delay0 minExtra road slowdown

Verified queue tailNone verifiedNo connected tail confirmed

Road sample8 min ago

Queue-tailJust checked

The four values travellers must not mix up

Each figure answers a different question. Adding them together again can double-count the same road delay.

USE FOR THE WHOLE CROSSING

Estimated full crossing

A directional planning range from BorderKu's monitored approach through the corridor exit. It combines current directional road travel with BorderKu's modelled checkpoint-processing component when enough current evidence exists.

Example: 12–22 min

USE FOR THE ROAD TO THE FIRST POST

Drive to first checkpoint

The current traffic-aware drive from BorderKu's fixed monitoring point to the first checkpoint.

Example: 2 min

SUPPORTING ROAD SIGNAL

Approach delay

The extra slowdown on the approach road. This delay is already reflected in traffic-aware road travel, so do not add it again to the full crossing estimate.

Example: 4 min

VERIFIED QUEUE EVIDENCE

Verified queue tail

The distance of congestion verified as continuously connected to the checkpoint. BorderKu does not simply convert this distance into extra minutes and add it again.

Example: 800 m verified

Remember: Estimated full crossing ≠ Drive to first checkpoint ≠ Approach delay ≠ Verified queue tail.

Read the card in this order

This sequence keeps the planning estimate and the evidence underneath it in the correct context.

Choose Outbound or Return

Make sure the direction matches the journey you are actually taking.

Check the road-status badge

Low delay, Slowdown, Heavy or Unavailable describes the current approach-road state.

Read Estimated full crossing

This is the end-to-end planning range to use first when BorderKu has enough current evidence.

Read Drive to first checkpoint

This tells you how long the monitored road approach currently takes.

Use Approach delay as context

It explains how much extra road slowdown is contributing to the drive.

Check Verified queue tail

Use it to see whether congestion is actually connected to the checkpoint.

Check freshness

Road-sample age and queue-tail verification age tell you how current the evidence is.

Open Map or Details

Use the Traffic Map and detail drawer when you need the evidence behind the summary card.

What “Estimated full crossing” means

It is broader than road delay, but it is still a BorderKu planning estimate rather than an official immigration or customs measurement.

Current directional road travelMeasured road componentTraffic-aware travel through BorderKu's monitored directional corridor.

Checkpoint-processing componentModelled componentDerived from BorderKu's directional estimator, not from direct access to immigration counter systems.

Estimated full crossingPlanning rangeShown only when the current evidence is sufficient.

Do not add Approach delay or Queue tail again. Road congestion is already represented in the traffic-aware road component, while verified queue-tail distance is supporting evidence.

When BorderKu withholds the full-crossing range

“Not enough current evidence” is intentional. It is safer than publishing a precise-looking number that the current data cannot support.

ROAD EVIDENCE

Road sample is stale

The live road component needs refreshing before BorderKu should publish an end-to-end range.

ROUTE QUALITY

Route needs checking

If the returned road route is implausible or takes a large detour, the card suppresses the affected time values.

MODEL INPUT

Processing component unavailable

BorderKu does not invent a checkpoint-processing number when the directional model does not provide a usable component.

EVIDENCE CONSISTENCY

Signals materially conflict

If current road evidence and queue-tail evidence do not safely support the same picture, precision is reduced or withheld.

The compact Traffic Map cards use the same logic

The smaller cards show the same directional contract in a more compact layout.

LabuTemburong → Lawas

Full crossing18–43 min

Slowdown

To checkpoint6 min

Delay3 min

Queue tailNone verified

Sindumin / MerapokSarawak → Sabah

Full crossingNot enough evidence

Unavailable

To checkpoint—

Delay—

Queue tailNone verified

Selecting a different checkpoint or switching Outbound / Return changes the exact direction used by every displayed metric.

Three examples

Use the whole card, not just the largest number.

EXAMPLE A

Low delay

Full crossing: 12–22 min

Drive 2 min · Delay 0 min · No verified queue tail

The road looks clear, but the full-crossing range still includes a modelled checkpoint-processing component.

EXAMPLE B

Slowdown

Full crossing: 28 min–1 hr

Drive 6 min · Delay 4 min · No verified queue tail

The 4-minute road delay helps explain the drive. Do not add those 4 minutes again to the displayed full-crossing range.

EXAMPLE C

Unavailable

Full crossing: Not enough current evidence

Drive — · Delay — · Queue tail not confirmed

BorderKu is deliberately withholding precision until the road route or evidence becomes usable again.

THE SIMPLE VERSION

Read the estimate, then read the evidence.

Use Estimated full crossing for the end-to-end planning range. Use Drive to first checkpoint and Approach delay for the road. Use Verified queue tail to understand connected congestion. Then check freshness before you travel.

Check live queues →Open Traffic Map →