Interpret a UUID
Back
Your input: adca8010-3400-8013-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:adca8010-3400-8013-87ea-5ce32bd83b97
URI: uuid:adca8010-3400-8013-87ea-5ce32bd83b97
Microsoft GUID syntax: {ADCA8010-3400-8013-87EA-5CE32BD83B97}
C++ struct syntax: { 0xadca8010, 0x3400, 0x8013, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.231007884668388174169267079191060822935
As OID (Microsoft): 1.2.840.113556.1.8000.2554.44490.32784.13312.32787.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.12522962520937365523.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2915729424.872448019.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.44490.32784.13312.32787.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xadca8010340001307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xadca8010]
Custom data block2 (16 bit): [0x3400]
Custom data block3 (12 bit): [0x013]
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: [0xadca] 0b1010110111001010
Milliseconds: [0x80] 501 (deviation -2ms..2ms)
Seconds: [0x10] 16
Minute of day: [0x0034] 52 (00:51)
Day of year: [0x130] 304 (Day=31, 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-31 00:51:16'501 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing