Interpret a UUID
Back
Your input: bd5c2504-6000-890b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:bd5c2504-6000-890b-87ea-5ce32bd83b97
URI: uuid:bd5c2504-6000-890b-87ea-5ce32bd83b97
Microsoft GUID syntax: {BD5C2504-6000-890B-87EA-5CE32BD83B97}
C++ struct syntax: { 0xbd5c2504, 0x6000, 0x890b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.251702533310113497409272583497958570903
As OID (Microsoft): 1.2.840.113556.1.8000.2554.48476.9476.24576.35083.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13644821671746504971.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3176932612.1610647819.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.48476.9476.24576.35083.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xbd5c2504600090b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xbd5c2504]
Custom data block2 (16 bit): [0x6000]
Custom data block3 (12 bit): [0x90b]
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: [0xbd5c] 0b1011110101011100
Milliseconds: [0x25] 145 (deviation -2ms..2ms)
Seconds: [0x04] 4
Minute of day: [0x0060] 96 (01:35)
Day of year: [0x0b9] 185 (Day=4, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-04 01:35:04'145 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing