Interprete a UUID

Back

UUID: 
Your input:                      5495e80c-02a5-8081-87e9-5ce32bd83b96

Various notations:

URN:                             urn:uuid:5495e80c-02a5-8081-87e9-5ce32bd83b96
URI:                             uuid:5495e80c-02a5-8081-87e9-5ce32bd83b96
Microsoft GUID syntax:           {5495E80C-02A5-8081-87E9-5CE32BD83B96}
C++ struct syntax:               { 0x5495e80c, 0x02a5, 0x8081, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.112433510348439669631493601671280868246
As OID (Microsoft):              1.2.840.113556.1.8000.2554.21653.59404.677.32897.34793.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.6095032808997486721.9793460995456777110
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.1419110412.44400769.2280217827.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.21653.59404.677.32897.34793.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x5495e80c02a508107e95ce32bd83b96]
Custom data block1 (32 bit):     [0x5495e80c]
Custom data block2 (16 bit):     [0x02a5]
Custom data block3 (12 bit):     [0x081]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b96]

Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 2

Random 16 bits:                  [0x5495] 0b0101010010010101
Milliseconds:                    [0xe8] 909 (deviation -2ms..2ms)
Seconds:                         [0x0c] 12
Minute of day:                   [0x02a5] 677 (11:16)
Day of year:                     [0x081] 129 (Day=9, Month=5)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2025-05-09 11:16:12'909 (deviation -2ms..2ms)