Interpret a UUID
Back
Your input: 89117325-3905-8a09-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:89117325-3905-8a09-87ea-5ce32bd83b97
URI: uuid:89117325-3905-8a09-87ea-5ce32bd83b97
Microsoft GUID syntax: {89117325-3905-8A09-87EA-5CE32BD83B97}
C++ struct syntax: { 0x89117325, 0x3905, 0x8a09, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.182194839895322341678689647799072996247
As OID (Microsoft): 1.2.840.113556.1.8000.2554.35089.29477.14597.35337.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9876802061507856905.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2299622181.956664329.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.35089.29477.14597.35337.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x891173253905a0907ea5ce32bd83b97]
Custom data block1 (32 bit): [0x89117325]
Custom data block2 (16 bit): [0x3905]
Custom data block3 (12 bit): [0xa09]
Custom data block4 (14 bit): [0x07ea]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x8911] 0b1000100100010001
Milliseconds: [0x73] 451 (deviation -2ms..2ms)
Seconds: [0x25] 37
Minute of day: [0x0539] 1337 (22:16)
Day of year: [0x09a] 154 (Day=3, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-03 22:16:37'451 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing