Interpret a UUID

Back

Your input:                      2d5b4715-c203-8901-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:2d5b4715-c203-8901-87ea-5ce32bd83b97
URI:                             uuid:2d5b4715-c203-8901-87ea-5ce32bd83b97
Microsoft GUID syntax:           {2D5B4715-C203-8901-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x2d5b4715, 0xc203, 0x8901, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.60289200599365521338267209503507757975
As OID (Microsoft):              1.2.840.113556.1.8000.2554.11611.18197.49667.35073.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.3268284113362323713.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.760956693.3255011585.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.11611.18197.49667.35073.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x2d5b4715c20390107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x2d5b4715]
Custom data block2 (16 bit):     [0xc203]
Custom data block3 (12 bit):     [0x901]
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:                  [0x2d5b] 0b0010110101011011
Milliseconds:                    [0x47] 278 (deviation -2ms..2ms)
Seconds:                         [0x15] 21
Minute of day:                   [0x03c2] 962 (16:01)
Day of year:                     [0x019] 25 (Day=25, 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-25 16:01:21'278 (deviation -2ms..2ms)