Interprete a UUID
Back
Your input: f38baa13-012f-8077-87e8-5ce32bd83b96
Various notations:
URN: urn:uuid:f38baa13-012f-8077-87e8-5ce32bd83b96
URI: uuid:f38baa13-012f-8077-87e8-5ce32bd83b96
Microsoft GUID syntax: {F38BAA13-012F-8077-87E8-5CE32BD83B96}
C++ struct syntax: { 0xf38baa13, 0x012f, 0x8077, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }
As OID (ISO/ITU-T 128 bits): 2.25.323727581754405517902194104194379037590
As OID (Microsoft): 1.2.840.113556.1.8000.2554.62347.43539.303.32887.34792.6087467.14171030
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17549307371580260471.9793179520480066454
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4086016531.19890295.2280152291.735591318
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.62347.43539.303.32887.34792.23779.11224.15254
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xf38baa13012f07707e85ce32bd83b96]
Custom data block1 (32 bit): [0xf38baa13]
Custom data block2 (16 bit): [0x012f]
Custom data block3 (12 bit): [0x077]
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: [0xf38b] 0b1111001110001011
Milliseconds: [0xaa] 666 (deviation -2ms..2ms)
Seconds: [0x13] 19
Minute of day: [0x012f] 303 (05:02)
Day of year: [0x077] 119 (Day=28, 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-28 05:02:19'666 (deviation -2ms..2ms)