Interpret a UUID

Back

UUID: 
Your input:                      19eddd3a-4600-8204-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:19eddd3a-4600-8204-87ea-5ce32bd83b97
URI:                             uuid:19eddd3a-4600-8204-87ea-5ce32bd83b97
Microsoft GUID syntax:           {19EDDD3A-4600-8204-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x19eddd3a, 0x4600, 0x8204, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.34465761279516048495769823535001254807
As OID (Microsoft):              1.2.840.113556.1.8000.2554.6637.56634.17920.33284.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.1868392662780903940.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.435019066.1174438404.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.6637.56634.17920.33284.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x19eddd3a460020407ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x19eddd3a]
Custom data block2 (16 bit):     [0x4600]
Custom data block3 (12 bit):     [0x204]
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:                  [0x19ed] 0b0001100111101101
Milliseconds:                    [0xdd] 866 (deviation -2ms..2ms)
Seconds:                         [0x3a] 58
Minute of day:                   [0x0046] 70 (01:09)
Day of year:                     [0x042] 66 (Day=7, 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-07 01:09:58'866 (deviation -2ms..2ms)