Interprete a UUID

Back

Your input:                      1daf2e39-5a01-800d-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:1daf2e39-5a01-800d-87e9-5ce32bd83b97
URI:                             uuid:1daf2e39-5a01-800d-87e9-5ce32bd83b97
Microsoft GUID syntax:           {1DAF2E39-5A01-800D-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x1daf2e39, 0x5a01, 0x800d, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.39457201362708650961361598093981137815
As OID (Microsoft):              1.2.840.113556.1.8000.2554.7599.11833.23041.32781.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.2138979171882336269.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.498019897.1510047757.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.7599.11833.23041.32781.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x1daf2e395a0100d07e95ce32bd83b97]
Custom data block1 (32 bit):     [0x1daf2e39]
Custom data block2 (16 bit):     [0x5a01]
Custom data block3 (12 bit):     [0x00d]
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:                  [0x1daf] 0b0001110110101111
Milliseconds:                    [0x2e] 180 (deviation -2ms..2ms)
Seconds:                         [0x39] 57
Minute of day:                   [0x015a] 346 (05:45)
Day of year:                     [0x0d0] 208 (Day=27, Month=7)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-07-27 05:45:57'180 (deviation -2ms..2ms)