Interprete a UUID
Back
Your input: ed7a7415-0605-8114-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:ed7a7415-0605-8114-87e9-5ce32bd83b97
URI: uuid:ed7a7415-0605-8114-87e9-5ce32bd83b97
Microsoft GUID syntax: {ED7A7415-0605-8114-87E9-5CE32BD83B97}
C++ struct syntax: { 0xed7a7415, 0x0605, 0x8114, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.315662849642935311494234037396281244567
As OID (Microsoft): 1.2.840.113556.1.8000.2554.60794.29717.1541.33044.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17112117367791780116.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3984225301.101024020.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.60794.29717.1541.33044.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xed7a7415060511407e95ce32bd83b97]
Custom data block1 (32 bit): [0xed7a7415]
Custom data block2 (16 bit): [0x0605]
Custom data block3 (12 bit): [0x114]
Custom data block4 (14 bit): [0x07e9]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0xed7a] 0b1110110101111010
Milliseconds: [0x74] 454 (deviation -2ms..2ms)
Seconds: [0x15] 21
Minute of day: [0x0506] 1286 (21:25)
Day of year: [0x141] 321 (Day=17, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-11-17 21:25:21'454 (deviation -2ms..2ms)