Interpret a UUID
Back
Your input: f1017b1f-3a03-840a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:f1017b1f-3a03-840a-87ea-5ce32bd83b97
URI: uuid:f1017b1f-3a03-840a-87ea-5ce32bd83b97
Microsoft GUID syntax: {F1017B1F-3A03-840A-87EA-5CE32BD83B97}
C++ struct syntax: { 0xf1017b1f, 0x3a03, 0x840a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.320351636491431928188836422809921534871
As OID (Microsoft): 1.2.840.113556.1.8000.2554.61697.31519.14851.33802.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17366297012164854794.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4043406111.973308938.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.61697.31519.14851.33802.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xf1017b1f3a0340a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xf1017b1f]
Custom data block2 (16 bit): [0x3a03]
Custom data block3 (12 bit): [0x40a]
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: [0xf101] 0b1111000100000001
Milliseconds: [0x7b] 482 (deviation -2ms..2ms)
Seconds: [0x1f] 31
Minute of day: [0x033a] 826 (13:45)
Day of year: [0x0a4] 164 (Day=13, 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-13 13:45:31'482 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing