Interpret a UUID

Back

UUID: 
Your input:                      bf204504-5c01-8a06-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:bf204504-5c01-8a06-87ea-5ce32bd83b97
URI:                             uuid:bf204504-5c01-8a06-87ea-5ce32bd83b97
Microsoft GUID syntax:           {BF204504-5C01-8A06-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xbf204504, 0x5c01, 0x8a06, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.254050100526041829867488931006180244375
As OID (Microsoft):              1.2.840.113556.1.8000.2554.48928.17668.23553.35334.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.13772083545524767238.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3206563076.1543604742.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.48928.17668.23553.35334.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xbf2045045c01a0607ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xbf204504]
Custom data block2 (16 bit):     [0x5c01]
Custom data block3 (12 bit):     [0xa06]
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:                  [0xbf20] 0b1011111100100000
Milliseconds:                    [0x45] 270 (deviation -2ms..2ms)
Seconds:                         [0x04] 4
Minute of day:                   [0x015c] 348 (05:47)
Day of year:                     [0x06a] 106 (Day=16, Month=4)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-04-16 05:47:04'270 (deviation -2ms..2ms)