Interpret a UUID
Back
Your input: 3fe0f128-2e02-820c-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:3fe0f128-2e02-820c-87ea-5ce32bd83b97
URI: uuid:3fe0f128-2e02-820c-87ea-5ce32bd83b97
Microsoft GUID syntax: {3FE0F128-2E02-820C-87EA-5CE32BD83B97}
C++ struct syntax: { 0x3fe0f128, 0x2e02, 0x820c, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.84909329474841824447094897833240181655
As OID (Microsoft): 1.2.840.113556.1.8000.2554.16352.61736.11778.33292.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.4602943974045549068.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1071706408.771916300.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.16352.61736.11778.33292.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x3fe0f1282e0220c07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x3fe0f128]
Custom data block2 (16 bit): [0x2e02]
Custom data block3 (12 bit): [0x20c]
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: [0x3fe0] 0b0011111111100000
Milliseconds: [0xf1] 944 (deviation -2ms..2ms)
Seconds: [0x28] 40
Minute of day: [0x022e] 558 (09:17)
Day of year: [0x0c2] 194 (Day=13, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-13 09:17:40'944 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing