Group Guntimes

Updated September 23, 2026 08:54

The Group Guntimes panel lets you watch, from a single place and in real time, every guntime the timing devices of one export group are recording, telling you which device read each one.

This article applies to the Group Guntimes panel, available from Devices › Dashboard in the Companies UI.

ℹ️ Note: if you only need the guntimes of one specific device, see the Device Exports article (where a single device sends its readings and how to download them) or Public Device Page (sharing one device's guntimes with someone who has no account).

What are group guntimes?
Where to find it
What you see in the panel
- Panel header
- Guntimes table
Times: your clock or UTC
Live readings
Filtering by device
Loading more, and refreshing
If nothing shows up
Related guides

1. What are group guntimes?

The Devices Dashboard already groups its cards by export: every timing device sending its readings to the same destination, under the same identifier, sits under one group heading.

Group Guntimes is the panel that shows the guntimes of all the timing devices in that group at once, newest first, telling you which device read each one.

It answers the question you actually have during an event — is this whole setup seeing tags? — without opening device by device.

ℹ️ Note: a guntime is a start-type read. It is not every tag read a timing device takes: a device reads the same tag many times as it passes, and only the read that counts as the athlete's pass arrives here.

2. Where to find it

Open Devices › Dashboard. Every group heading carries a Guntimes button next to the group name and its device count. Press it and a panel slides in from the side.

Pressing the button does not fold the group.

ℹ️ Note: if a group has no button, that group cannot be identified to the service on its own — usually the pool of devices with no consumer assigned. That is expected, not a fault.

3. What you see in the panel

3.1. Panel header

At the top of the panel:

The group, how many timing devices feed it, and the period being queried. You do not choose that period: it comes from the group's own exports and runs up to now.
Two badges, and they do not mean the same thing. This is the one part of the panel worth reading twice:
- Newest page / History — where you are in the history. It says nothing about the connection.
- Live feed connected / connecting — the realtime connection itself.
They move independently. You can be on the newest page with the feed down, or connected while reading page five of history.
Latest received — the most recent reading to arrive live, shown above the table with its wave time, when the cloud received it, and which timing device read it. Until the first one arrives it reads "Connected and waiting — no detection has arrived yet."

3.2. Guntimes table

Then the table, with three columns:

Column	Description
Wave time	When the athlete passed.
Received in the cloud	How long ago the cloud got it. Hover for the exact timestamp.
Device	Which timing device read it.

4. Times: your clock or UTC

A Hours toggle at the top switches the whole panel between Local time and UTC. It opens on your local time.

Everything on the panel follows that one setting — the rows, the period line at the top, and the Latest received block. You will never see two clocks mixed on screen.

5. Live readings

While you are on the newest page, new guntimes appear on their own as the timing devices report them. You do not need to refresh.

⚠️ Important: only the newest page is live. As soon as you load older readings the panel is showing history, and the badge changes to say so rather than leaving a "newest" claim standing.

6. Filtering by device

Filter by device narrows the list to the timing devices you pick.

It filters what is already on screen — it fetches nothing, so it is instant. Clearing it brings everything back.

ℹ️ Note: a device shown as a code instead of a name is displaying its identifier. That happens with bubbles and with devices deleted since they exported, and their readings are just as real as any other.

7. Loading more, and refreshing

Load more, at the bottom of the list, brings the next, older block. Underneath you will see how many you have loaded, and it tells you when there is nothing left in the window.
Refresh starts again from the newest page and discards what you had loaded. That is what you want when the question is what is coming in right now?

⚠️ Important: older readings are never pulled automatically, and that is deliberate. Each query can sweep weeks of history and has a real cost, so everything that fetches is a button you press. The "x minutes ago" column does keep ticking on its own — that is worked out in your browser and fetches nothing.

8. If nothing shows up

The panel distinguishes four situations on purpose, because they send you to different places:

Message	What it means
"This group hasn't started collecting yet"	Its exports are scheduled to begin later. Nothing is broken.
"No guntimes have been recorded in this group's export window"	The group has been running and has read nothing. This is the one that deserves attention: go and look at the timing devices.
"No guntimes match the selected devices"	There is data; your filter is hiding it. Clear the filter.
"No export matches this consumer and id"	Nothing is exporting under that configuration. Check the group still has its exports set up.

❌ Attention: if loading more fails, what is already on screen stays there. A notice appears above the list with a Start over button.

9. Related guides

Devices Dashboard — the live wall of status cards these groups come from.
Device Exports — where a single timing device sends its readings, and how to download them.
Public Device Page — sharing one device's guntimes with someone who has no account.

With this panel open during the event you have, on a single screen, the confirmation that every timing device in the group is reading tags and which device recorded each guntime.