Interprete a UUID
Back
Your input: bb1d471d-8605-8414-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:bb1d471d-8605-8414-87e9-5ce32bd83b97
URI: uuid:bb1d471d-8605-8414-87e9-5ce32bd83b97
Microsoft GUID syntax: {BB1D471D-8605-8414-87E9-5CE32BD83B97}
C++ struct syntax: { 0xbb1d471d, 0x8605, 0x8414, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.248717654210853010092767588751397895063
As OID (Microsoft): 1.2.840.113556.1.8000.2554.47901.18205.34309.33812.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13483011051545265172.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3139258141.2248508436.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.47901.18205.34309.33812.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xbb1d471d860541407e95ce32bd83b97]
Custom data block1 (32 bit): [0xbb1d471d]
Custom data block2 (16 bit): [0x8605]
Custom data block3 (12 bit): [0x414]
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: [0xbb1d] 0b1011101100011101
Milliseconds: [0x47] 278 (deviation -2ms..2ms)
Seconds: [0x1d] 29
Minute of day: [0x0586] 1414 (23:33)
Day of year: [0x144] 324 (Day=20, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-11-20 23:33:29'278 (deviation -2ms..2ms)