Plum Axe vs Samsung I8530 Galaxy Beam

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

  Axe: 47.3 g lighter

  Axe:

  98 g

  I8530 Galaxy Beam:

  145.3 g

• Depth

  Axe: 2.1 mm thinner

  Axe:

  10.4 mm

  I8530 Galaxy Beam:

  12.5 mm

• Height

  Axe: 2 mm shorter

  Axe:

  122 mm

  I8530 Galaxy Beam:

  124 mm

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. Axe

   Height:

   122 mm

   Width:

   63.6 mm

   Depth:

   10.4 mm

2. 2. I8530 Galaxy Beam

   Height:

   124 mm +2 mm versus Axe

   Width:

   64.2 mm

   Depth:

   12.5 mm +2.1 mm versus Axe

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. Axe

   Screen diagonal:

   4 in

   Aspect ratio (height:width):

   5:3

   Approximate rectangular screen area:

   45.5 cm²

2. 2. I8530 Galaxy Beam

   Screen diagonal:

   4 in

   Aspect ratio (height:width):

   5:3

   Approximate rectangular screen area:

   45.5 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.

No unambiguous storage/RAM pairings are recorded. See the original specifications below.

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.