Interprete a UUID
Back
Your input: 88ed163a-2102-8812-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:88ed163a-2102-8812-87e9-5ce32bd83b97
URI: uuid:88ed163a-2102-8812-87e9-5ce32bd83b97
Microsoft GUID syntax: {88ED163A-2102-8812-87E9-5CE32BD83B97}
C++ struct syntax: { 0x88ed163a, 0x2102, 0x8812, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.182006032600682084786380536213474392983
As OID (Microsoft): 1.2.840.113556.1.8000.2554.35053.5690.8450.34834.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9866566797556353042.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2297239098.553814034.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.35053.5690.8450.34834.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x88ed163a210281207e95ce32bd83b97]
Custom data block1 (32 bit): [0x88ed163a]
Custom data block2 (16 bit): [0x2102]
Custom data block3 (12 bit): [0x812]
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: [0x88ed] 0b1000100011101101
Milliseconds: [0x16] 86 (deviation -2ms..2ms)
Seconds: [0x3a] 58
Minute of day: [0x0221] 545 (09:04)
Day of year: [0x128] 296 (Day=23, Month=10)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-10-23 09:04:58'086 (deviation -2ms..2ms)