Interpret a UUID
Back
Your input: db675817-3d03-8210-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:db675817-3d03-8210-87ea-5ce32bd83b97
URI: uuid:db675817-3d03-8210-87ea-5ce32bd83b97
Microsoft GUID syntax: {DB675817-3D03-8210-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdb675817, 0x3d03, 0x8210, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.291637524346501349175894773116329016215
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56167.22551.15619.33296.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15809701873738547728.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3680983063.1023640080.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56167.22551.15619.33296.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdb6758173d0321007ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdb675817]
Custom data block2 (16 bit): [0x3d03]
Custom data block3 (12 bit): [0x210]
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: [0xdb67] 0b1101101101100111
Milliseconds: [0x58] 345 (deviation -2ms..2ms)
Seconds: [0x17] 23
Minute of day: [0x033d] 829 (13:48)
Day of year: [0x102] 258 (Day=15, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-15 13:48:23'345 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing