Interprete a UUID

Back

Your input:                      ce69fb05-4c01-8512-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:ce69fb05-4c01-8512-87e9-5ce32bd83b97
URI:                             uuid:ce69fb05-4c01-8512-87e9-5ce32bd83b97
Microsoft GUID syntax:           {CE69FB05-4C01-8512-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xce69fb05, 0x4c01, 0x8512, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.274371249606312853948596971097411828631
As OID (Microsoft):              1.2.840.113556.1.8000.2554.52841.64261.19457.34066.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.14873695244536349970.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3463052037.1275168018.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.52841.64261.19457.34066.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xce69fb054c0151207e95ce32bd83b97]
Custom data block1 (32 bit):     [0xce69fb05]
Custom data block2 (16 bit):     [0x4c01]
Custom data block3 (12 bit):     [0x512]
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:                  [0xce69] 0b1100111001101001
Milliseconds:                    [0xfb] 983 (deviation -2ms..2ms)
Seconds:                         [0x05] 5
Minute of day:                   [0x014c] 332 (05:31)
Day of year:                     [0x125] 293 (Day=20, 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-20 05:31:05'983 (deviation -2ms..2ms)