The games

Turn 67 Tap Into a School Break Challenge Without Getting in Trouble

How to run a fair, fast 67 Tap challenge with friends during a school break or free period

· 3 min read · by the 67 team

A group of students in a hallway all tapping their phones with a countdown clock above them

Six seven! Don't just read it: Play 67 Join the chat

A ten minute break is not long enough to do much of anything, except it is exactly long enough for a 67 Tap sprint and some bragging rights before the bell rings.

Why break time is perfect for this

A 67-second sprint fits inside literally any break you have, and the scoring is instant, no waiting for results, no setup beyond opening the game. That makes it one of the few competitive things you can actually finish start to end during a five or ten minute window without cutting it close.

The simplest version: everyone runs one sprint

No teams, no rules beyond one sprint each. Everyone opens 67 Tap, starts their sprint at the same moment (someone counts down "three, two, one, go"), and whoever has the highest score when the timers all hit zero wins bragging rights. It takes barely over a minute total and settles cleanly.

The group version: stack for the country

If your friend group actually cares about the leaderboard and not just personal bragging rights, run it as a group push instead of a competition against each other. Everyone taps for the same 67 seconds, nobody is racing anyone, the only goal is total taps added to your shared country's total in that window. This is a genuinely fun way to feel like your break time did something bigger than kill ten minutes.

Keeping it actually fair

  • Start and stop together. A sprint started thirty seconds before everyone else's is not a fair comparison.
  • No borrowed phones running while someone else holds them. The rate limits exist for a reason and a phone propped against a book tapping itself is not a person playing.
  • Best score counts, not average. Nerves and thumb size vary, one bad start should not sink someone's whole turn.
  • If someone is clearly using an auto-tapper or a script, that run does not count. It is a game between friends, not a coding challenge.

Making it a recurring thing

The best version of this challenge is not a one-off, it is a standing thing your group does every day at the same break. Consistency does more for a rivalry than any single high score does, and 67 Tap saves your personal best on your own device automatically, so you always have a number to beat from the day before.

Reading the room

Not every teacher or supervisor loves phones out during a "break," so use good judgment about when and where this is appropriate. The game itself needs no account and loads instantly, which makes it easy to fit into genuinely free moments, but that is not a reason to push it into times when phones are not supposed to be out at all.

Bring receipts

Screenshot your sprint result before you close the app; the score screen includes a share button specifically for this. Nothing settles a break time argument faster than a screenshot with a timestamp on it.

Rotating who counts down

Give someone different the job of calling the countdown each time your group runs this, so it never feels like one person is controlling the pace to their own advantage. It is a small thing, but a challenge that feels fair is a challenge people actually want to keep doing every day instead of just once.

A version for when only one phone is available

If your group only has one working phone between you at that moment, take turns instead of racing simultaneously. Everyone gets their own 67-second sprint back to back, and whoever ends the round with the best individual score wins. It takes longer than the simultaneous version, but it works with zero setup and no coordination beyond deciding who goes first.

Get your group together for the next break. Tap 67 and see who actually has the fastest thumbs in your year, or organise the whole thing in the chat if your friends need convincing.

More 67