Overview

Our system support two types of overspeed monitoring:

1. Device Speed Overspeed – based on raw speed data directly from the GPS device.
2. Software-Based Overspeed – based on speed thresholds configured in the software, with additional logic to reduce false positives.
   

3. Road Overspeed Limit – Triggered when the vehicle’s speed exceeds the posted speed limit of the road segment (from map data).
   

1. Device Speed Overspeed

• Uses the vehicle’s reported speed from the tracking device.

• As soon as the reported speed exceeds the configured threshold, an overspeed event is triggered and sent to the server.

• Pros: Instant detection, no tolerance.

• Cons: May generate false positives due to GPS fluctuations or temporary spikes.

2. Software-Based Overspeed

• You set a speed limit in the tracking system (e.g. 80 km/h).
• The system waits for speeds above that limit to show up several times before sending an alert. The platform is capable of creating software overspeeding events, if you would like to use this feature, set a speed limit as shown below, the platform will monitor each message from the tracker and generate events when the speeding starts and stops, including a summary of the overspeeding episode, it is advisable to set it slightly higher than needed i.e. if you want the speed limit to be 80 and want to allow for 10% overspeeding allowance, please set this to 88 to avoid seeing excessive overspeed events.
• This “overspeeding episode” helps avoid triggering alerts for brief speed bursts — so reports are cleaner and more reliable.

Pros:

• Reduces false positives caused by brief or minor speed spikes.
  

• Provides smoother, more accurate reporting.
  

Cons:

• Detection is slightly delayed compared to device speed overspeed.

3. Road Overspeed Limit

• Trigger: Compares vehicle’s current speed against the legal or posted road speed limit (from map provider data such as Google, TomTom, or OpenStreetMap).
• Logic: An event is triggered if the vehicle speed > road’s maximum allowed speed.
• Pros: Provides context-aware alerts — e.g., 70 km/h may be fine on a highway but flagged as overspeed in a 50 km/h zone.

• Cons:

  • Accuracy depends on the quality of the road speed data.
  • Not all regions have fully up-to-date or accurate road speed limit data.
  • Requires mapping provider integration.

Comparison Table — What’s the Difference?​

An Important Note on Hardware Support

Not all GPS tracking devices support device speed-based overspeed. It depends on the hardware manufacturer and model:

• Teltonika devices do support speed-triggered overspeed alerts in many tracker models. wiki.teltonika-gps.com
• Concox (for example their GT06 series or OBD trackers) support overspeed alarms based on speed thresholds, iconcox.com
• Before setting up device-speed overspeed as your main alert method, check your tracker’s manual or settings to confirm whether it supports instant device-speed overspeed or only averaged/threshold overspeed.

• GPS speed spikes or signal glitches are common, especially in urban or hilly terrain. If the system flagged every little spike, you’d get lots of false overspeed alerts.
• By allowing upto a maximum speeding episode records over the threshold before flagging an event, we reduce “noise” and improve alert quality without losing meaningful overspeed detection.

Tips for Best Use

• If your priority is real-time monitoring and driver behavior enforcement, combine both types: enable device-speed overspeed for immediate alerts and software-based overspeed for reporting and trend tracking.
• If your main goal is fleet safety oversight, compliance reports, or reducing false alarms, rely primarily on software-based overspeed settings.
• Always check the specific GPS tracker’s documentation to know which overspeed method it supports — deploying the wrong one could lead to missed alerts or too many false alerts.