Interprete a UUID

Back

UUID: 
Your input:                      ab5c5a3b-f100-8712-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:ab5c5a3b-f100-8712-87e9-5ce32bd83b97
URI:                             uuid:ab5c5a3b-f100-8712-87e9-5ce32bd83b97
Microsoft GUID syntax:           {AB5C5A3B-F100-8712-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xab5c5a3b, 0xf100, 0x8712, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.227777508756118260628564089528940772247
As OID (Microsoft):              1.2.840.113556.1.8000.2554.43868.23099.61696.34578.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12347843491835971346.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2874956347.4043343634.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.43868.23099.61696.34578.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xab5c5a3bf10071207e95ce32bd83b97]
Custom data block1 (32 bit):     [0xab5c5a3b]
Custom data block2 (16 bit):     [0xf100]
Custom data block3 (12 bit):     [0x712]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

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

Random 16 bits:                  [0xab5c] 0b1010101101011100
Milliseconds:                    [0x5a] 353 (deviation -2ms..2ms)
Seconds:                         [0x3b] 59
Minute of day:                   [0x00f1] 241 (04:00)
Day of year:                     [0x127] 295 (Day=22, Month=10)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-10-22 04:00:59'353 (deviation -2ms..2ms)