Celkon A22 vs Celkon A35k

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.

• WeightA35k: 43 g lighterA35k: 102 g · A22: 145 g
• WidthA35k: 4 mm narrowerA35k: 63 mm · A22: 67 mm
• Screen diagonalA35k: 1 in smaller diagonalA35k: 3.5 in · A22: 4.5 in
• DepthA22: 0.8 mm thinnerA22: 9.9 mm · A35k: 10.7 mm
• HeightA35k: 12 mm shorterA35k: 119 mm · A22: 131 mm
• Release year2012 / 2014A22: 2012 · A35k: 2014

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

   Height

   131 mm+12 mm versus A35k

   Width

   67 mm+4 mm versus A35k

   Depth

   9.9 mm

   Weight

   145 g

2. 2. A35k

   Height

   119 mm

   Width

   63 mm

   Depth

   10.7 mm+0.8 mm versus A22

   Weight

   102 g

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. A22 4.5 in · 16:9 About 55.8 cm² rectangular area
2. 2. A35k 3.5 in · 3:2 About 36.5 cm² rectangular area

A22 has approximately 53% more rectangular screen area than A35k.

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.