Popularity · relative index

Based on public voting signals, not player counts.

— / 100Insufficient history
02550751003,0000 CCU2026-08-02 – 2026-08-04 UTC: approximately 1,000 peak concurrent users2026-08-05 – 2026-08-07 UTC: approximately 2,000 peak concurrent users2026-08-08 – 2026-08-10 UTC: approximately 2,000 peak concurrent users2026-08-11 – 2026-08-13 UTC: approximately 2,000 peak concurrent users2026-08-14 – 2026-08-16 UTC: approximately 2,000 peak concurrent users2026-08-17 – 2026-08-19 UTC: approximately 2,000 peak concurrent users2026-08-20 – 2026-08-22 UTC: approximately 2,000 peak concurrent users2026-08-23 – 2026-08-25 UTC: approximately 2,000 peak concurrent users2026-08-26 – 2026-08-28 UTC: approximately 2,000 peak concurrent users2026-08-29 – 2026-08-31 UTC: approximately 2,000 peak concurrent users2026-09-01 – 2026-09-03 UTC: approximately 2,000 peak concurrent users2026-09-04 – 2026-09-06 UTC: approximately 2,000 peak concurrent users2026-09-07 – 2026-09-09 UTC: approximately 2,000 peak concurrent users2026-09-10 – 2026-09-12 UTC: approximately 2,000 peak concurrent users2026-09-13 – 2026-09-15 UTC: approximately 2,000 peak concurrent users2026-09-16 – 2026-09-18 UTC: approximately 2,000 peak concurrent users2026-09-19 – 2026-09-21 UTC: approximately 2,000 peak concurrent users2026-09-22 – 2026-09-24 UTC: approximately 2,000 peak concurrent users2026-09-25 – 2026-09-27 UTC: approximately 2,000 peak concurrent users2026-09-28 – 2026-09-30 UTC: approximately 2,000 peak concurrent users2026-10-01 – 2026-10-03 UTC: approximately 2,000 peak concurrent users2026-10-04 – 2026-10-06 UTC: approximately 2,000 peak concurrent users2026-10-07 – 2026-10-09 UTC: approximately 2,000 peak concurrent users2026-10-10 – 2026-10-12 UTC: approximately 2,000 peak concurrent users2026-10-13 – 2026-10-15 UTC: approximately 3,000 peak concurrent users2026-10-16 – 2026-10-18 UTC: approximately 2,000 peak concurrent users2026-10-19 – 2026-10-21 UTC: approximately 2,000 peak concurrent users2026-10-22 – 2026-10-24 UTC: approximately 2,000 peak concurrent users2026-10-25 – 2026-10-27 UTC: approximately 2,000 peak concurrent users2026-10-28 – 2026-10-30 UTC: approximately 2,000 peak concurrent users (partial period)2026-08-012026-10-29

━ Popularity · index / 100 (left) · ▥ Estimated peak CCU · concurrent users (right)

Three-day maxima, not averages or daily unique players. Periods use UTC; the last source period is incomplete. Historical zero-filled samples are ambiguous and shown as gaps. Values are approximate tiers. Bars at date-range edges may represent a partly visible full source period; the listed dates and tooltip identify the complete aggregation interval.

Latest snapshot: ≈ 1,000 online · 2026-10-29 16:40:00 UTC

Explore the Poki CCU table →
CCU period data · dates and approximate peaks
  • 2026-08-02 – 2026-08-04 UTC: approximately 1,000 peak concurrent users
  • 2026-08-05 – 2026-08-07 UTC: approximately 2,000 peak concurrent users
  • 2026-08-08 – 2026-08-10 UTC: approximately 2,000 peak concurrent users
  • 2026-08-11 – 2026-08-13 UTC: approximately 2,000 peak concurrent users
  • 2026-08-14 – 2026-08-16 UTC: approximately 2,000 peak concurrent users
  • 2026-08-17 – 2026-08-19 UTC: approximately 2,000 peak concurrent users
  • 2026-08-20 – 2026-08-22 UTC: approximately 2,000 peak concurrent users
  • 2026-08-23 – 2026-08-25 UTC: approximately 2,000 peak concurrent users
  • 2026-08-26 – 2026-08-28 UTC: approximately 2,000 peak concurrent users
  • 2026-08-29 – 2026-08-31 UTC: approximately 2,000 peak concurrent users
  • 2026-09-01 – 2026-09-03 UTC: approximately 2,000 peak concurrent users
  • 2026-09-04 – 2026-09-06 UTC: approximately 2,000 peak concurrent users
  • 2026-09-07 – 2026-09-09 UTC: approximately 2,000 peak concurrent users
  • 2026-09-10 – 2026-09-12 UTC: approximately 2,000 peak concurrent users
  • 2026-09-13 – 2026-09-15 UTC: approximately 2,000 peak concurrent users
  • 2026-09-16 – 2026-09-18 UTC: approximately 2,000 peak concurrent users
  • 2026-09-19 – 2026-09-21 UTC: approximately 2,000 peak concurrent users
  • 2026-09-22 – 2026-09-24 UTC: approximately 2,000 peak concurrent users
  • 2026-09-25 – 2026-09-27 UTC: approximately 2,000 peak concurrent users
  • 2026-09-28 – 2026-09-30 UTC: approximately 2,000 peak concurrent users
  • 2026-10-01 – 2026-10-03 UTC: approximately 2,000 peak concurrent users
  • 2026-10-04 – 2026-10-06 UTC: approximately 2,000 peak concurrent users
  • 2026-10-07 – 2026-10-09 UTC: approximately 2,000 peak concurrent users
  • 2026-10-10 – 2026-10-12 UTC: approximately 2,000 peak concurrent users
  • 2026-10-13 – 2026-10-15 UTC: approximately 3,000 peak concurrent users
  • 2026-10-16 – 2026-10-18 UTC: approximately 2,000 peak concurrent users
  • 2026-10-19 – 2026-10-21 UTC: approximately 2,000 peak concurrent users
  • 2026-10-22 – 2026-10-24 UTC: approximately 2,000 peak concurrent users
  • 2026-10-25 – 2026-10-27 UTC: approximately 2,000 peak concurrent users
  • 2026-10-28 – 2026-10-30 UTC: approximately 2,000 peak concurrent users (partial period)
Popularity data · dates and index values
  • 2026-08-01 UTC: Insufficient data
  • 2026-08-02 UTC: Insufficient data
  • 2026-08-03 UTC: Insufficient data
  • 2026-08-04 UTC: Insufficient data
  • 2026-08-05 UTC: Insufficient data
  • 2026-08-06 UTC: Insufficient data
  • 2026-08-07 UTC: Insufficient data
  • 2026-08-08 UTC: Insufficient data
  • 2026-08-09 UTC: Insufficient data
  • 2026-08-10 UTC: Insufficient data
  • 2026-08-11 UTC: Insufficient data
  • 2026-08-12 UTC: Insufficient data
  • 2026-08-13 UTC: Insufficient data
  • 2026-08-14 UTC: Insufficient data
  • 2026-08-15 UTC: Insufficient data
  • 2026-08-16 UTC: Insufficient data
  • 2026-08-17 UTC: Insufficient data
  • 2026-08-18 UTC: Insufficient data
  • 2026-08-19 UTC: Insufficient data
  • 2026-08-20 UTC: Insufficient data
  • 2026-08-21 UTC: Insufficient data
  • 2026-08-22 UTC: Insufficient data
  • 2026-08-23 UTC: Insufficient data
  • 2026-08-24 UTC: Insufficient data
  • 2026-08-25 UTC: Insufficient data
  • 2026-08-26 UTC: Insufficient data
  • 2026-08-27 UTC: Insufficient data
  • 2026-08-28 UTC: Insufficient data
  • 2026-08-29 UTC: Insufficient data
  • 2026-08-30 UTC: Insufficient data
  • 2026-08-31 UTC: Insufficient data
  • 2026-09-01 UTC: Insufficient data
  • 2026-09-02 UTC: Insufficient data
  • 2026-09-03 UTC: Insufficient data
  • 2026-09-04 UTC: Insufficient data
  • 2026-09-05 UTC: Insufficient data
  • 2026-09-06 UTC: Insufficient data
  • 2026-09-07 UTC: Insufficient data
  • 2026-09-08 UTC: Insufficient data
  • 2026-09-09 UTC: Insufficient data
  • 2026-09-10 UTC: Insufficient data
  • 2026-09-11 UTC: Insufficient data
  • 2026-09-12 UTC: Insufficient data
  • 2026-09-13 UTC: Insufficient data
  • 2026-09-14 UTC: Insufficient data
  • 2026-09-15 UTC: Insufficient data
  • 2026-09-16 UTC: Insufficient data
  • 2026-09-17 UTC: Insufficient data
  • 2026-09-18 UTC: Insufficient data
  • 2026-09-19 UTC: Insufficient data
  • 2026-09-20 UTC: Insufficient data
  • 2026-09-21 UTC: Insufficient data
  • 2026-09-22 UTC: Insufficient data
  • 2026-09-23 UTC: Insufficient data
  • 2026-09-24 UTC: Insufficient data
  • 2026-09-25 UTC: Insufficient data
  • 2026-09-26 UTC: Insufficient data
  • 2026-09-27 UTC: Insufficient data
  • 2026-09-28 UTC: Insufficient data
  • 2026-09-29 UTC: Insufficient data
  • 2026-09-30 UTC: Insufficient data
  • 2026-10-01 UTC: Insufficient data
  • 2026-10-02 UTC: Insufficient data
  • 2026-10-03 UTC: Insufficient data
  • 2026-10-04 UTC: Insufficient data
  • 2026-10-05 UTC: Insufficient data
  • 2026-10-06 UTC: Insufficient data
  • 2026-10-07 UTC: Insufficient data
  • 2026-10-08 UTC: Insufficient data
  • 2026-10-09 UTC: Insufficient data
  • 2026-10-10 UTC: Insufficient data
  • 2026-10-11 UTC: Insufficient data
  • 2026-10-12 UTC: Insufficient data
  • 2026-10-13 UTC: Insufficient data
  • 2026-10-14 UTC: Insufficient data
  • 2026-10-15 UTC: Insufficient data
  • 2026-10-16 UTC: Insufficient data
  • 2026-10-17 UTC: Insufficient data
  • 2026-10-18 UTC: Insufficient data
  • 2026-10-19 UTC: Insufficient data
  • 2026-10-20 UTC: Insufficient data
  • 2026-10-21 UTC: Insufficient data
  • 2026-10-22 UTC: Insufficient data
  • 2026-10-23 UTC: Insufficient data
  • 2026-10-24 UTC: Insufficient data
  • 2026-10-25 UTC: Insufficient data
  • 2026-10-26 UTC: Insufficient data
  • 2026-10-27 UTC: Insufficient data
  • 2026-10-28 UTC: Insufficient data
  • 2026-10-29 UTC: Insufficient data

N New label observed

The recorded Poki feed provides new-label observations only; hot and staff-picked observations are not available from this source.

Markers are positive daily observations from the portal API, not entry or exit dates or continuous placement. Hot does not prove a popular-list position; staff-picked does not prove homepage placement. These observations do not establish a cause for popularity changes.

No recorded label observations in this range. This does not prove that the game was never listed.

Insufficient historyNo reliable popularity values in this range. Missing data is not zero.
Last observed: Coverage 3/31 days570 comparable games
ⓘ About this index
Custom date range
Reset

About Temple Run 2

About Temple Run 2

Grab the golden idol and get ready to jump gaps and avoid traps like fire pits and rotating spikes. The game gets faster the longer you run. One mistake and the monkey will catch you.

Play Temple Run 2 and see why over 2 million other players have upvoted it!

How Temple Run 2 works

In Temple Run 2, your character runs automatically. React before each obstacle reaches you by jumping, sliding or changing lanes at the right moment.

The 4 actions you use in every run:

Jump: Clear barriers, traps and holes in the path.

Slide: Duck under low obstacles and overhanging gates.

Turn: Change direction at sharp corners.

Change lanes: Shift left or right to collect coins and avoid obstacles.

The game starts slow. After the first 500 meters, the run speeds up and obstacles start appearing faster.

By 2,000 meters, the run becomes fast enough that even a small delay can end it.

Controls

Desktop:

Up arrow to jump

Down arrow to slide

Left and right arrows to turn and change lanes

Mobile:

Swipe up to jump

Swipe down to slide

Swipe left or right to turn and change lanes

Obstacles and difficulty

These are the 5 types of obstacles you encounter in every run:

Traps: Jump over spinning blades, spiked logs, fire pits and fire-breathing statues.

Low gates and fallen trees: Jumping over these is not possible, you need to slide under them.

Sharp turns: Left or right turns in the path that come up fast.

Broken pathways: Jump or change lanes to avoid holes and broken parts of the path.

Zip-lines, mine carts and rivers: Short sections where movement changes. You steer a mine cart, slide down a zip-line or swim side to side.

Temple Run 2 maps

In Temple Run 2, you run on the Sky Summit map. This is the original map from the 2013 release.

At Poki, you can also play 4 additional Temple Run 2 maps as separate games. Each has its own obstacles and visual themes.

Frozen Shadows adds icy caves and frozen water slides.

Spooky Summit is a Halloween-themed version of Sky Summit.

Jungle Fall takes you through dense jungle ruins.

Holi Festival covers the path in colour and festival obstacles.

Temple Run 2 power-ups

Temple Run 2 has 3 power-ups. You can spend coins in the "Abilities" menu to improve each power-up.

Coin Magnet: Pulls nearby coins toward you for a short time.

Shield: Blocks one obstacle hit. It does not protect against falls.

Boost: Lets you move faster and pass through obstacles.

Who created Temple Run 2?

Temple Run 2 was developed by Imangi Studios and released in 2013, following the success of the original Temple Run from 2011.

By 2018, Temple Run 2 passed 500 million downloads on Google Play, making it one of the most downloaded mobile games of all time.

Temple Run 2 is available as a mobile app on both iOS and Android.

Games like Temple Run 2

Check out the games below if you enjoy skill games built around avoiding obstacles and surviving longer as the speed keeps increasing.

The Dinosaur Game is an endless runner where you jump over cacti as the speed increases.

Subway Surfers is another endless runner where you switch lanes to avoid trains and barriers as the speed increases.

Description from poki.com ↗

Explore similar ideas

See all Poki games →

Murder

actionPokiPoki
1K CCU
Popularity100Stable
Murder: popularity over the last 30 days. Daily rolling vote-rate percentile within the same portal, on a fixed 0–100 scale. 30 of 30 daily values available. Missing values are gaps, not zero.2026-09-30: 99.8 / 1002026-10-01: 99.8 / 1002026-10-02: 100 / 1002026-10-03: 100 / 1002026-10-04: 100 / 1002026-10-05: 100 / 1002026-10-06: 100 / 1002026-10-07: 100 / 1002026-10-08: 100 / 1002026-10-09: 100 / 1002026-10-10: 100 / 1002026-10-11: 100 / 1002026-10-12: 99.8 / 1002026-10-13: 99.8 / 1002026-10-14: 99.8 / 1002026-10-15: 99.8 / 1002026-10-16: 100 / 1002026-10-17: 100 / 1002026-10-18: 100 / 1002026-10-19: 100 / 1002026-10-20: 100 / 1002026-10-21: 100 / 1002026-10-22: 100 / 1002026-10-23: 100 / 1002026-10-24: 100 / 1002026-10-25: 100 / 1002026-10-26: 100 / 1002026-10-27: 100 / 1002026-10-28: 100 / 1002026-10-29: 100 / 100

Hole.io

3dPokiPoki
5K CCU
Popularity100Partial history
Hole.io: popularity over the last 30 days. Daily rolling vote-rate percentile within the same portal, on a fixed 0–100 scale. 18 of 30 daily values available. Missing values are gaps, not zero.2026-10-12: 100 / 1002026-10-13: 100 / 1002026-10-14: 100 / 1002026-10-15: 100 / 1002026-10-16: 99.8 / 1002026-10-17: 99.8 / 1002026-10-18: 99.8 / 1002026-10-19: 99.8 / 1002026-10-20: 99.8 / 1002026-10-21: 99.8 / 1002026-10-22: 99.8 / 1002026-10-23: 99.8 / 1002026-10-24: 99.8 / 1002026-10-25: 99.8 / 1002026-10-26: 99.8 / 1002026-10-27: 99.8 / 1002026-10-28: 99.8 / 1002026-10-29: 99.8 / 100

Subway Surfers

actionPokiPoki
10K CCU
Popularity100Stable
Subway Surfers: popularity over the last 30 days. Daily rolling vote-rate percentile within the same portal, on a fixed 0–100 scale. 30 of 30 daily values available. Missing values are gaps, not zero.2026-09-30: 100 / 1002026-10-01: 100 / 1002026-10-02: 99.8 / 1002026-10-03: 99.8 / 1002026-10-04: 99.8 / 1002026-10-05: 99.8 / 1002026-10-06: 99.8 / 1002026-10-07: 99.8 / 1002026-10-08: 99.8 / 1002026-10-09: 99.8 / 1002026-10-10: 99.8 / 1002026-10-11: 99.8 / 1002026-10-12: 99.6 / 1002026-10-13: 99.6 / 1002026-10-14: 99.6 / 1002026-10-15: 99.6 / 1002026-10-16: 99.6 / 1002026-10-17: 99.6 / 1002026-10-18: 99.6 / 1002026-10-19: 99.6 / 1002026-10-20: 99.6 / 1002026-10-21: 99.6 / 1002026-10-22: 99.6 / 1002026-10-23: 99.6 / 1002026-10-24: 99.6 / 1002026-10-25: 99.6 / 1002026-10-26: 99.6 / 1002026-10-27: 99.6 / 1002026-10-28: 99.6 / 1002026-10-29: 99.6 / 100

Aquapark.io

racingPokiPoki
5K CCU
Popularity100Partial history
Aquapark.io: popularity over the last 30 days. Daily rolling vote-rate percentile within the same portal, on a fixed 0–100 scale. 15 of 30 daily values available. Missing values are gaps, not zero.2026-10-15: 98.4 / 1002026-10-16: 98.4 / 1002026-10-17: 98.4 / 1002026-10-18: 98.4 / 1002026-10-19: 98.6 / 1002026-10-20: 99 / 1002026-10-21: 99 / 1002026-10-22: 99 / 1002026-10-23: 99 / 1002026-10-24: 99.2 / 1002026-10-25: 99.2 / 1002026-10-26: 99.2 / 1002026-10-27: 99.3 / 1002026-10-28: 99.5 / 1002026-10-29: 99.5 / 100

Recommendations share a recorded category on the same portal. No inferred game mechanics are shown.