England pulls off impossible tie against Australia


Recommended Posts

LOL it was australia who saved the match, they got all out for 196 on a pitch where the average score was 251, if it wasnt for hussey in batting, aussies would be all out for 120 and if it wasnt for Mcgrath england wouldnt be 33 for 5

LOL it was australia who saved the match, they got all out for 196 on a pitch where the average score was 251, if it wasnt for hussey in batting, aussies would be all out for 120 and if it wasnt for Mcgrath england wouldnt be 33 for 5

586154289[/snapback]

Average scores of a particular ground dont mean anything, it all depends on the weather conditions. 200 was a good score to defend and Australia was in the driving seat when England was 5 down for 33 with a run rate of 2.5 runs per over.

Australians are known to finish off the tail, arent they ? Sadly their level of cricket isnt like before anyways. They let England walk all over them. Couldnt even stop Giles from getting 30 odd runs in 20 balls with two leading bowlers bowling.

Australia halted in their tracks

Australia have threatened to get away, to start a winning streak that will lead them steamrolling into the main event over the last two weeks - but at each turn they've been held back. First the Bangladesh defeat, then Pietersen at Bristol, then rain at Edgbaston (262 was too many for England under lights), then the Banglas again, at Canterbury this time, refusing to roll over and take a drubbing. Now this.

The pattern was the same: Adam Gilchrist and Matthew Hayden smashed it everywhere in the first six overs. Then Hayden mistimed, Gilchrist scooped, the out-of-touch Ricky Ponting scratched, pulled a great six, then was suffocated down the leg side. The run-a-ball merchant Andrew Symonds came in too early, was not happy with the attacking Test-match field settings and couldn't get it off the square. The Aussies just could not pull away.

Then reality appeared to bite hard and brutally. Australia found the energy and rhythm to put England back where all antipodeans think they belong. England 33 for 5 is, they believe, natural order. But this is New England. England dug in with Paul Collingwood and Geraint Jones mustering a rearguard action. The luck was with them from the moment Jones played at his first five balls and only hit one of them. Then the ball landed in gaps, outside edges went for four and that final ball from McGrath dribbled from Ashley Giles' pad in front of middle stump and was given as runs. By this stage, Ricky Ponting was finished. He only discovered in the press conference after the game that they were not leg byes - greeted with an astonished silence. Glenn McGrath clarified the situation: "I am surprised it was given as runs as it did not hit the bat."

England no longer give up. From the position they found themselves in, to tie the match was beyond astonishing. Australia are firmly within reach. Both captains thought they should have won the match but it was clear that Michael Vaughan was relieved and Ponting numb. Vaughan: "I do not know what to say - a tie in an Australia-England final at Lord's ... I haven't been involved in a tie before." Ponting: "I feel pretty empty at the moment." Both captains praised Jones and Collingwood. "They didn't do much wrong," explained Ponting. And McGrath did seem genuinely surprised by the competitive edge to this England outfit. "They are playing with a lot more confidence and they are more match aware. When you have won as many games as them, you have an edge."

What does it all mean? In truth, England failed to beat Australia at Lord's. Again. Since 1900 the two teams have met here 33 times in all forms of cricket and England have triumphed on only five occasions. But Steve Harmison and Andrew Flintoff have Australia's batsmen in knots, although England haven't exactly mastered McGrath and Lee (who will surely play in the Tests). At the moment, it is not a case of who will make the most runs but who will do least badly. There has been so much made of bowlers gaining a psychological edge over various batsmen that every batsman has a voodoo against every bowler (the exception being Jason Gillespie who is really struggling for form). It is not pretty to watch.

Something England have done well over this two-year renaissance is fight hard. They did bowl superbly. Harmison was terrifying - quick, straight, ruthless. Flintoff miserly, Simon Jones aggressive and bullish after a mauling from Gilchrist in his opening spell. Giles as tight and tedious as ever. These are the figures that matter for the Ashes. And then there was Geraint Jones in a seemingly hopeless situation.

The personal battles are hotting up as well. Flintoff and Lee - Freddie is ahead in this one. McGrath and Trescothick - McGrath has his number. Hayden and Simon Jones - he had a few words during Jones' brief innings. Actually, Hayden and just about anyone, including the kids who hold the flags as the players run onto the field. :rofl:

What can you learn from the NatWest Series about the Ashes? In truth, very little. It looks like it may be the tightest Ashes encounter for 18 years but this probably won't materialise. One-day internationals prove nothing, especially when key personnel change so much (see 1997), and there are still three more to come. Any early psychological or actual (in the case of Hayden) blows that were dealt or felt will mean nothing when the Australians pull on that bloody baggy green for the first Test in front of a packed house at their home from home: Lord's.

Source

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!