Skip to main content
Complete Olympic Games coverage at your fingertips
Your inside track on the Olympic Games
Enjoy unlimited digital access
$1.99
per week for 24 weeks
Complete Olympic Games coverage at your fingertips
Your inside track onthe Olympics Games
$1.99
per week
for 24 weeks
// //

Immanuel Quickley of the New York Knicks attempts to get past the Raptors' Kyle Lowry during their game at Madison Square Garden on April 11, 2021 in New York City

Rich Schultz/Getty Images

Julius Randle scored 26 points and the New York Knicks recovered after blowing an 18-point lead to beat the Toronto Raptors 102-96 on Sunday night.

RJ Barrett added 19 as the Knicks (27-27) won their second straight to get back to .500. Nerlens Noel finished with nine points, 13 rebounds and four blocked shots.

New York led 66-48 early in the third quarter but lost momentum when the game was delayed because the court was wet. The Raptors used a 37-15 run to surge to a four-point lead with 7 minutes remaining, but Barrett hit a 3-pointer with the Knicks leading by one with 35 seconds to play.

Story continues below advertisement

The Knicks snapped a nine-game losing streak to Toronto. New York had not beaten the Raptors since Nov. 22, 2017, at home.

Gary Trent Jr. had 23 points and Chris Boucher added 17 points and 14 rebounds for Toronto, which scored 87 points in the first half of a rout at Cleveland on Friday but found things much tougher against the Knicks.

Kyle Lowry finished with 19 points in his return to the Raptors’ lineup after missing five consecutive games with a right foot infection.

Toronto’s Malachi Flynn hit back-to-back 3s to give Toronto an 87-83 lead with 8:19 left. The Knicks then put together a 9-0 run to go up 92-87 on Alec Burks’ 3 with 3:34 remaining.

Toronto got as close as 95-94 on Lowry’s layup with 53 seconds before Randle found Barrett for his 3-pointer.

Your Globe

Build your personal news feed

  1. Follow topics and authors relevant to your reading interests.
  2. Check your Following feed daily, and never miss an article. Access your Following feed from your account menu at the top right corner of every page.

Follow topics related to this article:

View more suggestions in Following Read more about following topics and authors
Report an error
Due to technical reasons, we have temporarily removed commenting from our articles. We hope to have this fixed soon. Thank you for your patience. If you are looking to give feedback on our new site, please send it along to feedback@globeandmail.com. If you want to write a letter to the editor, please forward to letters@globeandmail.com.

Welcome to The Globe and Mail’s comment community. This is a space where subscribers can engage with each other and Globe staff. Non-subscribers can read and sort comments but will not be able to engage with them in any way. Click here to subscribe.

If you would like to write a letter to the editor, please forward it to letters@globeandmail.com. Readers can also interact with The Globe on Facebook and Twitter .

Welcome to The Globe and Mail’s comment community. This is a space where subscribers can engage with each other and Globe staff. Non-subscribers can read and sort comments but will not be able to engage with them in any way. Click here to subscribe.

If you would like to write a letter to the editor, please forward it to letters@globeandmail.com. Readers can also interact with The Globe on Facebook and Twitter .

Welcome to The Globe and Mail’s comment community. This is a space where subscribers can engage with each other and Globe staff.

We aim to create a safe and valuable space for discussion and debate. That means:

  • Treat others as you wish to be treated
  • Criticize ideas, not people
  • Stay on topic
  • Avoid the use of toxic and offensive language
  • Flag bad behaviour

If you do not see your comment posted immediately, it is being reviewed by the moderation team and may appear shortly, generally within an hour.

We aim to have all comments reviewed in a timely manner.

Comments that violate our community guidelines will not be posted.

UPDATED: Read our community guidelines here

Discussion loading ...

To view this site properly, enable cookies in your browser. Read our privacy policy to learn more.
How to enable cookies