Emmerdale

Emmerdale John Sugden confirmed as Nate’s k.i.l.l.e.r as grim final moments revealed

Emmerdale aired the truth about John Sugden and his sickening crimes on Thursday, and with that we saw how and why Nate Robinson d.i.e.d on the ITV soap as John k.i.l.l.e.d him

Nate Robinson's death on Emmerdale was finally explained on Thursday night

Nate Robinson’s d.e.a.t.h on Emmerdale was finally explained on Thursday night(Image: ITV)

Nate Robinson’s d.e.a.t.h on Emmerdale was finally explained on Thursday night, as we learned the truth about John Sugden’s secrets.

John is a k.i.l.l.e.r and has targeted multiple villagers including his future mother-in-law Chas Dingle, Jacob Gallagher, and possibly his own fiancé Aaron Dingle. The Aaron scene wasn’t clear, but as we saw John speaking about saving lives it panned back to the moment last year when Aaron was attacked and John saved him.

Whether this was a hint he staged the attack remains to be seen, but what is clear is that not only did he set up Ella Forster and was the person really harassing Chas and her partner Liam Cavanagh, but John is also a k.i.l.l.e.r. We now know that John is the one who k.i.l.l.e.d Nate.

As theories predicted, Nate never left the village back in September and just moments after he last appeared onscreen, he was k.i.ll.e.d. In the episode that aired on Thursday, first available on ITVX on Thursday morning, we saw John making eerie claims about being a hero.

He said there was nothing like saving a life, and that some people can’t be saved. He also claimed “bringing someone back from the d.e.a.d is the most rewarding thing in the world”, while his face made it clear someone had d.i.e.d on the medic’s watch.


READ MORE: Who is John visiting in Emmerdale? Hospital patient ‘is not Aidan Moore’

Emmerdale aired the truth about John Sugden and his sickening crimes

Emmerdale aired the truth about John Sugden and his sickening crimes (Image: ITV)

It soon became very apparent he was possibly talking about the mystery hospital patient he was visiting, but he was most certainly also speaking about Nate. With that we saw flashbacks to Nate’s final moments, and that fateful day in September where we thought he’d left for Shetland.

Nate had just vowed he was leaving the toxic village behind, but new scenes confirmed he was in a bad way after his beating from his father Cain Dingle. John was holding Nate and checking him over, with his head hurting and his body bruised.


John appeared sympathetic and offered to help him, telling him he had something that would make him feel better. By this point we’d also seen he was the person who ‘stalked’ Chas pretending it was Ella, and we also saw his sick plan against Jacob.

Knowing Jacob had a serious nut allergy, he stole his AAI pen before switching the labels on their coffees so that Jacob drank the one with almond milk in it. As Jacob collapsed and lost consciousness after suffering from anaphylactic shock, John delayed helping him and covered his tracks, before rushing to play the hero.

We now know that John is the one who killed Nate

We now know that John is the one who k.i.l.l.e.d Nate(Image: ITV)


But with that, we also saw Nate’s final moments playing out the very day he appeared to leave the village in September, proving John k.i.l.l.e.d him in that final exchange we saw between them. John had said to Jacob he was “not losing him too” as he went to help him, clearly referring to him k.i.l.l.i.n.g Nate.

We saw Nate say he was fine, only for John to fill a syringe with some form of liquid medication before stabbing it into Nate’s neck. Nate screamed out in pain before suddenly collapsing, with John telling him he would feel better now.

Fans have predicted for months that John k.i.l.l.e.d Nate, after he vanished into thin air and his body was discovered in a lake in February. Viewers were left wondering how and why he d.i.e.d, with the episode now revealing his final moments.

 

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button
error: Content is protected !!