Interpret a UUID

Back

Your input:                      d40ee213-c701-8d00-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:d40ee213-c701-8d00-87ea-5ce32bd83b97
URI:                             uuid:d40ee213-c701-8d00-87ea-5ce32bd83b97
Microsoft GUID syntax:           {D40EE213-C701-8D00-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xd40ee213, 0xc701, 0x8d00, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.281873612653916557434679860479982582679
As OID (Microsoft):              1.2.840.113556.1.8000.2554.54286.57875.50945.36096.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.15280399160285695232.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3557745171.3338767616.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.54286.57875.50945.36096.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xd40ee213c701d0007ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xd40ee213]
Custom data block2 (16 bit):     [0xc701]
Custom data block3 (12 bit):     [0xd00]
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:                  [0xd40e] 0b1101010000001110
Milliseconds:                    [0xe2] 885 (deviation -2ms..2ms)
Seconds:                         [0x13] 19
Minute of day:                   [0x01c7] 455 (07:34)
Day of year:                     [0x00d] 13 (Day=13, Month=1)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-01-13 07:34:19'885 (deviation -2ms..2ms)