Interprete a UUID

Back

UUID: 
Your input:                      c0a1df0f-4903-8c13-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:c0a1df0f-4903-8c13-87e9-5ce32bd83b97
URI:                             uuid:c0a1df0f-4903-8c13-87e9-5ce32bd83b97
Microsoft GUID syntax:           {C0A1DF0F-4903-8C13-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xc0a1df0f, 0x4903, 0x8c13, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.256052259173288700868200203673727941527
As OID (Microsoft):              1.2.840.113556.1.8000.2554.49313.57103.18691.35859.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.13880620783275052051.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3231833871.1224969235.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.49313.57103.18691.35859.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xc0a1df0f4903c1307e95ce32bd83b97]
Custom data block1 (32 bit):     [0xc0a1df0f]
Custom data block2 (16 bit):     [0x4903]
Custom data block3 (12 bit):     [0xc13]
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:                  [0xc0a1] 0b1100000010100001
Milliseconds:                    [0xdf] 874 (deviation -2ms..2ms)
Seconds:                         [0x0f] 15
Minute of day:                   [0x0349] 841 (14:00)
Day of year:                     [0x13c] 316 (Day=12, Month=11)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-11-12 14:00:15'874 (deviation -2ms..2ms)