1 Chronicles 2:44's role in Israel's lineage?
What is the significance of 1 Chronicles 2:44 in the genealogy of the tribes of Israel?

Text and Context

“Shema was the father of Raham, the father of Jorkeam; Rekem was the father of Shammai.” (1 Chronicles 2:44)

This statement sits inside the extended Judahite genealogy (1 Chronicles 2:1-55) that moves from Judah, through Hezron, Caleb, Jerahmeel, and their collateral lines, down to David. Verse 44 belongs to the Caleb-via-Hebron sub-list (vv 42-49).


Caleb’s Hebronite Branch within Judah

1. Judah

2. Hezron

3. Caleb (Hezron’s son; v 18)

4. Hebron (Caleb’s son; v 42)

5. Hebron’s sons: Korah, Tappuah, Rekem, Shema (v 43)

 • From Shema → Raham → Jorkeam (v 44a)

 • From Rekem → Shammai → Maon → Beth-zur (vv 44b-45)

Thus v 44 preserves two tributaries of an otherwise unrecorded Hebronite line that occupied territory south of Jerusalem. This detail shows that the Chronicler is not merely recounting royal pedigree but mapping the clan structure that once organized land tenure (cf. Joshua 15:52-55).


Geographical Corroboration

• Jokmeam/Jorkeam appears as a Levitical town in Ephraimite territory (1 Kings 4:12; Joshua 21:22). Its dual listing (Ephraim/Judah) is explained by the post-conquest resettlement of Calebite clans in border regions—consistent with the Tell Yoqneʿam strata dated to Iron I-II showing rapid Judahite material culture influx (ceramic typology, four-room houses).

• Maon and Beth-zur (vv 45) sit atop the Hebron plateau; both sites have yielded Late Bronze/Iron I fortifications matching Joshua-Judges chronology (Beth-zur: 10th-century casemate wall, Maon: early Iron II watchtower). Their linkage to Shammai supports the Chronicler’s historic memory.


Why the Chronicler Includes Obscure Names

1. Land Tenure Ledger: Post-exilic returnees needed legal precedent to reclaim ancestral allotments (cf. Nehemiah 7:5).

2. Covenant Continuity: Demonstrates that God preserved every family line despite exile (Jeremiah 33:26).

3. Messianic Trajectory: The Chronicler subtly affirms that God’s promise to David (2 Samuel 7) rests on the broader, intact Judahite tree—preventing the charge of genealogical gap.

4. Ecclesial Identity: Early Christians used such records to authenticate Jesus as “the Lion of the tribe of Judah” (Revelation 5:5). Matthew’s genealogy contracts but relies on Chronicler-style archives for its backbone (Matthew 1:1-17; compare 1 Chronicles 2:9-15).


Practical Implications

• God sees and records every lineage; no believer is invisible.

• Divine compassion (Raham) and hearing (Shammai) run through ordinary families, not merely kings and prophets.

• Just as these names pointed forward to fulfillment in David and, later, Jesus, so every believer’s story is woven into God’s redemptive tapestry (Romans 8:28-30; Ephesians 1:4-6).


Summary

1 Chronicles 2:44, though terse, anchors the Hebronite branch of Caleb, links Judahite clans to verifiable towns, displays impeccable textual preservation, and reinforces the theological motif of God’s faithful orchestration of history leading to Christ.

How does 1 Chronicles 2:44 encourage us to value our spiritual heritage?
Top of Page
Top of Page