Interpret a UUID
Back
Your input: fdd1c333-1504-880a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:fdd1c333-1504-880a-87ea-5ce32bd83b97
URI: uuid:fdd1c333-1504-880a-87ea-5ce32bd83b97
Microsoft GUID syntax: {FDD1C333-1504-880A-87EA-5CE32BD83B97}
C++ struct syntax: { 0xfdd1c333, 0x1504, 0x880a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.337383832094031158467869505407673711511
As OID (Microsoft): 1.2.840.113556.1.8000.2554.64977.49971.5380.34826.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.18289614185891661834.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4258382643.352618506.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.64977.49971.5380.34826.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xfdd1c333150480a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xfdd1c333]
Custom data block2 (16 bit): [0x1504]
Custom data block3 (12 bit): [0x80a]
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: [0xfdd1] 0b1111110111010001
Milliseconds: [0xc3] 764 (deviation -2ms..2ms)
Seconds: [0x33] 51
Minute of day: [0x0415] 1045 (17:24)
Day of year: [0x0a8] 168 (Day=17, 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-17 17:24:51'764 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing