Interprete a UUID

Back

UUID: 
Your input:                      a970e623-0153-8097-87e9-5ce32bd83b96

Various notations:

URN:                             urn:uuid:a970e623-0153-8097-87e9-5ce32bd83b96
URI:                             uuid:a970e623-0153-8097-87e9-5ce32bd83b96
Microsoft GUID syntax:           {A970E623-0153-8097-87E9-5CE32BD83B96}
C++ struct syntax:               { 0xa970e623, 0x0153, 0x8097, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.225225736263411644209599115148496747414
As OID (Microsoft):              1.2.840.113556.1.8000.2554.43376.58915.339.32919.34793.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12209511627821908119.9793460995456777110
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2842748451.22249623.2280217827.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.43376.58915.339.32919.34793.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xa970e623015309707e95ce32bd83b96]
Custom data block1 (32 bit):     [0xa970e623]
Custom data block2 (16 bit):     [0x0153]
Custom data block3 (12 bit):     [0x097]
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:                  [0xa970] 0b1010100101110000
Milliseconds:                    [0xe6] 901 (deviation -2ms..2ms)
Seconds:                         [0x23] 35
Minute of day:                   [0x0153] 339 (05:38)
Day of year:                     [0x097] 151 (Day=31, 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-31 05:38:35'901 (deviation -2ms..2ms)