Day 3 of the Rawalpindi Test between Pakistan and South Africa turned dramatic when Mohammad Rizwan was at the center of one of the strangest moments seen in recent Test cricket. The usually composed wicketkeeper-batter found himself in an awkward situation after accidentally knocking down the stumps with his bat — only for the umpires to ignore South Africa’s appeal for hit-wicket. What followed was a mix of confusion, laughter, and debate over cricket’s fine print.
The incident occurred late in the day, with Pakistan looking to consolidate their innings after a steady session. Rizwan, known for his calm approach, was facing Keshav Maharaj. On the final delivery of the day, he played a defensive shot toward the off side, and as he stepped back after completing the stroke, his bat clipped the stumps, dislodging the bails. Instantly, South Africa’s wicketkeeper Kyle Verreynne noticed the bails fall and made an animated appeal for hit-wicket. The fielders quickly joined in, confident they had earned a wicket at the stroke of stumps.
However, to their surprise, the on-field umpires remained unmoved. After a brief discussion, the appeal was turned down. The reason, as clarified later, lay in the intricate details of the laws of cricket. According to the MCC’s rules, a batter can only be declared out hit-wicket if they dislodge the stumps while playing the ball, completing their shot, or setting off for a run immediately after playing it. In this case, Rizwan’s action came well after he had played the delivery and had not attempted a run. The ball was considered dead, and therefore, the appeal had no standing.
Adding to the timing confusion was the fact that the incident happened right as the day’s play was being called off. The umpires had already decided to end proceedings for the day when Rizwan’s bat brushed the stumps. Technically, once the umpire signals “time” or declares “stumps,” the ball is no longer in play. That interpretation made it even clearer that Rizwan could not be given out, no matter how strange the visual might have looked.
The South African players were visibly frustrated, arguing that the act occurred before the umpire had called stumps, but the officials remained firm in their decision. Rizwan, on the other hand, appeared momentarily puzzled, realizing only after a few seconds that he had accidentally disturbed the bails. A small smile crossed his face as he walked off, knowing he had escaped an unusual dismissal by the slimmest of margins.
This rare event sparked discussion among commentators and fans alike. Some felt the umpires made the right call by adhering strictly to the law, while others argued that common sense suggested a hit-wicket should count regardless of the timing. It reignited debate about how the “dead ball” rule is applied and whether there is enough clarity in interpreting such moments.
For Rizwan, it was another chapter in his eventful cricketing journey — one that mixed luck with awareness. He continued to display calmness in the following day’s play, ensuring that the bizarre incident did not distract from his batting responsibilities. For South Africa, it was a case of near success turning into disappointment, as they were denied what could have been a crucial breakthrough.
In the end, the Rawalpindi Test’s Day 3 will be remembered not just for the runs and wickets, but for this odd sequence that left fans and players equally bewildered. Cricket, once again, proved why it remains a game full of surprises, where even a momentary lapse or an accidental nudge can lead to a headline — and in this case, a near hit-wicket that wasn’t.