Interpret a UUID
Back
Your input: 8ab1dc1c-9d00-8413-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:8ab1dc1c-9d00-8413-87ea-5ce32bd83b97
URI: uuid:8ab1dc1c-9d00-8413-87ea-5ce32bd83b97
Microsoft GUID syntax: {8AB1DC1C-9D00-8413-87EA-5CE32BD83B97}
C++ struct syntax: { 0x8ab1dc1c, 0x9d00, 0x8413, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.184356964359370178972478787637346843543
As OID (Microsoft): 1.2.840.113556.1.8000.2554.35505.56348.40192.33811.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9994011063563093011.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2326912028.2634056723.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.35505.56348.40192.33811.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x8ab1dc1c9d0041307ea5ce32bd83b97]
Custom data block1 (32 bit): [0x8ab1dc1c]
Custom data block2 (16 bit): [0x9d00]
Custom data block3 (12 bit): [0x413]
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: [0x8ab1] 0b1000101010110001
Milliseconds: [0xdc] 862 (deviation -2ms..2ms)
Seconds: [0x1c] 28
Minute of day: [0x009d] 157 (02:36)
Day of year: [0x134] 308 (Day=4, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-11-04 02:36:28'862 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing