Oct 29, 2026 5:14 PM
The Leafs say Marchenko is week-to-week with a lower-body injury, but moving him to injured reserve opens up a spot for another potential return.
SEATTLE — One day after the Toronto Maple Leafs revealed that Kirill Marchenko will be out of the lineup week-to-week with a lower-body injury, the club has officially placed the forward on injured reserve.
Why would they do this?
Knowing they’ll be without Marchenko for at least a week, there’s no harm in placing him on injured reserve, which requires a player to miss a minimum of seven days. The forward has already returned home, so he was not going to be available for their game against the Vancouver Canucks on Saturday. That would make Marchenko unavailable until Toronto’s game at home on Nov. 3 against the Seattle Kraken.
By placing Marchenko on IR, the club has opened up a roster spot. Following the activation of Dakota Joshua from long-term injured reserve, the club was at the maximum 23 players. But if the Leafs are ready for a player to come off the IR, they’d need that open spot.
With Chris Tanev upgraded to day-to-day and a full participant at the morning skate on Wednesday, the defenseman may be available for Saturday’s game against the Canucks. That’s where that additional roster spot would come in handy by moving Marchenko to IR.
Marchenko was injured when his left leg appeared to bend awkwardly following a collision with Calgary Flames forward Yegor Sharangovich. Acquired in September in a blockbuster trade with the Columbus Blue Jackets that saw fan favorite Matthew Knies part ways in return, the 26-year-old has six goals and eight assists in 14 games this season, while averaging 17:37 of ice time.
See more of The Hockey News on Google — Save us as Preferred Source

For action-packed issues, access to the entire magazine archive and a free issue, subscribe to The Hockey News at THN.com/free. Get the latest news and trending stories by subscribing to our newsletter here. And share your thoughts by commenting below the article on THN.com or creating your own post in our community forum.
2
Comments
Powered by RoundtableAn AI/DeFi-powered Enterprise Media Operating System. Learn more at Roundtable.io.© Roundtable 2026. By using this site you agree to the Terms of Use and Privacy Policy


