Interpret a UUID
Back
Your input: 2a3d7631-bf03-8510-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:2a3d7631-bf03-8510-87ea-5ce32bd83b97
URI: uuid:2a3d7631-bf03-8510-87ea-5ce32bd83b97
Microsoft GUID syntax: {2A3D7631-BF03-8510-87EA-5CE32BD83B97}
C++ struct syntax: { 0x2a3d7631, 0xbf03, 0x8510, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.56146703196966177276382445993719249815
As OID (Microsoft): 1.2.840.113556.1.8000.2554.10813.30257.48899.34064.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.3043718879202477328.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.708671025.3204678928.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.10813.30257.48899.34064.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x2a3d7631bf0351007ea5ce32bd83b97]
Custom data block1 (32 bit): [0x2a3d7631]
Custom data block2 (16 bit): [0xbf03]
Custom data block3 (12 bit): [0x510]
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: [0x2a3d] 0b0010101000111101
Milliseconds: [0x76] 462 (deviation -2ms..2ms)
Seconds: [0x31] 49
Minute of day: [0x03bf] 959 (15:58)
Day of year: [0x105] 261 (Day=18, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-18 15:58:49'462 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing