Tracking interval, runtime & battery

Choose a send interval that reaches your target runtime on GL3xx trackers.

The send interval (also called report interval or refresh rate) sets how often a GPS tracker transmits its position. A shorter interval gives a smoother live picture but drains the battery faster. This page helps you pick an interval that reaches your target runtime.

The values below apply to the Queclink GL3xx series (GL320, GL310, GL300).

Interval → runtime

Report- & Send Interval [sec]	GL320, GL310 [hr]	GL300 [hr]
5	13	8
10	19	13
30	35	26
60	60	42
120	70	50

These figures assume the autonomy settings from Configuring trackers for increased autonomy. Real runtime also depends on:

• settings of the GPS tracker

• network coverage

• visibility of the GPS device for satellites — How is the device stowed?

• constitution of the battery

• temperature

The 60-second threshold

Below a 60 s interval, the GL3xx keeps the GPS module switched on continuously. At 60 s or slower, the module sleeps between fixes.

Because of this, a 30 s and a 59 s interval drain the battery at roughly the same rate — there is no power saving between them. The first real efficiency gain comes at 60 s, which is the sweet spot: it doubles the runtime of a 30 s interval (35 h → 60 h on a GL320/GL310) while still updating every minute. Going below 60 s costs battery without moving you into a higher runtime tier.

Battery drain per hour

For a GL3xx in the RACE profile:

• 10 s interval: about 5 % battery per hour.

• 60 s interval: about 2 % battery per hour.

• SLEEP profile (before/after the race): about 5–7 % per 24 hours.

With optimized autonomy settings and a 5-minute interval, a device can run for about four days and five hours (100 % → 20 %). See Configuring trackers for increased autonomy.

Choosing an interval for a target runtime

Pick the slowest interval that still gives the live experience you need, then check it clears your target runtime with margin — battery drains faster in the cold, with poor network, or on older cells.

Example: 32 h runtime.

• 60 s is the safe choice. A GL320/GL310 comfortably reaches 32 h and typically finishes with 35–40 % battery left.

• 45 s reaches 32 h in good conditions, but because it sits below the 60 s threshold it drains like a 30 s interval — closer to 24 h in rough conditions — with no meaningful benefit in the live picture. For a 32 h target, prefer 60 s.

Hybrid strategy for mixed fields: run the elite runners (short race time) at a fast interval such as 10–20 s, and keep the rest of the field at 60 s so they last the full 32 h. Alternatively, swap devices mid-race to run a low interval throughout.

See also

Configuring trackers for increased autonomySend messages