Interpret a UUID

Back

UUID: 
Your input:                      f67f5c0f-4a00-8a04-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:f67f5c0f-4a00-8a04-87ea-5ce32bd83b97
URI:                             uuid:f67f5c0f-4a00-8a04-87ea-5ce32bd83b97
Microsoft GUID syntax:           {F67F5C0F-4A00-8A04-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xf67f5c0f, 0x4a00, 0x8a04, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.327651375857131744007738866774998268823
As OID (Microsoft):              1.2.840.113556.1.8000.2554.63103.23567.18944.35332.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.17762016676108339716.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4135541775.1241549316.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.63103.23567.18944.35332.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xf67f5c0f4a00a0407ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xf67f5c0f]
Custom data block2 (16 bit):     [0x4a00]
Custom data block3 (12 bit):     [0xa04]
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:                  [0xf67f] 0b1111011001111111
Milliseconds:                    [0x5c] 360 (deviation -2ms..2ms)
Seconds:                         [0x0f] 15
Minute of day:                   [0x004a] 74 (01:13)
Day of year:                     [0x04a] 74 (Day=15, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-03-15 01:13:15'360 (deviation -2ms..2ms)