Interpret a UUID
Back
Your input: de1b1b04-ab00-8c10-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:de1b1b04-ab00-8c10-87ea-5ce32bd83b97
URI: uuid:de1b1b04-ab00-8c10-87ea-5ce32bd83b97
Microsoft GUID syntax: {DE1B1B04-AB00-8C10-87EA-5CE32BD83B97}
C++ struct syntax: { 0xde1b1b04, 0xab00, 0x8c10, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.295229355074326310898473543885139753879
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56859.6916.43776.35856.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16004415407653948432.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3726318340.2868939792.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56859.6916.43776.35856.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xde1b1b04ab00c1007ea5ce32bd83b97]
Custom data block1 (32 bit): [0xde1b1b04]
Custom data block2 (16 bit): [0xab00]
Custom data block3 (12 bit): [0xc10]
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: [0xde1b] 0b1101111000011011
Milliseconds: [0x1b] 106 (deviation -2ms..2ms)
Seconds: [0x04] 4
Minute of day: [0x00ab] 171 (02:50)
Day of year: [0x10c] 268 (Day=25, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-25 02:50:04'106 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing