Interpret a UUID
Back
Your input: 62f17701-a201-8c0f-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:62f17701-a201-8c0f-87ea-5ce32bd83b97
URI: uuid:62f17701-a201-8c0f-87ea-5ce32bd83b97
Microsoft GUID syntax: {62F17701-A201-8C0F-87EA-5CE32BD83B97}
C++ struct syntax: { 0x62f17701, 0xa201, 0x8c0f, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.131518100865938088000773749928258714519
As OID (Microsoft): 1.2.840.113556.1.8000.2554.25329.30465.41473.35855.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.7129610534000888847.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1659991809.2718010383.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.25329.30465.41473.35855.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x62f17701a201c0f07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x62f17701]
Custom data block2 (16 bit): [0xa201]
Custom data block3 (12 bit): [0xc0f]
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: [0x62f1] 0b0110001011110001
Milliseconds: [0x77] 466 (deviation -2ms..2ms)
Seconds: [0x01] 1
Minute of day: [0x01a2] 418 (06:57)
Day of year: [0x0fc] 252 (Day=9, 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-09 06:57:01'466 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing