Interpret a UUID
Back
Your input: 190d8c34-df03-8512-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:190d8c34-df03-8512-87ea-5ce32bd83b97
URI: uuid:190d8c34-df03-8512-87ea-5ce32bd83b97
Microsoft GUID syntax: {190D8C34-DF03-8512-87EA-5CE32BD83B97}
C++ struct syntax: { 0x190d8c34, 0xdf03, 0x8512, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.33301043480012223941567132111923067799
As OID (Microsoft): 1.2.840.113556.1.8000.2554.6413.35892.57091.34066.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.1805253184353174802.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.420318260.3741549842.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.6413.35892.57091.34066.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x190d8c34df0351207ea5ce32bd83b97]
Custom data block1 (32 bit): [0x190d8c34]
Custom data block2 (16 bit): [0xdf03]
Custom data block3 (12 bit): [0x512]
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: [0x190d] 0b0001100100001101
Milliseconds: [0x8c] 548 (deviation -2ms..2ms)
Seconds: [0x34] 52
Minute of day: [0x03df] 991 (16:30)
Day of year: [0x125] 293 (Day=20, 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-20 16:30:52'548 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing