Xiaomi Redmi 3 vs YU Yureka Black

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.

• Weight

  Redmi 3: 8 g lighter

  Redmi 3:

  144 g

  Yureka Black:

  152 g

• Chipset

  Redmi 3:

  Qualcomm MSM8939v2 Snapdragon 616 (28 nm)

  Yureka Black:

  Qualcomm MSM8937 Snapdragon 430 (28 nm)

• Height

  Redmi 3: 2.7 mm shorter

  Redmi 3:

  139.3 mm

  Yureka Black:

  142 mm

• Release year

  Redmi 3:

  2016

  Yureka Black:

  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. Redmi 3

   Height:

   139.3 mm

   Width:

   69.6 mm

   Depth:

   8.5 mm

2. 2. Yureka Black

   Height:

   142 mm +2.7 mm versus Redmi 3

   Width:

   69.6 mm

   Depth:

   8.7 mm

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. Redmi 3

   Screen diagonal:

   5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   68.9 cm²

2. 2. Yureka Black

   Screen diagonal:

   5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   68.9 cm²

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.