Issues with reports and positions

At 6.6 version we face some issues, the devices position are wrong at the map, the real position is far far away. Also at the reports for the trips we have minus distance or the speed is 650km/h.
when we select a position on the trip, it doesn't show the full route, but only a flag without any route..
i checked the logs some devices have time outs, or others are sending older positions from 30 minutes to a whole day.
Any ideas to resolve it?

2025-05-26 18:13:45  INFO: [Td8ca3053: gps103 < 195.226.133.37] imei:869220041750179,tracker,250526181343,100%,F,181343.000,A,3520.55265,N,02508.18686,E,17.79,248.80;
2025-05-26 18:13:45  INFO: [Td8ca3053] id: 869220041750179, time: 2025-05-26 18:13:43, lat: 35.34254, lon: 25.13645, speed: 17.8, course: 248.8
2025-05-26 18:13:45  INFO: [T43508016: gps103 < 5.35.166.172] imei:869220041988548,tracker,250526181344,75%,F,181344.000,A,3937.04639,N,01953.96427,E,14.96,303.03;
2025-05-26 18:13:46  INFO: [T43508016] id: 869220041988548, time: 2025-05-26 18:13:44, lat: 39.61744, lon: 19.89940, speed: 15.0, course: 303.0
2025-05-26 18:13:46  INFO: [T275abd1d: gps103 < 195.226.133.60] imei:869220041749718,tracker,250526181344,100%,F,181344.000,A,3522.27966,N,02432.40243,E,0.00,296.61;
2025-05-26 18:13:46  INFO: [T275abd1d] id: 869220041749718, time: 2025-05-26 18:13:44, lat: 35.37133, lon: 24.54004, course: 296.6
2025-05-26 18:13:46  INFO: [T80c6b1f6: gps103 < 195.226.133.59] imei:868307060513587,tracker,250526040135,100%,F,040135.000,A,3530.92011,N,02401.32770,E,3.98,212.80,,1,0,,,;
2025-05-26 18:13:46  INFO: [T80c6b1f6] id: 868307060513587, time: 2025-05-26 04:01:35, lat: 35.51534, lon: 24.02213, speed: 4.0, course: 212.8
2025-05-26 18:13:46  INFO: [T14c24a2c: gps103 < 195.226.133.45] imei:869220041747241,tracker,250526181344,100%,F,181344.000,A,3530.76433,N,02358.69953,E,0.00,51.67;
2025-05-26 18:13:46  INFO: [T14c24a2c] id: 869220041747241, time: 2025-05-26 18:13:44, lat: 35.51274, lon: 23.97833, course: 51.7
2025-05-26 18:13:46  INFO: [T1261e419: gps103 < 195.226.133.61] imei:869220041988860,tracker,250526130452,100%,F,130452.000,A,3858.42836,N,02045.33858,E,,;
2025-05-26 18:13:46  INFO: [T1261e419] id: 869220041988860, time: 2025-05-26 13:04:52, lat: 38.97381, lon: 20.75564, course: 0.0
2025-05-26 18:13:46  INFO: [Tcc13c1a4: gps103 < 5.35.166.166] imei:868307060515947,tracker,250526160826,100%,F,160826.000,A,3653.58128,N,02717.33540,E,15.74,92.93,,1,0,,,;
2025-05-26 18:13:46  INFO: [Tcc13c1a4] id: 868307060515947, time: 2025-05-26 16:08:26, lat: 36.89302, lon: 27.28892, speed: 15.7, course: 92.9
2025-05-26 18:13:46  INFO: [Te46095bf: gps103 < 195.226.133.61] imei:869220041539341,acc off,250526181344,,F,181344.000,A,3937.68937,N,01953.80689,E,0.00,201.83;
2025-05-26 18:13:46  INFO: [Te46095bf] id: 869220041539341, time: 2025-05-26 18:13:44, lat: 39.62816, lon: 19.89678, course: 201.8
2025-05-26 18:13:46  INFO: [T63266672: gps103 < 195.226.133.45] imei:869220041628938,tracker,250526181344,,F,181344.000,A,3520.23870,N,02503.89357,E,0.00,309.36;
2025-05-26 18:13:46  INFO: [T63266672] id: 869220041628938, time: 2025-05-26 18:13:44, lat: 35.33731, lon: 25.06489, course: 309.4
2025-05-26 18:13:46  INFO: [T673a650c] connected
2025-05-26 18:13:46  INFO: [T4b740363: gps103 < 5.35.166.166] imei:869220041988043,tracker,250526181344,100%,F,181344.000,A,3930.93274,N,01951.05445,E,0.43,351.56;
2025-05-26 18:13:46  INFO: [T4b740363] id: 869220041988043, time: 2025-05-26 18:13:44, lat: 39.51555, lon: 19.85091, speed: 0.4, course: 351.6
2025-05-26 18:13:46  INFO: [T673a650c: gps103 < 195.226.133.37] ##,imei:869220041622725,A;
2025-05-26 18:13:46  INFO: Event id: 869220041622725, time: 2025-05-26 18:13:46, type: deviceOnline, notifications: 0
2025-05-26 18:13:46  INFO: [T673a650c: gps103 > 195.226.133.37] LOAD
2025-05-26 18:13:46  INFO: [T955b63f7: gps103 < 195.226.133.44] imei:869220041989892,tracker,250526181344,5%,F,181344.000,A,3530.86313,N,02346.78195,E,6.87,187.85;
2025-05-26 18:13:46  INFO: [T955b63f7] id: 869220041989892, time: 2025-05-26 18:13:44, lat: 35.51439, lon: 23.77970, speed: 6.9, course: 187.9
2025-05-26 18:13:46  INFO: [Taf9a00f8: gps103 < 195.226.133.43] imei:869220041539143,tracker,250526181345,,F,181345.000,A,3927.43898,N,01952.18818,E,0.00,68.47;
2025-05-26 18:13:46  INFO: [Taf9a00f8] id: 869220041539143, time: 2025-05-26 18:13:45, lat: 39.45732, lon: 19.86980, course: 68.5
2025-05-26 18:13:46  INFO: [Tc4fe5ef1: gps103 < 195.226.133.38] imei:869220041993035,tracker,250526181345,75%,F,181345.000,A,3947.26905,N,01948.21876,E,21.91,248.29;
2025-05-26 18:13:46  INFO: [Tc4fe5ef1] id: 869220041993035, time: 2025-05-26 18:13:45, lat: 39.78782, lon: 19.80365, speed: 21.9, course: 248.3
2025-05-26 18:13:46  INFO: [T05867842: gps103 < 5.35.166.167] imei:869220041750427,tracker,250526181345,100%,F,181345.000,A,3520.35885,N,02508.63400,E,0.00,197.77;
2025-05-26 18:13:46  INFO: [T05867842] id: 869220041750427, time: 2025-05-26 18:13:45, lat: 35.33931, lon: 25.14390, course: 197.8
2025-05-26 18:13:46  INFO: [Tae576570: gps103 < 195.226.133.37] imei:868307060515913,tracker,250526161627,100%,F,161627.000,A,3653.46607,N,02717.97988,E,0.00,0.00,,1,0,,,;
2025-05-26 18:13:46  INFO: [Tae576570] id: 868307060515913, time: 2025-05-26 16:16:27, lat: 36.89110, lon: 27.29966, course: 0.0
2025-05-26 18:13:46  INFO: [T54a8e19c: gps103 < 5.35.166.172] 869220041992771;
2025-05-26 18:13:46  INFO: [T54a8e19c: gps103 > 5.35.166.172] ON

Negative distance usually means that your device reports data not in chronological order. Large jumps could also probably be because of that.

so probably the issues are from the devices and not the traccar?
Any clues what to investigate? maybe wrong timezone on devices?

You should probably check the raw data to see what the device is sending. But I don't think it's a time zone issue.

I checked the logs from yesterday and i find some device to report data with wrong timestamp
this is a little part from them
868307060513587 2025-05-26 04:01:35 - 14 hours back
869220041988860 2025-05-26 13:04:5. ~5 hours back
868307060515947 2025-05-26 16:08:26 ~2 hours back
868307060515913. 2025-05-26 16:16:27 -2 hours back

What else i need to check on the raw data?
So is it an issue with the device (coban 311c) or something else?
At the same server others devices works and reports correct.

Actually i saw this in a device

The Fixtime shouldn't be the same ?

What you have to check is if fix time order is different from server time order.