Interpret a UUID
Back
Your input: db833f12-5205-8c01-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:db833f12-5205-8c01-87ea-5ce32bd83b97
URI: uuid:db833f12-5205-8c01-87ea-5ce32bd83b97
Microsoft GUID syntax: {DB833F12-5205-8C01-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdb833f12, 0x5205, 0x8c01, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.291782401208661070491262483656923954071
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56195.16146.20997.35841.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15817555664173370369.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3682811666.1376095233.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56195.16146.20997.35841.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdb833f125205c0107ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdb833f12]
Custom data block2 (16 bit): [0x5205]
Custom data block3 (12 bit): [0xc01]
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: [0xdb83] 0b1101101110000011
Milliseconds: [0x3f] 247 (deviation -2ms..2ms)
Seconds: [0x12] 18
Minute of day: [0x0552] 1362 (22:41)
Day of year: [0x01c] 28 (Day=28, Month=1)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-01-28 22:41:18'247 (deviation -2ms..2ms)