Interpret a UUID
Back
Your input: 29a13004-be02-840e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:29a13004-be02-840e-87ea-5ce32bd83b97
URI: uuid:29a13004-be02-840e-87ea-5ce32bd83b97
Microsoft GUID syntax: {29A13004-BE02-840E-87EA-5CE32BD83B97}
C++ struct syntax: { 0x29a13004, 0xbe02, 0x840e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.55335281552784476712605889834329324439
As OID (Microsoft): 1.2.840.113556.1.8000.2554.10657.12292.48642.33806.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.2999731623731299342.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.698429444.3187835918.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.10657.12292.48642.33806.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x29a13004be0240e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x29a13004]
Custom data block2 (16 bit): [0xbe02]
Custom data block3 (12 bit): [0x40e]
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: [0x29a1] 0b0010100110100001
Milliseconds: [0x30] 188 (deviation -2ms..2ms)
Seconds: [0x04] 4
Minute of day: [0x02be] 702 (11:41)
Day of year: [0x0e4] 228 (Day=16, 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-16 11:41:04'188 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing