Interpret a UUID

Back

UUID: 
Your input:                      8e39b936-9c01-8702-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:8e39b936-9c01-8702-87ea-5ce32bd83b97
URI:                             uuid:8e39b936-9c01-8702-87ea-5ce32bd83b97
Microsoft GUID syntax:           {8E39B936-9C01-8702-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x8e39b936, 0x9c01, 0x8702, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.189050092894773498480581364513632697239
As OID (Microsoft):              1.2.840.113556.1.8000.2554.36409.47414.39937.34562.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.10248426071254992642.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2386147638.2617345794.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.36409.47414.39937.34562.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x8e39b9369c0170207ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x8e39b936]
Custom data block2 (16 bit):     [0x9c01]
Custom data block3 (12 bit):     [0x702]
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:                  [0x8e39] 0b1000111000111001
Milliseconds:                    [0xb9] 725 (deviation -2ms..2ms)
Seconds:                         [0x36] 54
Minute of day:                   [0x019c] 412 (06:51)
Day of year:                     [0x027] 39 (Day=8, Month=2)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-02-08 06:51:54'725 (deviation -2ms..2ms)