Interpret a UUID
Back
Your input: f0ca2d1d-5c04-8314-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:f0ca2d1d-5c04-8314-87ea-5ce32bd83b97
URI: uuid:f0ca2d1d-5c04-8314-87ea-5ce32bd83b97
Microsoft GUID syntax: {F0CA2D1D-5C04-8314-87EA-5CE32BD83B97}
C++ struct syntax: { 0xf0ca2d1d, 0x5c04, 0x8314, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.320064477988330797532291807272393784215
As OID (Microsoft): 1.2.840.113556.1.8000.2554.61642.11549.23556.33556.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17350730118519358228.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4039781661.1543799572.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.61642.11549.23556.33556.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xf0ca2d1d5c0431407ea5ce32bd83b97]
Custom data block1 (32 bit): [0xf0ca2d1d]
Custom data block2 (16 bit): [0x5c04]
Custom data block3 (12 bit): [0x314]
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: [0xf0ca] 0b1111000011001010
Milliseconds: [0x2d] 176 (deviation -2ms..2ms)
Seconds: [0x1d] 29
Minute of day: [0x045c] 1116 (18:35)
Day of year: [0x143] 323 (Day=19, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-11-19 18:35:29'176 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing