I Chronicles 7

This chapter is a tour through five of Jacob's twelve sons' family trees — Issachar, Benjamin, Naphtali, Manasseh, Ephraim, and Asher — but it's not evenly weighted, and that unevenness is the first thing worth noticing. Naphtali gets one verse. Zebulun and Dan get nothing at all Tyndale. Meanwhile Issachar, Benjamin, and Asher get long, detailed treatments that all share a strange feature: they end with military head-counts. "22,600 mighty men of valor." "87,000." "26,000 men fit for battle." Scholars think these three sections may actually come from an old army muster list rather than a pure genealogy — which is why they read differently, heavy on soldiers, light on where people actually settled Tyndale.

The chapter has a clear shape if you watch for it: name the sons → count the fighting men → move to the next tribe. But right in the middle of this dry roll call, the writer stops and tells a story — the only real narrative in the whole chapter. Ephraim's sons Ezer and Elead go raiding cattle in Gath and get killed by the locals (verse 21). Ephraim grieves "for many days" (verse 22), his relatives come to comfort him, and later he has another son he names Beriah — which means something like "in tragedy" or "born in evil circumstance" — because disaster had struck his house (verse 23). It's a small, human wound tucked inside a genealogy, and it's easy to skim right past it. Then, almost as a footnote, we learn Ephraim's daughter Sheerah built whole towns (verse 24) — a woman remembered by name as a builder of cities, which is unusual in these lists and worth pausing on.

The chapter closes by tracing Ephraim's line all the way down to "Nun his son, and Joshua his son" (verse 27) — quietly reminding you that the man who led Israel into the Promised Land came out of a family that had already buried sons in that land generations before they ever crossed the Jordan.

This sits inside 1 Chronicles 1–9, the long genealogical prologue the Chronicler uses to re-anchor a post-exile community (more on that below) in who they are before he tells them anything else. Christians haven't fought much over this chapter theologically — the real disagreement, such as it is, is scholarly: why are two tribes missing, and are the numbers literal head-counts or something more like tribal "shares" or symbolic totals. Nobody's salvation hinges on solving it.

1 Chronicles was almost certainly written after the Babylonian exile — after 539 BC, when the Persian king Cyrus let the Jewish exiles go home, and probably closer to 400 BC, once a fragile community was rebuilding Jerusalem's walls and temple. The author (Jewish tradition credits Ezra or someone from his circle) was writing for people who had lost almost everything — their land, their kingship, their temple, their sense of who they were — and had come back to a ruined city surrounded by hostile neighbors, wondering if they were even still "Israel" anymore.

That's why nine straight chapters of genealogy open this book. It sounds tedious to us, but to a people who'd just been scattered across an empire, this was a lifeline: it said, "you still belong to a tribe, a family, a promise that goes back to Jacob." Land inheritance in Israel had always run through tribal and family lines (see Numbers 26 and Joshua 13–21), so after the exile, proving your genealogy wasn't sentimental — it determined whether you could reclaim ancestral land, serve in the temple, or be counted as part of Israel at all.

The heavy military numbers in Issachar, Benjamin, and Asher's sections likely trace back to old census records — possibly connected to the census David ordered in 2 Samuel 24, or some parallel tribal muster the Chronicler had access to that never made it into the official royal records Matthew Henry. Whatever their source, listing "mighty men of valor" and "troops for battle" for tribes that, by the Chronicler's own day, no longer had an army or a king, was itself a kind of hope — a reminder that these tribes had once been strong, and might be again under God's hand.

The name תּוֹלָע (Tôwlâʻ), H8439, Issachar's firstborn (verse 1), literally means "worm" John Gill. It's a jarring name for the ancestor of a clan that would grow into over 22,000 fighting men — a small, easily-missed reminder that God builds strong things out of humble, even embarrassing, beginnings.

Look at how many names across this chapter are compound with אֵל (ʼêl), God — Jediael ("knowing God," H3043), Jeriel ("thrown of God," H3400), Uzziel ("strength of God," H5816), Ammihud, Elishama. Israelite parents were constantly preaching sermons through their children's names. Even יְהוֹשֻׁעַ / Joshua, closing out Ephraim's line in verse 27, carries the divine name folded into it — "the LORD saves."

The phrase that structures this whole chapter is גִּבּוֹרֵי חַיִל (gibbôrê chayil) — "mighty men of valor" — built from גִּבּוֹר (gibbôwr), H1368, meaning powerful, a warrior, and חַיִל (chayil), H2428, meaning force, strength, an army, even wealth or virtue. It shows up again and again (verses 2, 5, 7, 9, 11, 40), and it's doing double duty — these were men strong enough to fight, but the word also carries a sense of substance, of being people of weight and worth, not just muscle.

Notice too תּוֹלְדָה (tôwlᵉdâh), H8435 — "generations, family history" — used repeatedly (verses 2, 4, 9) from the root meaning "to bear, to give birth." The whole chapter is one long act of tôwlᵉdâh: not just listing names, but insisting that history itself is carried in bodies, in births, in families that don't disappear even when kingdoms fall Strong's.

The most striking thread in this chapter, easy to walk right past, is the line at the very end of Ephraim's genealogy: "Nun his son, and Joshua his son" (verse 27). Joshua — the man who led Israel into the land God promised, the man whose Hebrew name, Yehoshua, is the very name the angel tells Joseph to give Mary's son in Matthew 1:21, because "he will save his people from their sins." "Jesus" is literally the Greek form of "Joshua." The Chronicler isn't making that connection explicit — he's just doing genealogy — but the echo is there for anyone with ears to hear it: the man who brought Israel into rest under the old covenant shares his name, and in some sense his mission, with the one who brings God's people into a deeper rest under the new one (see Hebrews 4:8-9).

There's also the quieter thread of Ephraim's grief. A father loses two sons to violence, mourns for "many days," and God gives him another son in the wake of tragedy — a son whose very name remembers the wound (verse 23). It's a small, human pattern that shows up again and again in Scripture: loss doesn't get erased, but God keeps giving life on the other side of it. That's not a direct prophecy of Jesus, but it's the same shape the gospel takes — the Father who does not spare his own grief in order to bring life out of death.

And underneath the whole chapter is the patient, unglamorous faithfulness of God to keep every single tribal line alive — worm-named Tola's descendants, grieving Ephraim's descendants, all of them — right up until the moment the true heir, "the root of Jesse" and "the Lion of the tribe of Judah" ( Revelation 5:5), was born to finish what all these genealogies were pointing toward.

Be honest: your eyes probably started to glaze over somewhere around verse 9. That's fine — even faithful people find genealogies hard to love. But sit with what this chapter is actually claiming: God kept records. Not just of kings and prophets, but of Zemirah and Bimhal and Rizia — names you will never hear again, people who lived, married, raised kids, fought in wars nobody remembers, and died. Not one of them was famous. All of them were known.

That should press on you somewhere. Most of us live quiet, unremarkable lives — not headline lives, not "mighty man of valor with 22,600 descendants" lives. This chapter says that's not a problem for God. He doesn't only write down the names that make it into sermons. He writes down all of them.

But don't let the comfort of that swallow the cost of it. Ephraim's grief in verses 22-23 is the one place this chapter slows down and lets you feel something, and it's worth staying there rather than rushing to the next name list. He lost two sons to a senseless raid and mourned "many days." Scripture doesn't rush him past it, and neither should you rush past your own grief in the name of moving on to the next thing God has for you. What this chapter costs you is patience — patience to believe that your name, your ordinary, unlisted life, matters to God even when nobody writes it down, and patience to let your own grief be real before you look for the "Beriah" God might bring out of it.

• Lord, thank you that you know my name even though the world may never write it down — help me believe that an ordinary, unremarkable life is not a wasted one in your eyes.
• Father, like Ephraim, I carry grief I haven't fully let myself feel — teach me to mourn honestly instead of rushing past the pain to look "faithful."
• Thank you for every generation of faith that came before me and made a way for me to know you — help me live so that I pass something real on to those after me.
• Jesus, you carry the name of Joshua before you — thank you for leading your people into a rest that lasts. Help me trust you to finish what you started in my life.
• God, give me patience with the "boring" parts of Scripture and of my own life — teach me to find you even in the long lists and the slow, quiet years.

• Is there a part of your story that feels too ordinary or forgettable to matter to God? What would it mean to believe he's still writing it down?
• Ephraim mourned "for many days" before life moved forward again. Are you rushing past a grief you haven't actually let yourself feel?
• This chapter remembers Sheerah, a woman who built cities, in a list otherwise dominated by soldiers and sons. Whose quiet contributions in your own life have you overlooked?
• Tola's name means "worm," yet God built a mighty tribe from him. Where in your life do you feel too small or unlikely for God to use?
• The tribes of Zebulun and Dan are simply left out of this record. Does it unsettle you to think some things about your life might go unrecorded — and can you trust God with that anyway?