Interpret a UUID
Back
Your input: ba231003-e702-860d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:ba231003-e702-860d-87ea-5ce32bd83b97
URI: uuid:ba231003-e702-860d-87ea-5ce32bd83b97
Microsoft GUID syntax: {BA231003-E702-860D-87EA-5CE32BD83B97}
C++ struct syntax: { 0xba231003, 0xe702, 0x860d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.247418462433775305463706536615209352087
As OID (Microsoft): 1.2.840.113556.1.8000.2554.47651.4099.59138.34317.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13412581724186117645.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3122860035.3875702285.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.47651.4099.59138.34317.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xba231003e70260d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xba231003]
Custom data block2 (16 bit): [0xe702]
Custom data block3 (12 bit): [0x60d]
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: [0xba23] 0b1011101000100011
Milliseconds: [0x10] 63 (deviation -2ms..2ms)
Seconds: [0x03] 3
Minute of day: [0x02e7] 743 (12:22)
Day of year: [0x0d6] 214 (Day=2, 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-02 12:22:03'063 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing