Interpret a UUID
Back
Your input: c95ee234-fd02-8212-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:c95ee234-fd02-8212-87ea-5ce32bd83b97
URI: uuid:c95ee234-fd02-8212-87ea-5ce32bd83b97
Microsoft GUID syntax: {C95EE234-FD02-8212-87EA-5CE32BD83B97}
C++ struct syntax: { 0xc95ee234, 0xfd02, 0x8212, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.267667491080207979855925893211174222743
As OID (Microsoft): 1.2.840.113556.1.8000.2554.51550.57908.64770.33298.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.14510283766645293586.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3378438708.4244800018.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.51550.57908.64770.33298.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xc95ee234fd0221207ea5ce32bd83b97]
Custom data block1 (32 bit): [0xc95ee234]
Custom data block2 (16 bit): [0xfd02]
Custom data block3 (12 bit): [0x212]
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: [0xc95e] 0b1100100101011110
Milliseconds: [0xe2] 885 (deviation -2ms..2ms)
Seconds: [0x34] 52
Minute of day: [0x02fd] 765 (12:44)
Day of year: [0x122] 290 (Day=17, Month=10)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-10-17 12:44:52'885 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing