Interpret a UUID
Back
Your input: 94128719-e600-8d02-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:94128719-e600-8d02-87ea-5ce32bd83b97
URI: uuid:94128719-e600-8d02-87ea-5ce32bd83b97
Microsoft GUID syntax: {94128719-E600-8D02-87EA-5CE32BD83B97}
C++ struct syntax: { 0x94128719, 0xe600, 0x8d02, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.196821944896803950078463347617466694551
As OID (Microsoft): 1.2.840.113556.1.8000.2554.37906.34585.58880.36098.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.10669739012496854274.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2484242201.3858795778.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.37906.34585.58880.36098.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x94128719e600d0207ea5ce32bd83b97]
Custom data block1 (32 bit): [0x94128719]
Custom data block2 (16 bit): [0xe600]
Custom data block3 (12 bit): [0xd02]
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: [0x9412] 0b1001010000010010
Milliseconds: [0x87] 529 (deviation -2ms..2ms)
Seconds: [0x19] 25
Minute of day: [0x00e6] 230 (03:49)
Day of year: [0x02d] 45 (Day=14, Month=2)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-02-14 03:49:25'529 (deviation -2ms..2ms)