Interpret a UUID
Back
Your input: 46b12726-eb02-890c-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:46b12726-eb02-890c-87ea-5ce32bd83b97
URI: uuid:46b12726-eb02-890c-87ea-5ce32bd83b97
Microsoft GUID syntax: {46B12726-EB02-890C-87EA-5CE32BD83B97}
C++ struct syntax: { 0x46b12726, 0xeb02, 0x890c, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.93965790346281535905725899472381688727
As OID (Microsoft): 1.2.840.113556.1.8000.2554.18097.10022.60162.35084.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.5093895701637794060.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1186015014.3942811916.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.18097.10022.60162.35084.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x46b12726eb0290c07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x46b12726]
Custom data block2 (16 bit): [0xeb02]
Custom data block3 (12 bit): [0x90c]
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: [0x46b1] 0b0100011010110001
Milliseconds: [0x27] 153 (deviation -2ms..2ms)
Seconds: [0x26] 38
Minute of day: [0x02eb] 747 (12:26)
Day of year: [0x0c9] 201 (Day=20, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-20 12:26:38'153 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing