The goddess of Hel, Hela has just gotten married in order to secure her throne! And she got married to a suitor that nobody was expecting.

This happened in the latest Thor #4 issue by Jason Aaron and Mike Del Mundo where Thor and Loki travel to Hel, which is the realm of the dead and also the frontline of the war against Sindr, the daughter of Surtur. Sindr aligns her realm with Malekeith the Accursed. Malekeith is a dark elf who has plunged nearly all 10 realms into a War.

On their arrival, Loki and Thor get reunited with their brother, Balder the Brave, who’s the ruler of Niffleheim and the leader of the dead army in their battle against Sindr. The heroes then stop a shipment towards the opposing forces, what they believed to be a weapon. However, they found out that it carried Loki’s children–former ruler of Hel, Hela and her brother Fenris Wolf.

Fuming with revenge, Hela quickly attacks the Asgardians but Loki stopped the fight and convinced Hela and Balder that Hel needs them all to be united if has any chances of surviving the assault by Sindr. Loki suggested Balder and Hela to marry and co-rule over Hel.

The two reluctantly agreed to Loki’s plan but Hela ignored to mention that she was already in a relationship with Thanos and that’s where her boyfriend shows up.

Upon seeing the Mad Titan, Hela assumes that he’s there to help her regain her throne but she was absolutely wrong; Thanos was just there to dump Hela. He takes out a monster in Sindr’s service and sets on his quest for all the Infinity Stones.

During the preparations of the ceremony, Balder’s lover Karnilla convinces Loki to help her and as Hela and Balder argue over the ceremony, Karnilla slips a ring onto Hela’s finger and says, “I do.” With that, Hela and Karnilla are bounded together as the new co-ruling queens of Hel.

As part of the deal with Loki, Karnilla brings back Balder back to the realm of the living, restoring him to life. Thor #4 is on sale now.

What do you think about this whole situation?

Facebook comments:

Leave a Reply

Adcodes and Instructions provided for: ============================================== ============================================== ======================================== SID 15564 ======================================== PLACE THIS CODE BEFORE THE TAG Edge Ad Code: ======================================== ======================================== ***EDGE Trafficking Instructions:*** ======================================== EDGE ad code should be placed directly on the site within the body at the end of the page. The default EDGE configuration is described below. If you have requested a custom configuration, please disregard default settings below. EDGE can be trafficked through ad servers via javascript tags, 1x1 javascript pixel, or DFP/GPT synchronous tag. In DFP, make sure that SafeFrame is disabled (it is automatically enabled by default), otherwise the tags will not work properly. For DFP/GPT, see this link to "Traffic and serve out-of-page creatives": ======================================== ======================================== ***EDGE Default Configuration:*** ======================================== SLIDER - Rails w/ Content Detect and Footer w/ Ad Detect: - Serve rail placements (160x600, 300x250 and 300x600) for Desktop when open space is available. All sizes are located at the bottom of the window by default. - When rail space is not available, serve 728x90 or 970x90 footer. With Ad Detect enabled for desktop footers, a 728x90 or 970x90 will not be served when it covers a standard IAB format (728x90, 300x250, 160x600, and/or 300x600). ======================================== ======================================== ***EDGE Default Settings:*** ======================================== - Device Targeting: Desktop, Tablet, and Mobile Phone - 100/24 Frequency cap - Minimum Time between EDGE sliders: 3 seconds is the minimum time allowed; may be increased ========================================