ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

54 Shot Rally between Novak Djokovic and Rafael Nadal (US Open Championship 2013)

Updated on December 12, 2013

Who played the better rally?

See results

Below is a chart of the longest rally of the Men's championship match during the 2013 US Open.

When watching this rally, I remember thinking to myself, "this can't continue!" Little did I know that these two tennis champions were only halfway through what ended up being a phenomenal rally--one that would decide a break point in the second set. Since I love to watch and analyze tennis, as I know others do as well, I decided to create a chart showing the approximate placement of each shot.

At the top of the graphic you'll see a legend. From left to right, the legend defines the shot markers as:

  • BH TS = Backhand Topspin
  • BH Slice = Backhand Slice
  • FH TS = Forehand Topspin
  • FH Slice = Forehand Slice
  • Nadal was on the top of the screen. Djokovic was on the bottom.
  • The markers on the top represent where Djokovic's shots landed.
  • The markers on the bottom represent where Nadal's shots landed.
  • The shot with the green halo won the rally.
  • The shot with the red halo lost the rally.

The markers are teardrop shaped. The point of the tear drop points to the approximate position of the player who struck the ball. This can give us an idea of how many cross court (CC) shots compared to down the line (DTL) shots were hit. You can also glean whether a shot was inside-out (though this is slightly harder to do).

Below the graphic I will break down a few statistics and provide some light commentary. Disclaimer: I did not have access to any of the official ball tracking technology used at the event. I gleaned this data by observing the CBS Broadcast in the United States.

Above is the shot placement chart for the super long rally between Djoker and Rafa, as they are sometimes called. The top half shows where Djokovic's balls landed and the bottom half shows where Nadal's balls landed.
Above is the shot placement chart for the super long rally between Djoker and Rafa, as they are sometimes called. The top half shows where Djokovic's balls landed and the bottom half shows where Nadal's balls landed. | Source
A jubliant Djokovic celebrates after a deep backhand wins him the longest rally of the match.
A jubliant Djokovic celebrates after a deep backhand wins him the longest rally of the match.

Some stats about the longest rally of the match

It's fairly unusual to see rallies of this length during a match of this caliber, during a break point. It was something special, for sure. Usually shot placement charts like this will span a whole game, or sometimes even a set! So to see such a detailed placement chart for one rally is rare.

  1. Djokovic hit 14 backhands.
  2. --> 0% of his BH's were slices.
  3. Djokovic hit 13 forehands.
  4. Nadal hit 17 backhands.
  5. --> 53% (9) of his BH's were slices.
  6. Nadal hit 10 forehands
  7. --> one of them was the slice serve to start the rally.

This rally, in some ways, was a microcosm of the entire match--save the ultimate victor. Nadal dedicated himself to the slice backhand down the line, whereas Djokovic hit extraordinarily few backhand slices.


Was Djokovic's lack of BH Slices during this match a strategic error?

See results

Watch the longest rally of the 2013 US Open Men's Finals match

Here is a video of the remarkable rally, for your reference. The second half of the video shows some highlights of the match. Enjoy!

Disclaimer: I have no affiliation with the publisher of the below YouTube video.

What do you guys think of this rally, or this match?

I'm not a professional tennis pundit, so I'll reserve my commentary of this rally and this match, however, I wouldn't mind hearing what you guys have to say! I know people all over the place, in forums, on social media, and around the watering holes are all discussing this rally, so I figured, "Hey, let's let people look at the shot placement. Hopefully this can add to the conversation."

I hope you enjoyed the article!

Time_Spiraling

Comments

    0 of 8192 characters used
    Post Comment

    • AUPADHYAY profile image

      ANIL KUMAR UPADHYAY 

      4 years ago from INDIA, UTTAR PRADESH STATE, KANPUR CITY

      An interesting hub. Liked it. thanks for sharing it.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)