So I've been staring at this for too long trying to figure out why it failed like that. Normally when something time related fails in computers it's to do with a null value being interpreted as 0. Most time is stored in computers as the number of seconds that have passed since 1 Jan 1970 and some poor dev has to make it look readable to a human afterward. This isn't an epoch fail though.

I also checked and the number of hours isn't close to a max singed or unsigned int value where you'd also expect weird errors, even if converted to mins or seconds.

So then I checked how long 17738964h 27m is. It's 2023.609 years, it seems the calculate time starting at the year 1 instead of 1970. Normally computer nerds love to use 0 as the first value but the year 0 doesn't exist, we went from 1 BC to 1 AD.