Interprete a UUID

Back

UUID: 
Your input:                      1872bc38-3504-8c15-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:1872bc38-3504-8c15-87e9-5ce32bd83b97
URI:                             uuid:1872bc38-3504-8c15-87e9-5ce32bd83b97
Microsoft GUID syntax:           {1872BC38-3504-8C15-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x1872bc38, 0x3504, 0x8c15, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.32497211286901741364478888802761849751
As OID (Microsoft):              1.2.840.113556.1.8000.2554.6258.48184.13572.35861.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.1761677353848966165.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.410172472.889490453.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.6258.48184.13572.35861.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x1872bc383504c1507e95ce32bd83b97]
Custom data block1 (32 bit):     [0x1872bc38]
Custom data block2 (16 bit):     [0x3504]
Custom data block3 (12 bit):     [0xc15]
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:                  [0x1872] 0b0001100001110010
Milliseconds:                    [0xbc] 737 (deviation -2ms..2ms)
Seconds:                         [0x38] 56
Minute of day:                   [0x0435] 1077 (17:56)
Day of year:                     [0x15c] 348 (Day=14, Month=12)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-12-14 17:56:56'737 (deviation -2ms..2ms)