Interpret a UUID
Back
Your input: b2393e15-7d04-880c-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:b2393e15-7d04-880c-87ea-5ce32bd83b97
URI: uuid:b2393e15-7d04-880c-87ea-5ce32bd83b97
Microsoft GUID syntax: {B2393E15-7D04-880C-87EA-5CE32BD83B97}
C++ struct syntax: { 0xb2393e15, 0x7d04, 0x880c, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.236899803382529454158764202948663196567
As OID (Microsoft): 1.2.840.113556.1.8000.2554.45625.15893.32004.34828.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.12842364074436364300.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2990095893.2097448972.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.45625.15893.32004.34828.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xb2393e157d0480c07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xb2393e15]
Custom data block2 (16 bit): [0x7d04]
Custom data block3 (12 bit): [0x80c]
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: [0xb239] 0b1011001000111001
Milliseconds: [0x3e] 243 (deviation -2ms..2ms)
Seconds: [0x15] 21
Minute of day: [0x047d] 1149 (19:08)
Day of year: [0x0c8] 200 (Day=19, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-19 19:08:21'243 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing