- This topic is empty.
April 1, 2022 at 9:39 pm #295SulhazanKeymaster
Hoshea King of Israel who usurped the throne of king Pekah, he was later defeated by the Assyrians when he refused to pay tributes.
But the king of Assyria discovered that Hoshea was a traitor, for he had sent
envoys to So king of Egypt, and he no longer paid tribute to the king of Assyria, as he had done year by year. Therefore Shalmaneser seized him and put him in prison. 2 KINGS 17:4
Based on what we read about him in the Bible, Hoshea must have been a gambler, but it seems his luck—or rather, the mercy of God—ran out when he chose to bet against the king of Assyria.
Hoshea enters the biblical scene as the assassin and usurper of King Pekah of Israel (2 Kings 15:30). This treacherous act alone demonstrates that Hoshea chose to live dangerously and take great risks. The high stakes of his choices become even more apparent, however, when we realize that he did this immediately after the Assyrians had captured much of Israel’s territory and deported many of the people to Assyria (2
Kings 15:29). Hoshea must have known that he was taking over a kingdom that was very much on the ropes with Assyria, and his fate was now tied to Israel’s.
Nevertheless, Hoshea continued taking risks both for himself and for Israel as a nation when he sent secret envoys to Egypt to try to gain their support against Assyria. The risk did not pay off, however, because when he refused to continue paying tribute to Assyria, the Egyptians
failed to show up. The Assyrians came and besieged Hoshea’s capital city of Samaria until it finally fell three years later. The kingdom of Israel came to an end, and the Assyrians deported many Israelites to Assyria and other cities far away.
King Hezekiah of Judah attempted a similar act of refusing to pay tribute to Assyria, but the city of Jerusalem survived due to the Lord’s intervention (2 Kings 18–19). Perhaps this was due to Hezekiah’s dependence upon the Lord, rather than on foreign powers, for help against Assyria.
- You must be logged in to reply to this topic.