BRAMPTON, Ont. — Ryan Obuchowski scored at the 2 minute, 16 second mark of overtime Friday to help the Toledo Walleye down the Brampton Beast 2-1 at the Powerade Centre.
Kevin Tansey scored in regulation for the Walleye (26-12-4), who improved to 11-8-2 away from home.
Toledo's Ryan Obuchowski (14) scored the winning shot Friday against the Brampton Beast in Brampton, Ont.
Vincent Dunn tallied the only goal of the game for the Beast (17-18-5), who fell to 10-10-2 on home ice.
It was the third meeting of the season between the two teams. Toledo had taken the first two games, winning 3-1 on Nov. 26 and 5-2 on Dec. 15. The Walleye are now an impressive 23-3-2 all-time against the Beast.
Tansey got Toledo going early, scoring his seventh goal of the season just 31 seconds into the contest. He was assisted by Tyler Barnes and Dylan Sadowy.
But Dunn got the equalizer at the 2:49 mark of the second period on the power play. It was his fourth of the year, assisted by Chris Leveille and Brandon Marino.
The teams didn’t score in the third period, setting up the extra period heroics by Obuchowski. He was assisted on the goal by Sadowy and Erik Bradford.
Toledo outshot Brampton in the game 36-32. The Beast were 1-for-4 on the power play, while the Walleye were 0-for-3.
Matej Machovsky stopped 31 of 32 shots to improve to 8-7-1 on the season for Toledo. Zachary Fucale had 34 saves for Brampton.
The Walleye completed their five-game road swing with two wins, two regulation losses, and a shootout loss.
The two teams will play again at 7:15 p.m. Saturday at the Huntington Center. The Walleye then will finish off the weekend by hosting Cincinnati at 5:15 p.m. Sunday.
Guidelines: Please keep your comments smart and civil. Don't attack other readers personally, and keep your language decent. Comments that violate these standards, or our privacy statement or visitor's agreement, are subject to being removed and commenters are subject to being banned. To post comments, you must be a registered user on toledoblade.com. To find out more, please visit the FAQ.