Interprete a UUID
Back
Your input: 83996901-8e05-8f15-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:83996901-8e05-8f15-87e9-5ce32bd83b97
URI: uuid:83996901-8e05-8f15-87e9-5ce32bd83b97
Microsoft GUID syntax: {83996901-8E05-8F15-87E9-5CE32BD83B97}
C++ struct syntax: { 0x83996901, 0x8e05, 0x8f15, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.174925418643369945636533952697440156567
As OID (Microsoft): 1.2.840.113556.1.8000.2554.33689.26881.36357.36629.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9482725945803902741.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2207869185.2382728981.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.33689.26881.36357.36629.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x839969018e05f1507e95ce32bd83b97]
Custom data block1 (32 bit): [0x83996901]
Custom data block2 (16 bit): [0x8e05]
Custom data block3 (12 bit): [0xf15]
Custom data block4 (14 bit): [0x07e9]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x8399] 0b1000001110011001
Milliseconds: [0x69] 411 (deviation -2ms..2ms)
Seconds: [0x01] 1
Minute of day: [0x058e] 1422 (23:41)
Day of year: [0x15f] 351 (Day=17, Month=12)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-12-17 23:41:01'411 (deviation -2ms..2ms)