Interprete a UUID

Back

UUID: 
Your input:                      ab8d212b-01c7-8058-87e9-5ce32bd83b96

Various notations:

URN:                             urn:uuid:ab8d212b-01c7-8058-87e9-5ce32bd83b96
URI:                             uuid:ab8d212b-01c7-8058-87e9-5ce32bd83b96
Microsoft GUID syntax:           {AB8D212B-01C7-8058-87E9-5CE32BD83B96}
C++ struct syntax:               { 0xab8d212b, 0x01c7, 0x8058, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.228030773863152600924605717143017241494
As OID (Microsoft):              1.2.840.113556.1.8000.2554.43917.8491.455.32856.34793.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12361573020799041624.9793460995456777110
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2878153003.29851736.2280217827.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.43917.8491.455.32856.34793.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xab8d212b01c705807e95ce32bd83b96]
Custom data block1 (32 bit):     [0xab8d212b]
Custom data block2 (16 bit):     [0x01c7]
Custom data block3 (12 bit):     [0x058]
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:                  [0xab8d] 0b1010101110001101
Milliseconds:                    [0x21] 129 (deviation -2ms..2ms)
Seconds:                         [0x2b] 43
Minute of day:                   [0x01c7] 455 (07:34)
Day of year:                     [0x058] 88 (Day=29, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2025-03-29 07:34:43'129 (deviation -2ms..2ms)