Interprete a UUID

Back

Your input:                      97e3f405-4c01-8512-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:97e3f405-4c01-8512-87e9-5ce32bd83b97
URI:                             uuid:97e3f405-4c01-8512-87e9-5ce32bd83b97
Microsoft GUID syntax:           {97E3F405-4C01-8512-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x97e3f405, 0x4c01, 0x8512, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.201897028078016504347875335703398726551
As OID (Microsoft):              1.2.840.113556.1.8000.2554.38883.62469.19457.34066.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.10944859823027619090.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2548298757.1275168018.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.38883.62469.19457.34066.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x97e3f4054c0151207e95ce32bd83b97]
Custom data block1 (32 bit):     [0x97e3f405]
Custom data block2 (16 bit):     [0x4c01]
Custom data block3 (12 bit):     [0x512]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3

Random 16 bits:                  [0x97e3] 0b1001011111100011
Milliseconds:                    [0xf4] 956 (deviation -2ms..2ms)
Seconds:                         [0x05] 5
Minute of day:                   [0x014c] 332 (05:31)
Day of year:                     [0x125] 293 (Day=20, Month=10)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-10-20 05:31:05'956 (deviation -2ms..2ms)