Tweets
- Tweets
- Tweets & replies
- Photos & videos
@PGATOUR is blocked
Are you sure you want to view these Tweets? Viewing Tweets won't unblock @PGATOUR.
-
After 18 holes at the
#PGAChamp: 1. Johnson 2. Lingmerth T3. Kuchar, Day, 5 others Scores: http://pgat.us/Scores pic.twitter.com/CCyNhHw3vq -
Afternoon's featured group: Spieth: -1 McIlroy: -1 Johnson: +3
#PGAChamp pic.twitter.com/D0ltOKsixW -
Danny Lee on No. 18 at Whistling Straits...
#PGAChamp pic.twitter.com/HZXDvMmp1G -
Steve Stricker is putting well after changing putters for the first time in 15 years: http://bit.ly/1Kk7DW5 pic.twitter.com/qMc61iBWo8
-
-
Here's the birdie David Lingmerth made to tie the lead at No. 14. http://snpy.tv/1HJrZpN
-
-
Make that five straight for Koepka. After a front-nine 40, he's 5 under on the back.
#PGAChamp pic.twitter.com/Qfs8sseA9a -
-
After shooting 40 on his front nine, Brooks Koepka has made four straight birdies. This chip-in is the latest. http://snpy.tv/1N6guAP
-
-
-
After making his first bogey of the day at No. 11, Jordan chipped in for his first birdie of the day at No. 12. http://snpy.tv/1Kk3Isp
-
-
-
"There is no justice" on this Phil Mickelson approach. http://snpy.tv/1ILJiua
-
-
-
-
Low man on the course: David Lingmerth, who is -5 through 10. No one else is better than -2 this afternoon. pic.twitter.com/584vxDwoM1
-
-
Phil Mickelson is clearly celebrating
#LeftHandersDay. What a shot.#QuickHits http://snpy.tv/1ILypZu
-
-
-
Jordan Spieth flashing some serious touch at No. 6.
#QuickHits http://snpy.tv/1ILtV57
-
-
And of course, Rory makes the putt and saves par from the pond.
#Watery pic.twitter.com/3GOEhpAh49 -
-
Rory McIlroy hit it in the water at No. 5, which didn't stop him from hitting this shot.
#QuickHits http://snpy.tv/1KjPTdi
-
-
-
Dustin on 18: "I don't even know what the carry is on that line... Pulled it and got away with it. I'll take it." pic.twitter.com/T7FSuz9WJO
-
-
The frustration of two bogeys in three holes. pic.twitter.com/HxYo9gVf0g
Play
-
PGA TOUR
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.