Interpret a UUID

Back

UUID: 
Your input:                      c8d0c824-f603-8b04-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:c8d0c824-f603-8b04-87ea-5ce32bd83b97
URI:                             uuid:c8d0c824-f603-8b04-87ea-5ce32bd83b97
Microsoft GUID syntax:           {C8D0C824-F603-8B04-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xc8d0c824, 0xf603, 0x8b04, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.266929656313830595261128266550162766743
As OID (Microsoft):              1.2.840.113556.1.8000.2554.51408.51236.62979.35588.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.14470285663813208836.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3369125924.4127427332.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.51408.51236.62979.35588.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xc8d0c824f603b0407ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xc8d0c824]
Custom data block2 (16 bit):     [0xf603]
Custom data block3 (12 bit):     [0xb04]
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:                  [0xc8d0] 0b1100100011010000
Milliseconds:                    [0xc8] 784 (deviation -2ms..2ms)
Seconds:                         [0x24] 36
Minute of day:                   [0x03f6] 1014 (16:53)
Day of year:                     [0x04b] 75 (Day=16, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-03-16 16:53:36'784 (deviation -2ms..2ms)