Interpret a UUID
Back
Your input: f925320a-b604-8710-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:f925320a-b604-8710-87ea-5ce32bd83b97
URI: uuid:f925320a-b604-8710-87ea-5ce32bd83b97
Microsoft GUID syntax: {F925320A-B604-8710-87EA-5CE32BD83B97}
C++ struct syntax: { 0xf925320a, 0xb604, 0x8710, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.331170900903303394016648255748489886615
As OID (Microsoft): 1.2.840.113556.1.8000.2554.63781.12810.46596.34576.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17952810511167162128.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4179964426.3053750032.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.63781.12810.46596.34576.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xf925320ab60471007ea5ce32bd83b97]
Custom data block1 (32 bit): [0xf925320a]
Custom data block2 (16 bit): [0xb604]
Custom data block3 (12 bit): [0x710]
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: [0xf925] 0b1111100100100101
Milliseconds: [0x32] 196 (deviation -2ms..2ms)
Seconds: [0x0a] 10
Minute of day: [0x04b6] 1206 (20:05)
Day of year: [0x107] 263 (Day=20, 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-20 20:05:10'196 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing