Interpret a UUID
Back
Your input: 01a014c3-bade-70c5-8063-f1b9de221e3d
Various notations:
URN: urn:uuid:01a014c3-bade-70c5-8063-f1b9de221e3d
URI: uuid:01a014c3-bade-70c5-8063-f1b9de221e3d
Microsoft GUID syntax: {01A014C3-BADE-70C5-8063-F1B9DE221E3D}
C++ struct syntax: { 0x01a014c3, 0xbade, 0x70c5, { 0x80, 0x63, 0xf1, 0xb9, 0xde, 0x22, 0x1e, 0x3d } }
As OID (ISO/ITU-T 128 bits): 2.25.2160416648667377515453794379838398013
As OID (Microsoft): 1.2.840.113556.1.8000.2554.416.5315.47838.28869.32867.15841758.2235965
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.117116421197951173.9251503840147152445
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.27268291.3135140037.2154033593.3726777917
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.416.5315.47838.28869.32867.61881.56866.7741
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x7] Unix Epoch Time
Timestamp: [0x01a014c3bade] 2026-08-18 12:06:06'814 GMT
Random bits: ????0000 11000101 ??000000 01100011 11110001 10111001 11011110 00100010 00011110 00111101
Random bytes: [0x0c5?063f1b9de221e3d]
Lookup this UUID at MagnumDB, Google, Bing