Interpret a UUID
Back
Your input: 6d7aee05-0304-850f-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:6d7aee05-0304-850f-87ea-5ce32bd83b97
URI: uuid:6d7aee05-0304-850f-87ea-5ce32bd83b97
Microsoft GUID syntax: {6D7AEE05-0304-850F-87EA-5CE32BD83B97}
C++ struct syntax: { 0x6d7aee05, 0x0304, 0x850f, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.145524139367857479880057896498011585431
As OID (Microsoft): 1.2.840.113556.1.8000.2554.28026.60933.772.34063.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.7888879402585720079.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1836772869.50627855.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.28026.60933.772.34063.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x6d7aee05030450f07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x6d7aee05]
Custom data block2 (16 bit): [0x0304]
Custom data block3 (12 bit): [0x50f]
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: [0x6d7a] 0b0110110101111010
Milliseconds: [0xee] 932 (deviation -2ms..2ms)
Seconds: [0x05] 5
Minute of day: [0x0403] 1027 (17:06)
Day of year: [0x0f5] 245 (Day=2, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-02 17:06:05'932 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing