Interpret a UUID
Back
Your input: b1322c15-5804-8a06-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:b1322c15-5804-8a06-87ea-5ce32bd83b97
URI: uuid:b1322c15-5804-8a06-87ea-5ce32bd83b97
Microsoft GUID syntax: {B1322C15-5804-8A06-87EA-5CE32BD83B97}
C++ struct syntax: { 0xb1322c15, 0x5804, 0x8a06, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.235533864213910992733055785117771381655
As OID (Microsoft): 1.2.840.113556.1.8000.2554.45362.11285.22532.35334.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.12768316363731405318.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2972855317.1476692486.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.45362.11285.22532.35334.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xb1322c155804a0607ea5ce32bd83b97]
Custom data block1 (32 bit): [0xb1322c15]
Custom data block2 (16 bit): [0x5804]
Custom data block3 (12 bit): [0xa06]
Custom data block4 (14 bit): [0x07ea]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0xb132] 0b1011000100110010
Milliseconds: [0x2c] 172 (deviation -2ms..2ms)
Seconds: [0x15] 21
Minute of day: [0x0458] 1112 (18:31)
Day of year: [0x06a] 106 (Day=16, Month=4)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-04-16 18:31:21'172 (deviation -2ms..2ms)