Interpret a UUID

Back

Your input:                      83cf7f17-a003-8c07-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:83cf7f17-a003-8c07-87ea-5ce32bd83b97
URI:                             uuid:83cf7f17-a003-8c07-87ea-5ce32bd83b97
Microsoft GUID syntax:           {83CF7F17-A003-8C07-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x83cf7f17, 0xa003, 0x8c07, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.175206250635329979878830751209517235095
As OID (Microsoft):              1.2.840.113556.1.8000.2554.33743.32535.40963.35847.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.9497949878593227783.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2211413783.2684587015.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.33743.32535.40963.35847.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x83cf7f17a003c0707ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x83cf7f17]
Custom data block2 (16 bit):     [0xa003]
Custom data block3 (12 bit):     [0xc07]
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:                  [0x83cf] 0b1000001111001111
Milliseconds:                    [0x7f] 498 (deviation -2ms..2ms)
Seconds:                         [0x17] 23
Minute of day:                   [0x03a0] 928 (15:27)
Day of year:                     [0x07c] 124 (Day=4, 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-04 15:27:23'498 (deviation -2ms..2ms)