Interprete a UUID
Back
Your input: ab24611c-0165-8074-87e8-5ce32bd83b96
Various notations:
URN: urn:uuid:ab24611c-0165-8074-87e8-5ce32bd83b96
URI: uuid:ab24611c-0165-8074-87e8-5ce32bd83b96
Microsoft GUID syntax: {AB24611C-0165-8074-87E8-5CE32BD83B96}
C++ struct syntax: { 0xab24611c, 0x0165, 0x8074, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }
As OID (ISO/ITU-T 128 bits): 2.25.227486879578680165802738402679141710742
As OID (Microsoft): 1.2.840.113556.1.8000.2554.43812.24860.357.32884.34792.6087467.14171030
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.12332088452557668468.9793179520480066454
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2871288092.23429236.2280152291.735591318
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.43812.24860.357.32884.34792.23779.11224.15254
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xab24611c016507407e85ce32bd83b96]
Custom data block1 (32 bit): [0xab24611c]
Custom data block2 (16 bit): [0x0165]
Custom data block3 (12 bit): [0x074]
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: [0xab24] 0b1010101100100100
Milliseconds: [0x61] 380 (deviation -2ms..2ms)
Seconds: [0x1c] 28
Minute of day: [0x0165] 357 (05:56)
Day of year: [0x074] 116 (Day=25, Month=4)
Unused 2 bits: [0] 0b00
Year: [0x7e8] 2024
Signature: [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time: 2024-04-25 05:56:28'380 (deviation -2ms..2ms)