Interpret a UUID
Back
Your input: cae21026-2002-8d11-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:cae21026-2002-8d11-87ea-5ce32bd83b97
URI: uuid:cae21026-2002-8d11-87ea-5ce32bd83b97
Microsoft GUID syntax: {CAE21026-2002-8D11-87EA-5CE32BD83B97}
C++ struct syntax: { 0xcae21026, 0x2002, 0x8d11, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.269677841777712315682373277858737437591
As OID (Microsoft): 1.2.840.113556.1.8000.2554.51938.4134.8194.36113.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.14619265096329891089.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3403812902.537038097.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.51938.4134.8194.36113.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xcae210262002d1107ea5ce32bd83b97]
Custom data block1 (32 bit): [0xcae21026]
Custom data block2 (16 bit): [0x2002]
Custom data block3 (12 bit): [0xd11]
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: [0xcae2] 0b1100101011100010
Milliseconds: [0x10] 63 (deviation -2ms..2ms)
Seconds: [0x26] 38
Minute of day: [0x0220] 544 (09:03)
Day of year: [0x11d] 285 (Day=12, Month=10)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-10-12 09:03:38'063 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing