Interpret a UUID

Back

Your input:                      feb0d31f-fc04-8502-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:feb0d31f-fc04-8502-87ea-5ce32bd83b97
URI:                             uuid:feb0d31f-fc04-8502-87ea-5ce32bd83b97
Microsoft GUID syntax:           {FEB0D31F-FC04-8502-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xfeb0d31f, 0xfc04, 0x8502, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.338542037298965856124529147051043732375
As OID (Microsoft):              1.2.840.113556.1.8000.2554.65200.54047.64516.34050.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.18352400615860372738.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4273001247.4228154626.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.65200.54047.64516.34050.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xfeb0d31ffc0450207ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xfeb0d31f]
Custom data block2 (16 bit):     [0xfc04]
Custom data block3 (12 bit):     [0x502]
Custom data block4 (14 bit):     [0x07ea]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

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

Random 16 bits:                  [0xfeb0] 0b1111111010110000
Milliseconds:                    [0xd3] 827 (deviation -2ms..2ms)
Seconds:                         [0x1f] 31
Minute of day:                   [0x04fc] 1276 (21:15)
Day of year:                     [0x025] 37 (Day=6, Month=2)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-02-06 21:15:31'827 (deviation -2ms..2ms)