Asus ROG Phone 3 vs LG K50S

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.

• Display technology

  OLED versus LCD

  ROG Phone 3:

  OLED

  K50S:

  LCD

• Depth

  K50S: 1.7 mm thinner

  ROG Phone 3:

  9.9 mm

  K50S:

  8.2 mm

• Height

  K50S: 5.2 mm shorter

  ROG Phone 3:

  171 mm

  K50S:

  165.8 mm

• Release year

  ROG Phone 3:

  2020

  K50S:

  2019

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. ROG Phone 3

   Height:

   171 mm +5.2 mm versus K50S

   Width:

   78 mm

   Depth:

   9.9 mm +1.7 mm versus K50S

   Weight:

   240 g

2. 2. K50S

   Height:

   165.8 mm

   Width:

   77.5 mm

   Depth:

   8.2 mm

   Weight:

   Unknown

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. ROG Phone 3

   Screen diagonal:

   6.59 in

   Aspect ratio (height:width):

   19.5:9

   Approximate rectangular screen area:

   106.6 cm²

2. 2. K50S

   Screen diagonal:

   6.5 in

   Aspect ratio (height:width):

   19:9

   Approximate rectangular screen area:

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

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.