Interpret a UUID
Back
Your input: 259ade21-7c05-880d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:259ade21-7c05-880d-87ea-5ce32bd83b97
URI: uuid:259ade21-7c05-880d-87ea-5ce32bd83b97
Microsoft GUID syntax: {259ADE21-7C05-880D-87EA-5CE32BD83B97}
C++ struct syntax: { 0x259ade21, 0x7c05, 0x880d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.49985554908100452732179761909961603991
As OID (Microsoft): 1.2.840.113556.1.8000.2554.9626.56865.31749.34829.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.2709722361212798989.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.630906401.2080737293.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.9626.56865.31749.34829.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x259ade217c0580d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x259ade21]
Custom data block2 (16 bit): [0x7c05]
Custom data block3 (12 bit): [0x80d]
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: [0x259a] 0b0010010110011010
Milliseconds: [0xde] 870 (deviation -2ms..2ms)
Seconds: [0x21] 33
Minute of day: [0x057c] 1404 (23:23)
Day of year: [0x0d8] 216 (Day=4, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-04 23:23:33'870 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing