Nokia N72 vs Samsung i620

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.

• Width

  N72: 6.3 mm narrower

  N72:

  53 mm

  i620:

  59.3 mm

• Depth

  i620: 5.5 mm thinner

  N72:

  21.8 mm

  i620:

  16.3 mm

• Height

  i620: 14.1 mm shorter

  N72:

  109 mm

  i620:

  94.9 mm

• Release year

  N72:

  2006

  i620:

  2007

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

   Height:

   109 mm +14.1 mm versus i620

   Width:

   53 mm

   Depth:

   21.8 mm +5.5 mm versus i620

2. 2. i620

   Height:

   94.9 mm

   Width:

   59.3 mm +6.3 mm versus N72

   Depth:

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

At least two phones need compatible screen dimensions for a drawing.

1. 1. N72

   N72: Screen geometry unavailable or conflicting.

2. 2. i620

   Screen diagonal:

   2.2 in

   Aspect ratio (height:width):

   4:3

   Approximate rectangular screen area:

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