Interpret a UUID
Back
Your input: a186f538-be04-8a12-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:a186f538-be04-8a12-87ea-5ce32bd83b97
URI: uuid:a186f538-be04-8a12-87ea-5ce32bd83b97
Microsoft GUID syntax: {A186F538-BE04-8A12-87EA-5CE32BD83B97}
C++ struct syntax: { 0xa186f538, 0xbe04, 0x8a12, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.214706448786352757495536588910929394583
As OID (Microsoft): 1.2.840.113556.1.8000.2554.41350.62776.48644.35346.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11639259911040567826.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2709976376.3187968530.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.41350.62776.48644.35346.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xa186f538be04a1207ea5ce32bd83b97]
Custom data block1 (32 bit): [0xa186f538]
Custom data block2 (16 bit): [0xbe04]
Custom data block3 (12 bit): [0xa12]
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: [0xa186] 0b1010000110000110
Milliseconds: [0xf5] 960 (deviation -2ms..2ms)
Seconds: [0x38] 56
Minute of day: [0x04be] 1214 (20:13)
Day of year: [0x12a] 298 (Day=25, 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-25 20:13:56'960 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing