Local and elapsed time

Local time, with its zone

Every time in a drive is the local time where you will be when you get there, followed by its zone — 14:05 MDT, say. The hour you read is the hour on the dashboard clock when you arrive, not the hour it will be back home.

A drive that stays in one time zone reads like any schedule. A drive that crosses one crosses it on the clock too: after the crossing, times are on the new clock.

Where the clock changes

The timeline marks where the clock changes, such as “Clocks go back 1H 0M”, with the two zones either side — CST → MST. It appears where the drive crosses into a zone with a different offset, and where the clocks go forward or back for summer time during the drive. On the map, a chip marks the same point.

Crossing a clock change can make a later section look earlier than the one before it. Nothing is wrong: the driving continues without a break, only the clock moves.

Elapsed time

The switch under the timeline’s strip changes every time to the time since you left, such as +02:35. Elapsed time always moves forward, even where a time zone moves the clock back, which makes it the easier way to see how long until a section. On Android, the arrival row then shows total elapsed time, including stops; its local-time display uses the destination’s clock.

On Android, clock changes appear in the hour grid’s time gutter. Stops stay fixed to their actual instant when a clock changes.

The switch applies to the drive you are looking at; the app opens drives in local time.

Which clock is which

• Your departure is set in your device’s time zone, the one the plan form shows.
• Each section is on the clock where it is.
• The arrival is on the destination’s clock.
• The radar’s time on the map is the exception: it is on your device’s clock, because it describes now, not your drive.

12-hour or 24-hour

Times are shown on a 24-hour clock unless you choose otherwise, such as 06:45 MST or 6:45 AM MST. Units, clock and language shows where to change it.