I Chronicles 3

This chapter is a family tree, but read it slowly and it turns out to be a compressed version of the whole story of Israel's kings — rise, glory, collapse, and a flicker of hope left burning in the ashes.

It moves in three clear stages Tyndale. First (verses 1-9), David's sons: six born in Hebron while he was king only over Judah, then thirteen more born in Jerusalem after he became king over all Israel — including four by Bathsheba, one of whom is Solomon. Second (verses 10-16), a straight royal line from Solomon down through Rehoboam, all the way to Zedekiah — basically the entire history of the kingdom of Judah in fourteen names. Third (verses 17-24), the line doesn't stop at the disaster of Babylon. It keeps going, through Jeconiah "the captive," down to Zerubbabel and beyond, into names the reader has never heard of — obscure descendants living generations after the Babylonian exile (when Nebuchadnezzar's army destroyed Jerusalem in 586 BC and deported the survivors).

What's easy to miss: this is the only place in the entire Old Testament where the royal line is traced past the exile at all. Kings, Samuel, and the prophets all end at the wall coming down. Chronicles alone keeps counting sons after the throne is gone. That's the quiet argument of the whole chapter — the family didn't disappear just because the crown did.

Also easy to miss: the honesty buried in the list. Amnon and Absalom, David's first and third sons, are named flatly next to their mothers with no commentary — the reader who knows 2 Samuel knows these two destroyed each other and nearly destroyed David's house ( 2 Samuel 13:1, 13:29) Jamieson-Fausset-Brown. The Chronicler doesn't hide the wreckage; he just keeps writing names past it.

Where this sits in the bigger book: 1 Chronicles opens with nine chapters of genealogy tracing from Adam to the returned exiles, and this chapter is its spine — David's own family, told by someone writing generations later to a small, defeated community trying to figure out if God was still keeping his promises to them.

1 Chronicles was almost certainly written after the Babylonian exile, probably in the 400s BC, likely by someone connected to the Levites or priesthood working with older sources like Samuel and Kings. The audience wasn't reading this in David's palace — they were a small, poor, politically powerless community back in the land of Judah, living under Persian rule, with no king, a half-rebuilt temple, and a wall around Jerusalem that had only recently gone back up.

That's the key to understanding why this chapter exists at all. Imagine you're one of those people. Your grandparents were dragged to Babylon. You've come home to rubble. You have priests, you have a temple project, but you have no king — the family God promised David an everlasting throne through ( 2 Samuel 7:16) looks, on paper, extinct. So the writer does something quietly defiant: he sits down and traces that family, name by name, right through the catastrophe, right up to people alive in his own generation — Zerubbabel and his children, real people the first readers might have known personally or known of. Zerubbabel himself led one of the first groups back from Babylon and helped rebuild the temple altar and foundation (see Ezra 2-3).

The list of the kings in verses 10-16 covers roughly 970 BC (Solomon's reign) to 586 BC (Zedekiah, the last king, blinded and hauled off by the Babylonians) — nearly four hundred years condensed into seven verses. Then the third section, verses 17-24, covers the exile and its aftermath, stretching possibly into the 5th century BC, close to the Chronicler's own lifetime. So this isn't dusty archive-keeping. It's a pastoral document: proof, in list form, that the promise survived the fire.

A few names carry the chapter's real freight Strong's.

בְּכוֹר (bᵉkôwr, H1060) in verse 1 — "firstborn." In that world this word wasn't just birth order, it was a legal claim: the firstborn son normally inherited the leading share and, for a king, the throne itself Jamieson-Fausset-Brown. Amnon carries this weight — and it's precisely why his story ends so badly, and why the throne having to pass instead to Bathsheba's son later feels like such an upheaval of the expected order.

דָּוִד (Dâvid, H1732) — the name itself is thought to come from a root meaning "beloved." Every name in this chapter hangs off that one man's name — every king, every exile, every obscure descendant in verse 24 is a "son of the beloved."

שְׁלֹמֹה (Shᵉlômôh, H8010) in verse 5 and 10 — from shalom, peace. Named at the very moment David's household was anything but peaceful.

נָתָן (Nâthân, H5416) in verse 5 — "given." Matthew Henry notices this may well be named for Nathan the prophet, the man who confronted David over Bathsheba and Uriah and brought him to repentance — meaning David gave his own son the name of the man who told him the hardest truth of his life Matthew Henry.

פִּילֶגֶשׁ (pîylegesh, H6370) in verse 9 — "concubine." The text draws a quiet legal and social line here: those sons aren't named, "not worthy of the honour," as Henry puts it — a small, cold detail that tells you something about how status worked in David's house Matthew Henry.

Yôʼshîyâh (Josiah, H2977), "founded of Jah," in verse 14 — the last great reforming king, right before the line runs into exile.

This chapter is, quietly, one of the most important genealogical hinges in the whole Bible for understanding who Jesus is. Matthew opens his Gospel by tracing exactly this line — David, Solomon, Rehoboam, all the way down through Zerubbabel — because he's making the same argument the Chronicler already made five hundred years earlier: the royal line did not die in Babylon. Matthew 1:6-12 lifts names almost straight off this page.

That's the real weight of verses 17-24. When Jeconiah is dragged off "the captive" and God, through Jeremiah, pronounces a curse over him that none of his descendants would ever sit on David's throne ( Jeremiah 22:30), it looks like the promise to David is dead. This chapter's answer is: the line kept having children anyway. It doesn't resolve the tension — it just refuses to let it be the last word. Centuries later, that refusal becomes the ground Matthew stands on when he writes "Jesus, the son of David, the son of Abraham" ( Matthew 1:1) and threads him — through Joseph, not by ordinary blood right, sidestepping Jeconiah's curse in a way theologians have puzzled over for centuries — right back into this very family tree.

There's also a smaller, sadder echo worth naming. David's sons in this chapter include men whose stories are half tragedy — Amnon, Absalom, Adonijah — men who wanted the throne and grasped for it and were destroyed by their own hunger for it Matthew Henry. Jesus is the Son of David who never grasped. Philippians 2:6-8 says he had every right to the throne and emptied himself instead. The whole bent, blood-soaked history of David's ambitious sons makes the humility of David's greater Son land that much harder.

It would be easy to skim this chapter — it's just names, right? But sit with it for a minute and something uncomfortable surfaces: God's promises get kept through families, through decades, through generations who never see the payoff.

Zerubbabel, sitting at the end of this list, had no idea his descendants would include the Messiah. He just lived his life, rebuilt an altar, raised kids, and died. The people in verses 20-24 — Hashubah, Ohel, Jushab-hesed, Anani — are names you've never heard and never will hear again in Scripture. And yet they were the thread. God was doing something through their ordinary, undocumented lives that they never got to see finished.

Here's what this chapter asks of you: it asks you to trust that your unremarkable, unrecorded life might matter more than you'll ever know — and to stop needing to see the ending before you'll be faithful in the middle. It also refuses to let you sanitize your own family. David's household was a wreck — rape, murder, rebellion, favoritism — and God's promise ran straight through the wreck, not around it. If your family has ugly chapters, you're not disqualified from being part of God's story. You're in good company.

The cost here is patience without proof. Most of us want to know how the story turns out before we'll keep showing up faithfully in our small corner of it. This chapter says: keep having the names. Keep raising the kids. Keep believing God remembers his promises even when four hundred years and a foreign empire stand between the promise and its fulfillment. You may be someone's Zerubbabel — a name mentioned once, doing something that echoes further than you can see.

• Lord, thank you that you kept your promise to David through exile, obscurity, and centuries of silence — help me trust you're keeping your promises to me the same way.
• Father, I confess I want proof before I'm faithful — teach me to be faithful in the unremarkable middle of my story, like the nameless generations in this list.
• God, my own family has its own Amnons and Absaloms, its own wreckage — thank you that you don't wait for a clean family before you work.
• Jesus, Son of David, thank you that you never grasped for the throne the way David's sons did — shape my ambition to look like yours.
• Lord, help me remember that you see and count the small, hidden lives — including mine — even when history doesn't write them down.

• Is there a part of your family's story you'd rather skip over the way you're tempted to skip over this list — and what would it look like to let God's promise run through it instead of around it?
• Where in your life are you demanding to see the ending before you'll keep being faithful?
• Which of David's sons do you relate to most right now — the one who grasps for what isn't his, or the one content to be given what God gives?
• Can you name three "unremarkable" seasons of your own life that might actually be the hinge someone else's story turns on later?
• What would it cost you to trust that God is still working even when — like the exiles reading this chapter — you can't see a throne, a king, or an obvious happy ending anywhere in sight?