Interpret a UUID

Back

Your input:                      40f6552e-5905-8803-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:40f6552e-5905-8803-87ea-5ce32bd83b97
URI:                             uuid:40f6552e-5905-8803-87ea-5ce32bd83b97
Microsoft GUID syntax:           {40F6552E-5905-8803-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x40f6552e, 0x5905, 0x8803, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.86349624434296822320781148000001473431
As OID (Microsoft):              1.2.840.113556.1.8000.2554.16630.21806.22789.34819.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.4681022520248600579.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.1089885486.1493534723.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.16630.21806.22789.34819.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x40f6552e590580307ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x40f6552e]
Custom data block2 (16 bit):     [0x5905]
Custom data block3 (12 bit):     [0x803]
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:                  [0x40f6] 0b0100000011110110
Milliseconds:                    [0x55] 333 (deviation -2ms..2ms)
Seconds:                         [0x2e] 46
Minute of day:                   [0x0559] 1369 (22:48)
Day of year:                     [0x038] 56 (Day=25, 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-25 22:48:46'333 (deviation -2ms..2ms)