BLU Dash L vs YU Yureka

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

  Dash L: 33 g lighter

  Dash L:

  122 g

  Yureka:

  155 g

• Screen diagonal

  Dash L: 1.5 in smaller diagonal

  Dash L:

  4 in

  Yureka:

  5.5 in

• Chipset

  Dash L:

  Mediatek MT6572 (28 nm)

  Yureka:

  Qualcomm MSM8939 Snapdragon 615 (28 nm)

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. Dash L

   Height:

   126 mm

   Width:

   64 mm

   Depth:

   11 mm

2. 2. Yureka

   Height:

   Unknown

   Width:

   Unknown

   Depth:

   Unknown

   Unavailable dimensions are omitted from the drawing.

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. Dash L

   Screen diagonal:

   4 in

   Aspect ratio (height:width):

   5:3

   Approximate rectangular screen area:

   45.5 cm²

2. 2. Yureka

   Screen diagonal:

   5.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   83.4 cm²

Yureka has approximately 83.1% more rectangular screen area than Dash L.

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.