Interprete a UUID
Back
Your input: 3af0213b-00d2-8165-87e8-5ce32bd83b96
Various notations:
URN: urn:uuid:3af0213b-00d2-8165-87e8-5ce32bd83b96
URI: uuid:3af0213b-00d2-8165-87e8-5ce32bd83b96
Microsoft GUID syntax: {3AF0213B-00D2-8165-87E8-5CE32BD83B96}
C++ struct syntax: { 0x3af0213b, 0x00d2, 0x8165, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }
As OID (ISO/ITU-T 128 bits): 2.25.78342048995806473586297730169723960214
As OID (Microsoft): 1.2.840.113556.1.8000.2554.15088.8507.210.33125.34792.6087467.14171030
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.4246930985910960485.9793179520480066454
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.988815675.13795685.2280152291.735591318
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.15088.8507.210.33125.34792.23779.11224.15254
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x3af0213b00d216507e85ce32bd83b96]
Custom data block1 (32 bit): [0x3af0213b]
Custom data block2 (16 bit): [0x00d2]
Custom data block3 (12 bit): [0x165]
Custom data block4 (14 bit): [0x07e8]
Custom data block5 (48 bit): [0x5ce32bd83b96]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 2
Random 16 bits: [0x3af0] 0b0011101011110000
Milliseconds: [0x21] 129 (deviation -2ms..2ms)
Seconds: [0x3b] 59
Minute of day: [0x00d2] 210 (03:29)
Day of year: [0x165] 357 (Day=22, Month=12)
Unused 2 bits: [0] 0b00
Year: [0x7e8] 2024
Signature: [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time: 2024-12-22 03:29:59'129 (deviation -2ms..2ms)