Interpret a UUID
Back
Your input: 9b03d805-4a03-800b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:9b03d805-4a03-800b-87ea-5ce32bd83b97
URI: uuid:9b03d805-4a03-800b-87ea-5ce32bd83b97
Microsoft GUID syntax: {9B03D805-4A03-800B-87EA-5CE32BD83B97}
C++ struct syntax: { 0x9b03d805, 0x4a03, 0x800b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.206050297656758888294965059975422426007
As OID (Microsoft): 1.2.840.113556.1.8000.2554.39683.55301.18947.32779.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11170009018037141515.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2600720389.1241743371.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.39683.55301.18947.32779.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x9b03d8054a0300b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x9b03d805]
Custom data block2 (16 bit): [0x4a03]
Custom data block3 (12 bit): [0x00b]
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: [0x9b03] 0b1001101100000011
Milliseconds: [0xd8] 846 (deviation -2ms..2ms)
Seconds: [0x05] 5
Minute of day: [0x034a] 842 (14:01)
Day of year: [0x0b0] 176 (Day=25, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-25 14:01:05'846 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing