Interprete a UUID
Back
Your input: 71bb2f33-d901-8016-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:71bb2f33-d901-8016-87e9-5ce32bd83b97
URI: uuid:71bb2f33-d901-8016-87e9-5ce32bd83b97
Microsoft GUID syntax: {71BB2F33-D901-8016-87E9-5CE32BD83B97}
C++ struct syntax: { 0x71bb2f33, 0xd901, 0x8016, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.151174680417289227196239675890901466007
As OID (Microsoft): 1.2.840.113556.1.8000.2554.29115.12083.55553.32790.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.8195195846661341206.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1908092723.3640754198.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.29115.12083.55553.32790.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x71bb2f33d90101607e95ce32bd83b97]
Custom data block1 (32 bit): [0x71bb2f33]
Custom data block2 (16 bit): [0xd901]
Custom data block3 (12 bit): [0x016]
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: [0x71bb] 0b0111000110111011
Milliseconds: [0x2f] 184 (deviation -2ms..2ms)
Seconds: [0x33] 51
Minute of day: [0x01d9] 473 (07:52)
Day of year: [0x160] 352 (Day=18, 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-18 07:52:51'184 (deviation -2ms..2ms)