Interpret a UUID
Back
Your input: 66ffc301-6400-8f09-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:66ffc301-6400-8f09-87ea-5ce32bd83b97
URI: uuid:66ffc301-6400-8f09-87ea-5ce32bd83b97
Microsoft GUID syntax: {66FFC301-6400-8F09-87EA-5CE32BD83B97}
C++ struct syntax: { 0x66ffc301, 0x6400, 0x8f09, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.136909246449037851127816600385654111127
As OID (Microsoft): 1.2.840.113556.1.8000.2554.26367.49921.25600.36617.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.7421865121670008585.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1728037633.1677758217.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.26367.49921.25600.36617.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x66ffc3016400f0907ea5ce32bd83b97]
Custom data block1 (32 bit): [0x66ffc301]
Custom data block2 (16 bit): [0x6400]
Custom data block3 (12 bit): [0xf09]
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: [0x66ff] 0b0110011011111111
Milliseconds: [0xc3] 764 (deviation -2ms..2ms)
Seconds: [0x01] 1
Minute of day: [0x0064] 100 (01:39)
Day of year: [0x09f] 159 (Day=8, 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-08 01:39:01'764 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing