I Chronicles 7:27

This is one line in a long list of names — a genealogy of the tribe of Ephraim, one of the sons of Joseph. On the surface it just tells you who fathered whom: Nun had a son named Joshua. That's it. Easy to skim right past.

But stop and look at what's tucked inside this list. This "Nun his son, and Joshua his son" is the Joshua — the man who stood next to Moses, who spied out the promised land, who eventually led Israel across the Jordan River and conquered Canaan. The Chronicler, writing centuries after Joshua died, is doing something quietly remarkable: he's tracing this towering figure of Israel's history all the way back to his ordinary family line in Ephraim, showing that the man who led a nation into its inheritance came from a real, traceable family, not a legend floating free of history Matthew Henry.

Notice too what's missing around this verse. Chronicles gives genealogies for Issachar, Benjamin, Naphtali, Manasseh, Ephraim, and Asher in this chapter — but Dan and Zebulun are conspicuously absent John Gill. Nobody knows for certain why, though many have connected it to Dan's later history of idol worship (see Judges 18 and 1 Kings 12:29). Chronicles was written after the Babylonian exile — when Nebuchadnezzar's army destroyed Jerusalem and dragged the survivors off to Babylon — to help a scattered, deflated people remember who they were. These lists aren't filler; they're roll call. They're saying: you still belong to something real, something God has kept track of down to the name.

1 Chronicles was almost certainly compiled after 539 BC, when the Persian king Cyrus let the Jewish exiles return home from Babylon — probably sometime in the 400s BC, likely by a priestly figure often called "the Chronicler." Picture the audience: people who had lost their land, their temple, their king, and in many cases their sense that they were still God's people at all. An entire generation had grown up in a foreign land, speaking a mixed language, wondering if the promises made to Abraham and David still meant anything.

The Chronicler's answer, strange as it sounds to us, was: open the family records. Nine straight chapters of genealogy open this book. Before any story of triumph or failure, before David or Solomon, the returning community needed to see their names — literally — connected all the way back through history. Land had been redistributed while they were gone. Tribal identity had frayed. Being able to say "I belong to Ephraim, and here's the line" wasn't trivia — it was how you proved your claim to ancestral land, your place in temple service, your right to stand among God's people again.

Joshua himself belongs to an earlier world entirely — roughly the 1400s or 1200s BC (scholars disagree on the exact date of the exodus), the generation after Moses, when Israel first crossed into Canaan. By the time the Chronicler is writing, Joshua's conquest is ancient history — the equivalent of an American today reading about the Mayflower. But naming him here in the Ephraimite line does something powerful for exiles rebuilding a shattered nation: it reminds them that God has done this before. He took a people with nothing but a promise and gave them a land through this very man's family line. If he did it once, the implicit hope runs, he can do it again.

Three small words carry this whole verse, and they're worth slowing down on.

נוּן (Nûwn), H5126 — Nun, Joshua's father's name. The root behind it carries a sense of "perpetuity" or continuing on Strong's. It's a fitting name to sit behind a son whose whole job would be carrying God's people forward into a future they couldn't see yet.

בֵּן (bên), H1121 — "son." This word is doing more work than English lets on. It's built from the root "to build" (בָּנָה), because in Hebrew thinking a son is literally how you build a family name into the future Strong's. Every "his son" in this chapter is a small act of construction — one generation laying the next like a brick.

יְהוֹשׁוּעַ (Yᵉhôwshûwaʻ), H3091 — Joshua. This is the name that matters most here. It's built from two pieces: יְהֹוָה (Yahweh, the LORD's covenant name) and יָשַׁע (yasha', "to save" or "to deliver"). Put together, the name literally means "Yahweh saves" or "the LORD is salvation" Strong's. His birth name was actually Hoshea ("salvation"), and Moses is the one who added the divine name onto the front of it in Numbers 13:16 — turning a general word for rescue into a name that pins the rescue directly on God himself.

That's the detail hiding in plain sight in this genealogy line. The man who led Israel into the promised land carries, in his very name, the confession that any deliverance Israel ever gets comes from the LORD — not from Joshua's own skill with a sword.

Here's the thread you don't want to miss: Joshua and Jesus are the same name. "Joshua" is the Hebrew Yehoshua; by the time the New Testament writers translate it into Greek, it becomes Iēsous — Jesus. Every time you say the name "Jesus," you are saying "Yahweh saves." That's not a coincidence buried in a boring genealogy — it's a signpost.

And the connection runs deeper than the name. The book of Hebrews makes the link explicit: "For if Joshua had given them rest, God would not have spoken later about another day" ( Hebrews 4:8). Joshua led Israel into the physical land of Canaan and gave them a kind of rest — but it wasn't the final rest. People still died, still sinned, still got exiled centuries later. Joshua's conquest was real, but it was a down payment, a preview, not the finished thing. The author of Hebrews is saying: there's a better Joshua coming, one who will lead God's people into a rest that lasts — not a plot of land, but reconciliation with God himself, forever.

So when you read "Nun his son, and Joshua his son" tucked into a genealogy, you're standing at the near end of a very long road that ends at a manger, then a cross, then an empty tomb. The first Joshua got Israel across the Jordan River with a sword and a battle plan. The second Joshua — Jesus of Nazareth — gets his people across from death to life with his own body broken on a cross. One name, two rescues, the second infinitely bigger than the first. This is exactly the kind of quiet echo the Bible loves to plant: not a direct prophecy shouting "look at me," but a name and a pattern laid down centuries early, waiting for you to notice it.

It would be easy to read a verse like this and feel nothing — just a name in a list, background noise before you get to the "real" parts of the Bible. But sit with what it's actually claiming: God bothered to keep track. Nun. Joshua. Real men, real fathers and sons, written down and preserved through a national catastrophe, through exile, through centuries, so that a beaten-down community rebuilding their lives in the rubble of Jerusalem could open a scroll and see: you are not forgotten, you are not a rounding error, your family line matters to God.

That's a costly thing to actually believe about your own life. It's much easier to assume you're invisible — one more name in seven billion, one more scrolling thumb in an infinite feed. This verse quietly insists otherwise. The God who wrote Joshua's father's name into permanent Scripture is the same God tracking your days too ( Psalm 139:16).

And then there's the name itself sitting right there in the middle of a dusty list: "Yahweh saves." Before Joshua ever swung a sword or led a single battle, his own name was preaching a sermon to him every single day — reminding him where the credit for any victory would actually belong. What if your name, or better, the name you were given at your baptism — "Christian," one who belongs to Christ — did the same work on you? What if you let it interrupt you the way Joshua's name must have interrupted him?

The cost here is small but real: slow down enough to stop treating genealogies, and maybe your own ordinary days, as filler. God doesn't waste ink. He doesn't waste you either.

• Lord, thank you that you keep records — that names like Nun and Joshua mattered enough to you to be written down forever. Help me believe my own name matters to you the same way.
• Jesus, thank you that you share your name with Joshua — "Yahweh saves." Teach me to actually lean on you for rescue instead of trusting my own strength.
• Father, I confess I often feel like a forgotten name in a crowd. Remind me that you know me completely, the way you knew every name in this list.
• Give me patience with the "boring" parts of Scripture — teach me to find you even in a genealogy.
• Like Joshua crossing the Jordan into a promise he couldn't fully see, give me courage to walk into whatever you're calling me toward right now.

• Do you actually believe God is tracking the details of your life the way he tracked Nun's family line — or does that feel like a nice idea you don't quite trust?
• Joshua's very name preached "the LORD saves" to him every day. What would change if you let your own name — Christian — preach the same sermon to you?
• Where in your life are you tempted to take credit for a "conquest" that was really God's doing all along?
• The exiles needed these genealogies to remember who they were after losing everything. What do you lean on to remember who you are when your life feels stripped down?
• Joshua only got Israel to a rest that didn't last. Where are you still looking for a "final rest" in things — jobs, relationships, achievements — that were never built to give it?