Hi Team,
I'm querying trips using Trips API for deviceId: 5.

When I use the following range:

from: 2025-07-01T00:00:00Z
to: 2025-07-01T23:59:00Z

I get the following data for my first trip:

• startPositionId: 13105303
• endPositionId: 13105787
• startLat: x.169125999999999
• startLon: x.511636

However, when I keep the same from date and extend the to date to: 2025-07-02T23:59:00Z

The result shifts, and I now get:

• startPositionId: 13105338
• endPositionId: 13105801
• startLat: x.16697
• startLon: x.506946

---

Question

Why does extending the to range cause Traccar to change, even though the from timestamp is identical?

Thanks

You forgot to mention the version of Traccar, but most likely this is related to fast reports.

Thanks for the clarification.

I'm using Traccar version 6.6.

Since I’ll be generating monthly reports, I’m considering increasing report.fastThreshold to ensure better accuracy across longer date ranges.

Could you share what kind of performance impact I might expect when doing this — and how best to balance accuracy vs. performance for such use cases?

Thanks again!

The performance is drastically different.

ok thanks.