Interpret a UUID
Back
Your input: 673c140a-9500-800a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:673c140a-9500-800a-87ea-5ce32bd83b97
URI: uuid:673c140a-9500-800a-87ea-5ce32bd83b97
Microsoft GUID syntax: {673C140A-9500-800A-87EA-5CE32BD83B97}
C++ struct syntax: { 0x673c140a, 0x9500, 0x800a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.137222427863945993863407217631202655127
As OID (Microsoft): 1.2.840.113556.1.8000.2554.26428.5130.38144.32778.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.7438842720191283210.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1731990538.2499837962.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.26428.5130.38144.32778.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x673c140a950000a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x673c140a]
Custom data block2 (16 bit): [0x9500]
Custom data block3 (12 bit): [0x00a]
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: [0x673c] 0b0110011100111100
Milliseconds: [0x14] 78 (deviation -2ms..2ms)
Seconds: [0x0a] 10
Minute of day: [0x0095] 149 (02:28)
Day of year: [0x0a0] 160 (Day=9, 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-09 02:28:10'078 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing