Interprete a UUID

Back

UUID: 
Your input:                      1e5ca323-0705-8b0f-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:1e5ca323-0705-8b0f-87e9-5ce32bd83b97
URI:                             uuid:1e5ca323-0705-8b0f-87e9-5ce32bd83b97
Microsoft GUID syntax:           {1E5CA323-0705-8B0F-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x1e5ca323, 0x0705, 0x8b0f, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.40357839992456859943753166255428221847
As OID (Microsoft):              1.2.840.113556.1.8000.2554.7772.41763.1797.35599.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.2187802889832205071.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.509387555.117803791.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.7772.41763.1797.35599.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x1e5ca3230705b0f07e95ce32bd83b97]
Custom data block1 (32 bit):     [0x1e5ca323]
Custom data block2 (16 bit):     [0x0705]
Custom data block3 (12 bit):     [0xb0f]
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:                  [0x1e5c] 0b0001111001011100
Milliseconds:                    [0xa3] 639 (deviation -2ms..2ms)
Seconds:                         [0x23] 35
Minute of day:                   [0x0507] 1287 (21:26)
Day of year:                     [0x0fb] 251 (Day=8, Month=9)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-09-08 21:26:35'639 (deviation -2ms..2ms)