Interpret a UUID
Back
Your input: c4203812-f704-8100-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:c4203812-f704-8100-87ea-5ce32bd83b97
URI: uuid:c4203812-f704-8100-87ea-5ce32bd83b97
Microsoft GUID syntax: {C4203812-F704-8100-87EA-5CE32BD83B97}
C++ struct syntax: { 0xc4203812, 0xf704, 0x8100, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.260695977990809597647781700573731502999
As OID (Microsoft): 1.2.840.113556.1.8000.2554.50208.14354.63236.33024.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.14132357284793450752.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3290445842.4144267520.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.50208.14354.63236.33024.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xc4203812f70410007ea5ce32bd83b97]
Custom data block1 (32 bit): [0xc4203812]
Custom data block2 (16 bit): [0xf704]
Custom data block3 (12 bit): [0x100]
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: [0xc420] 0b1100010000100000
Milliseconds: [0x38] 219 (deviation -2ms..2ms)
Seconds: [0x12] 18
Minute of day: [0x04f7] 1271 (21:10)
Day of year: [0x001] 1 (Day=1, Month=1)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-01-01 21:10:18'219 (deviation -2ms..2ms)