Nokia 800 Tough vs QMobile E1

Key differences

Calculated from recorded specifications using minimum difference thresholds. These are differences, not an overall ranking. For three phones, numeric highlights compare the two extremes.

• Width800 Tough: 9.9 mm narrower800 Tough: 62.1 mm · E1: 72 mm
• Screen diagonal800 Tough: 2.6 in smaller diagonal800 Tough: 2.4 in · E1: 5 in
• ChipsetQualcomm MSM8905 Snapdragon 205 (28 nm) / Mediatek MT6735P (28 nm)800 Tough: Qualcomm MSM8905 Snapdragon 205 (28 nm) · E1: Mediatek MT6735P (28 nm)
• DepthE1: 7.2 mm thinnerE1: 8.9 mm · 800 Tough: 16.1 mm
• Release year2019 / 2017800 Tough: 2019 · E1: 2017

Relative size, not calibrated actual size. Front and side outlines share one scale and a bottom baseline. Generic outlines use recorded body dimensions, excluding camera bumps.

1. 1. 800 Tough

   Height

   145.4 mm

   Width

   62.1 mm

   Depth

   16.1 mm+7.2 mm versus E1

   Weight

   161 g

2. 2. E1

   Height

   143.8 mm

   Width

   72 mm+9.9 mm versus 800 Tough

   Depth

   8.9 mm

   Weight

   Unknown

Screen size

Approximate rectangular screens calculated from recorded diagonal and aspect ratio at one relative scale. Rounded corners and cutouts are not subtracted. These are not phone outlines or calibrated actual sizes.

1. 1. 800 Tough 2.4 in · 4:3 About 17.8 cm² rectangular area
2. 2. E1 5 in · 16:9 About 68.9 cm² rectangular area

E1 has approximately 286.4% more rectangular screen area than 800 Tough.

Memory variants

Each row compares the same storage capacity. Cells show recorded RAM alternatives, not combined maxima. Not recorded does not mean unavailable in every market.

Practical features

Explicit Yes and No values are shown directly. Qualified or regional records retain their details. Unknown means the record is missing.

Battery capacity

Capacity is not battery life. No endurance test is implied.

Open a section for more detail. On narrow screens, swipe sideways or use Left/Right arrow keys while the table is focused. Unknown means missing data, not No. Recorded zero values are shown as recorded.