Interpret a UUID
Back
Your input: b7c52603-a701-8b0e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:b7c52603-a701-8b0e-87ea-5ce32bd83b97
URI: uuid:b7c52603-a701-8b0e-87ea-5ce32bd83b97
Microsoft GUID syntax: {B7C52603-A701-8B0E-87EA-5CE32BD83B97}
C++ struct syntax: { 0xb7c52603, 0xa701, 0x8b0e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.244272376730706254333459842073605192599
As OID (Microsoft): 1.2.840.113556.1.8000.2554.47045.9731.42753.35598.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13242032076481465102.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3083150851.2801896206.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.47045.9731.42753.35598.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xb7c52603a701b0e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xb7c52603]
Custom data block2 (16 bit): [0xa701]
Custom data block3 (12 bit): [0xb0e]
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: [0xb7c5] 0b1011011111000101
Milliseconds: [0x26] 149 (deviation -2ms..2ms)
Seconds: [0x03] 3
Minute of day: [0x01a7] 423 (07:02)
Day of year: [0x0eb] 235 (Day=23, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-23 07:02:03'149 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing