Interpret a UUID

Back

UUID: 
Your input:                      190bfe04-4e04-8d01-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:190bfe04-4e04-8d01-87ea-5ce32bd83b97
URI:                             uuid:190bfe04-4e04-8d01-87ea-5ce32bd83b97
Microsoft GUID syntax:           {190BFE04-4E04-8D01-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x190bfe04, 0x4e04, 0x8d01, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.33292967233164089859111989983982402455
As OID (Microsoft):              1.2.840.113556.1.8000.2554.6411.65028.19972.36097.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.1804815370134260993.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.420216324.1308921089.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.6411.65028.19972.36097.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x190bfe044e04d0107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x190bfe04]
Custom data block2 (16 bit):     [0x4e04]
Custom data block3 (12 bit):     [0xd01]
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:                  [0x190b] 0b0001100100001011
Milliseconds:                    [0xfe] 995 (deviation -2ms..2ms)
Seconds:                         [0x04] 4
Minute of day:                   [0x044e] 1102 (18:21)
Day of year:                     [0x01d] 29 (Day=29, Month=1)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-01-29 18:21:04'995 (deviation -2ms..2ms)