Intel Core Ultra 5 236V “Lunar Lake” CPU Spotted On Geekbench, Entry-Level 17W Chip For Thin & Light Laptops

A Lenovo laptop based on Intel's Core Ultra 5 236V "Lunar Lake" CPU was benchmarked on Geekbench today.

The 8-core Intel Core Ultra 5 236V "Lunar Lake" CPU shows up inside a Lenovo-based laptop

This is neither the first nor the last time we are getting leaks about Intel Lunar Lake CPUs. Roughly two weeks back, we saw the performance of Core Ultra 5 256V on Geekbench, outperforming Ryzen 8840HS convincingly in both single and multi-core tests.

Related Story Intel Arrow Lake-S “Core Ultra 9 285K” Desktop CPU Benchmarks Leak: Up To 18% Faster Than 14900K, Scores Over 43K In Cinebench At 250W

This time, we have the leaked benchmark numbers of the Intel Core Ultra 5 236V CPU. The processor is from the Ultra 5 200V series we are seeing in action, used inside a Lenovo laptop planned for release soon.

The Intel Core Ultra 5 236V scored 2021 in single-core and 5743 points in multi-core tests. The operating system was Windows 11 Pro and as we can see from the specs, it boasts a base clock frequency of 2.10 GHz. It is an 8-core/8-thread chip with a maximum frequency of 4.67 GHz (4668 MHz to be precise), coinciding with what is known from the specifications of the Core Ultra 200V lineup. Compared to the Core Ultra 256V, it has a 4 MB less L3 cache(8 MB vs 12 MB on 256V) and slightly slower base/boost clocks.

Despite the same core/thread count, the performance seems to be pretty lackluster compared to what we have seen on the higher-end chips like 256V and 268V. This is probably due to the lower clock speeds as well as the smaller L3 cache size. However, unlike the insignificant performance difference between the Core Ultra 7 256V and Core Ultra 7 268V as seen on Geekbench, the 236V is roughly 45-50% slower than both in multi-core tests.

We do not know if the CPU was benchmarked on the Balanced, High-Performance, or Power-Saver plan due to the absence of such information, and we probably would need a few more benchmark results to conclude. It is also likely that this could be an