Interpret a UUID
Back
Your input: 2635d023-a600-800d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:2635d023-a600-800d-87ea-5ce32bd83b97
URI: uuid:2635d023-a600-800d-87ea-5ce32bd83b97
Microsoft GUID syntax: {2635D023-A600-800D-87EA-5CE32BD83B97}
C++ struct syntax: { 0x2635d023, 0xa600, 0x800d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.50790077138887512924211285549966179223
As OID (Microsoft): 1.2.840.113556.1.8000.2554.9781.53283.42496.32781.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.2753335598734409741.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.641060899.2785050637.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.9781.53283.42496.32781.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x2635d023a60000d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x2635d023]
Custom data block2 (16 bit): [0xa600]
Custom data block3 (12 bit): [0x00d]
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: [0x2635] 0b0010011000110101
Milliseconds: [0xd0] 815 (deviation -2ms..2ms)
Seconds: [0x23] 35
Minute of day: [0x00a6] 166 (02:45)
Day of year: [0x0d0] 208 (Day=27, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-27 02:45:35'815 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing