Interpret a UUID
Back
Your input: 01a0e138-658f-7200-ae0a-f7a65480b798
Various notations:
URN: urn:uuid:01a0e138-658f-7200-ae0a-f7a65480b798
URI: uuid:01a0e138-658f-7200-ae0a-f7a65480b798
Microsoft GUID syntax: {01A0E138-658F-7200-AE0A-F7A65480B798}
C++ struct syntax: { 0x01a0e138, 0x658f, 0x7200, { 0xae, 0x0a, 0xf7, 0xa6, 0x54, 0x80, 0xb7, 0x98 } }
As OID (ISO/ITU-T 128 bits): 2.25.2164563503519811464597879301817284504
As OID (Microsoft): 1.2.840.113556.1.8000.2554.416.57656.25999.29184.44554.16229972.8435608
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.117341222649950720.12541108406120920984
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.27320632.1703899648.2919954342.1417721752
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.416.57656.25999.29184.44554.63398.21632.47000
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x7] Unix Epoch Time
Timestamp: [0x01a0e138658f] 2026-09-27 04:56:04'751 GMT
Random bits: ????0010 00000000 ??101110 00001010 11110111 10100110 01010100 10000000 10110111 10011000
Random bytes: [0x200?e0af7a65480b798]
Lookup this UUID at MagnumDB, Google, Bing