Interpret a UUID
Back
Your input: 88e1112f-2104-820b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:88e1112f-2104-820b-87ea-5ce32bd83b97
URI: uuid:88e1112f-2104-820b-87ea-5ce32bd83b97
Microsoft GUID syntax: {88E1112F-2104-820B-87EA-5CE32BD83B97}
C++ struct syntax: { 0x88e1112f, 0x2104, 0x820b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.181943622754824250327891741991771847575
As OID (Microsoft): 1.2.840.113556.1.8000.2554.35041.4399.8452.33291.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9863183553033175563.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2296451375.553943563.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.35041.4399.8452.33291.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x88e1112f210420b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x88e1112f]
Custom data block2 (16 bit): [0x2104]
Custom data block3 (12 bit): [0x20b]
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: [0x88e1] 0b1000100011100001
Milliseconds: [0x11] 67 (deviation -2ms..2ms)
Seconds: [0x2f] 47
Minute of day: [0x0421] 1057 (17:36)
Day of year: [0x0b2] 178 (Day=27, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-27 17:36:47'067 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing