These numbers are timestamps since Windows Epoch Time which starts at January 1, 1601, counting in millisecond intervals.
From the Microsoft page How to convert date/time attributes in Active Directory to standard time format:
Active Directory stores date/time values as the number of 100-nanosecond intervals that have elapsed since the 0 hour on January 1, 1601 until the date/time that is being stored.
The above page describes the built-in
win32tm command, that can do this conversion for you. As your Office times are stored in milliseconds and this command requires nanoseconds, we need to append 4 zeroes to the end of your values to get the "full" 18-digit timestamp code:
w32tm /ntte 133355384649580000
154346 12:14:24.9580000 - 03/08/2023 13:14:24
As the full 18-digit value is using 100ns time intervals since Windows Epoch, by removing 4 digits from the end you reduce the precision down to millisecond intervals from 100ns intervals. You'll probably never notice this reduction in precision.
You can validate converting from the number you have using online converters such as LDAP, Active Directory & Filetime Timestamp Converter but again you will need to add four
0s to the end of the string to get the correct 18-digit value.