Interpret a UUID

Back

UUID: 
Your input:                      fd110e13-6704-8416-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:fd110e13-6704-8416-87e9-5ce32bd83b97
URI:                             uuid:fd110e13-6704-8416-87e9-5ce32bd83b97
Microsoft GUID syntax:           {FD110E13-6704-8416-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xfd110e13, 0x6704, 0x8416, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.336383237471130762291631124232963373975
As OID (Microsoft):              1.2.840.113556.1.8000.2554.64785.3603.26372.33814.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.18235371842695365654.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4245753363.1728349206.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.64785.3603.26372.33814.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xfd110e13670441607e95ce32bd83b97]
Custom data block1 (32 bit):     [0xfd110e13]
Custom data block2 (16 bit):     [0x6704]
Custom data block3 (12 bit):     [0x416]
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:                  [0xfd11] 0b1111110100010001
Milliseconds:                    [0x0e] 55 (deviation -2ms..2ms)
Seconds:                         [0x13] 19
Minute of day:                   [0x0467] 1127 (18:46)
Day of year:                     [0x164] 356 (Day=22, 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-22 18:46:19'055 (deviation -2ms..2ms)