Engine Hours Mismatch

Yes, on the server. Check route report for the same period and see if you have hours there for all records.

Okay, thanks for the suggestion.
I have checked the Route report for the period and hours are there. They start from none (as it was a new device add) then they start accumulating up to the time that ignition was switched off. I have copied the report for your checking and kind guidance if something is wrong, pasted below:

    Device	Fix Time	Hours	Ignition
gt test	07/04/2024 1:11:47 PM	  ⚙	No
gt test	07/04/2024 1:11:47 PM	  ⚙	No
gt test	07/04/2024 1:11:57 PM	  ⚙	No
gt test	07/04/2024 1:12:07 PM	  ⚙	No
gt test	07/04/2024 1:12:17 PM	  ⚙	No
gt test	07/04/2024 1:12:27 PM	  ⚙	No
gt test	07/04/2024 1:12:27 PM	  ⚙	No
gt test	07/04/2024 1:12:33 PM	  ⚙	Yes
gt test	07/04/2024 1:12:37 PM	0 h 0 m  ⚙	Yes
...
gt test	07/04/2024 1:24:37 PM	0 h 12 m  ⚙	Yes
gt test	07/04/2024 1:24:47 PM	0 h 12 m  ⚙	No
gt test	07/04/2024 1:24:57 PM	0 h 12 m  ⚙	No

There's your answer. The start point doesn't have any hours. As I said, that was likely the reason and it is.

Thanks Anton, i understand now, so since the device now has 12 mins on hours, if we do another test and simulate ignition, that should give us hours for that new period right? (since the start point will have 12 minutes)

I think you can disregard the above. We tested by pulling a custom report from the time that hours were now present and they are now visible, so we will run a test tomorrow and pull hours for the day.
Thank you so much for your help, it is highly appreciated.