Interpret a UUID
Back
Your input: db40d63a-2801-8e03-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:db40d63a-2801-8e03-87ea-5ce32bd83b97
URI: uuid:db40d63a-2801-8e03-87ea-5ce32bd83b97
Microsoft GUID syntax: {DB40D63A-2801-8E03-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdb40d63a, 0x2801, 0x8e03, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.291437583119112692378809962663138311063
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56128.54842.10241.36355.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15798863038083337731.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3678459450.671190531.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56128.54842.10241.36355.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdb40d63a2801e0307ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdb40d63a]
Custom data block2 (16 bit): [0x2801]
Custom data block3 (12 bit): [0xe03]
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: [0xdb40] 0b1101101101000000
Milliseconds: [0xd6] 838 (deviation -2ms..2ms)
Seconds: [0x3a] 58
Minute of day: [0x0128] 296 (04:55)
Day of year: [0x03e] 62 (Day=3, Month=3)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-03-03 04:55:58'838 (deviation -2ms..2ms)