Interpret a UUID

Back

UUID: 
Your input:                      04e6fb1d-c600-8e07-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:04e6fb1d-c600-8e07-87ea-5ce32bd83b97
URI:                             uuid:04e6fb1d-c600-8e07-87ea-5ce32bd83b97
Microsoft GUID syntax:           {04E6FB1D-C600-8E07-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x04e6fb1d, 0xc600, 0x8e07, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.6516233504308605988707285453216693143
As OID (Microsoft):              1.2.840.113556.1.8000.2554.1254.64285.50688.36359.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.353245726089711111.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.82246429.3321925127.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.1254.64285.50688.36359.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x04e6fb1dc600e0707ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x04e6fb1d]
Custom data block2 (16 bit):     [0xc600]
Custom data block3 (12 bit):     [0xe07]
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:                  [0x04e6] 0b0000010011100110
Milliseconds:                    [0xfb] 983 (deviation -2ms..2ms)
Seconds:                         [0x1d] 29
Minute of day:                   [0x00c6] 198 (03:17)
Day of year:                     [0x07e] 126 (Day=6, Month=5)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-05-06 03:17:29'983 (deviation -2ms..2ms)