Fantasy #1 Contender Tournament Round 1: #3 Josh Koscheck vs. #14 Anthony Johnson
The UFC Welterweight Division has a plethora of young talent, a dominating champion, and many exciting match ups to choose from, but the one thing they lack is a true number one contender. I doubt the UFC would ever put together a welterweight tournament to determine a true number one contender (oh do I hope to be wrong), but we at WKR can have our own virtual (we're dorks, deal with it) tournament. The bracket and rankings have been set and it is time to begin the tournament. Let your vote choose who wins the most prestigious, meaningless, fake, yet enjoyable UFC Welterweight number 1 contender tournament.
The next match up is between #3 ranked Josh Koscheck and #14 Anthony Johnson. Fighter details after the jump.
Josh Koscheck 13-4 (11-4 UFC): TUF 1 participant Josh Koscheck has had a very successful UFC career and was being lined up for a title fight and rematch against George St. Pierre until he had cartoon birdies circle his head thanks to Paulo Thiago. Koscheck is coming off a give me win over UFC Nostalgia Fighter Frank Trigg. Koscheck is very athletic, powerful, and a great wrestler. However, he has a tendency to become in love with the KO when dominating wrestling is his best weapon. Cleaning up his striking and sticking to a game plan would help Josh get to the top.
Anthony Johnson 7-2 (4-2* UFC): Johnson is arguably the most exciting fighter in the whole UFC. One of those losses is via eye poke (accidental) to Kevin Burns which should have been changed to a no contest. However, it was kept on the records as a loss and Johnson had to avenge the loss, which he did via TKO. Johnson is young, athletic, packs unreal power, quickness, has a good wrestling base, and the UFC has high hopes for his future. However, he has yet to be tested and the UFC continues to take it slow with him by matching him up against one dimensional fighters. Case in point, his next opponent Yoshiyuki Yoshida.
#7 Paulo Thiago vs. #10 Carlos Condit
0 recs |
1 comment
|

by 


















