J.K. Rowling

CARL COURT/AFP/Getty Images

J.K. Rowling would like to ask for your forgiveness.

No, she's not exactly sorry that she hasn't started writing the next Harry Potter. Instead, she's looking back on the tragic deaths that occurred in the pages of her books.

With all of the shocking character endings readers have endured, which one was most upsetting to Rowling? It turns out to involve a Weasley.

"Today I would just like to say: I'm really sorry about Fred," Rowling wrote on Twitter Saturday. "*bows head in acceptance of your reasonable ire*"

Back in the fictional 1998, Fred Weasley died during the Battle of Hogwarts. As to why she chose May 2 to finally reveal the news, Harry Potter fans discovered that Saturday marked the 17th anniversary of the battle.

In another surprise twist, Rowling revealed Fred isn't the only death she is upset over. When one fan asked about Tonks or Lupin, the 49-year-old teased some more confessions in the future.

"I thought I might apologise for one death per anniversary," she tweeted to the curious reader. "Fred was the worst for me, so I started with him."

Ever since her last Harry Potter book, Rowling has been dipping her pen in other subjects. Just last month, her publisher announced a brand-new book titled Very Good Lives. The work will be a print version of the author's famous 2008 Harvard commencement speech.

As to what happened to Harry and friends, readers better hold on tight to any last hope.

"I've always said, I'm not gonna say 'I definitely won't' because I don't see why I should say that," Rowling said on Today.  "I think Harry Potter 8, as in, what happened next to Harry, Ron and Hermoine…I don't think that's going to happen."

  • Share
  • Tweet

We and our partners use cookies on this site to improve our service, perform analytics, personalize advertising, measure advertising performance, and remember website preferences. By using the site, you consent to these cookies. For more information on cookies including how to manage your consent visit our Cookie Policy.