Ramoth Gilead spelled death for King Ahab

The site of Ramoth Gilead is located in northern Jordan near the Syrian border. The exact site is uncertain, but many scholars think Tall ar-Rumeith is to be identified with the biblical site. Ahab, king of ancient Israel, was concerned because the town of Ramoth Gilead which he claimed for the northern kingdom of Israel was controlled by Syria. Jehoshaphat, the king of Judah, agreed to go with Ahab to fight for Ramoth Gilead.

Camels at Ramoth Gilead.
Camels in the foreground of the site possibly identified with Ramoth Gilead.

The prophets of the day seemed to be indebted to the kings and like good politicians assured them they would prosper in their effort to take the city. One prophet, a man named Micaiah came and told the king that he would not prosper. Micaiah said that he could only speak what the LORD told him.

a-biblical-king-in-his-chariot-going-to-war

AI imagines that King Ahab looked something like this when he headed into battle.

When the kings arrived at Ramoth Gilead Ahab disguised himself and went into battle. He had convinced Jehoshaphat to put on  his robes and go into battle. When the Syrian captains saw him, thinking he was Ahab,  they went after him. When they saw it was not Ahab they turned back.

The Biblical record says that a “certain man drew his bow at random, and struck the King of Israel between the  joins of his armor.” The soldiers of Israel propped up the king in his chariot and he died that evening. Ahab was taken back to Samaria for burial.

No amount of disguise can hide one from the LORD. This is another events that shows that the LORD rules in the kingdoms of men.

Read 1 Kings 22 for the full account of this event.

One response to “Ramoth Gilead spelled death for King Ahab

  1. Thanks! Josephus thought it was Naaman who shot the fateful arrow. 🙂 Drove up a construction road to the top in March 2023, no signage to indicate this was possibly (probably?) the site of an epic battle.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.