Interpret a UUID
Back
Your input: 112dfc32-b401-890a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:112dfc32-b401-890a-87ea-5ce32bd83b97
URI: uuid:112dfc32-b401-890a-87ea-5ce32bd83b97
Microsoft GUID syntax: {112DFC32-B401-890A-87EA-5CE32BD83B97}
C++ struct syntax: { 0x112dfc32, 0xb401, 0x890a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.22835644471315040868943370092660931479
As OID (Microsoft): 1.2.840.113556.1.8000.2554.4397.64562.46081.35082.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.1237922767295318282.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.288226354.3019999498.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.4397.64562.46081.35082.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x112dfc32b40190a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x112dfc32]
Custom data block2 (16 bit): [0xb401]
Custom data block3 (12 bit): [0x90a]
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: [0x112d] 0b0001000100101101
Milliseconds: [0xfc] 987 (deviation -2ms..2ms)
Seconds: [0x32] 50
Minute of day: [0x01b4] 436 (07:15)
Day of year: [0x0a9] 169 (Day=18, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-18 07:15:50'987 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing