Interpret a UUID
Back
Your input: db51c730-7e05-8d12-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:db51c730-7e05-8d12-87ea-5ce32bd83b97
URI: uuid:db51c730-7e05-8d12-87ea-5ce32bd83b97
Microsoft GUID syntax: {DB51C730-7E05-8D12-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdb51c730, 0x7e05, 0x8d12, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.291525547163902646633044058619554315159
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56145.50992.32261.36114.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15803631578506431762.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3679569712.2114293010.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56145.50992.32261.36114.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdb51c7307e05d1207ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdb51c730]
Custom data block2 (16 bit): [0x7e05]
Custom data block3 (12 bit): [0xd12]
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: [0xdb51] 0b1101101101010001
Milliseconds: [0xc7] 780 (deviation -2ms..2ms)
Seconds: [0x30] 48
Minute of day: [0x057e] 1406 (23:25)
Day of year: [0x12d] 301 (Day=28, 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-28 23:25:48'780 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing