Interpret a UUID
Back
Your input: 5f161a33-3e03-8a13-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:5f161a33-3e03-8a13-87ea-5ce32bd83b97
URI: uuid:5f161a33-3e03-8a13-87ea-5ce32bd83b97
Microsoft GUID syntax: {5F161A33-3E03-8A13-87EA-5CE32BD83B97}
C++ struct syntax: { 0x5f161a33, 0x3e03, 0x8a13, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.126391421532933106737840335575565482903
As OID (Microsoft): 1.2.840.113556.1.8000.2554.24342.6707.15875.35347.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.6851692690476861971.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1595284019.1040419347.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.24342.6707.15875.35347.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x5f161a333e03a1307ea5ce32bd83b97]
Custom data block1 (32 bit): [0x5f161a33]
Custom data block2 (16 bit): [0x3e03]
Custom data block3 (12 bit): [0xa13]
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: [0x5f16] 0b0101111100010110
Milliseconds: [0x1a] 102 (deviation -2ms..2ms)
Seconds: [0x33] 51
Minute of day: [0x033e] 830 (13:49)
Day of year: [0x13a] 314 (Day=10, 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-10 13:49:51'102 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing