Luke Chapter 3 Read as one passage

Luke 3:32–33

Put together from the study of each verse: what each one meant, in order, with the background, words and debates of the whole passage said once.

32the son of Jesse, the son of Obed, the son of Boaz, the son of Sala, the son of Nahshon, 33the son of Amminadab, the son of Admin, the son of Arni, the son of Hezron, the son of Perez, the son of Judah,

What the first hearers heard

Luke's readers, Greek-speaking Jews and Gentile believers who knew the Greek Old Testament, would recognise these five names as the closing lines of Ruth, recited aloud. The verse:

  • put Jesus in the royal line. Jesse is the "root" of Isaiah 11, so Jesus belongs to the one family God promised to keep on David's throne (2 Samuel 7; Luke 1:32–33).
  • reached back to Israel's founding. Nahshon led Judah at Sinai and was related by marriage to Aaron's priestly family, so the line starts among the leaders of the Exodus generation.
  • brought the Ruth story with it. Boaz and Obed bring up a foreign widow taken into Israel through a kinsman's loyalty. Luke does not name Ruth, but his story is open to Gentiles throughout (2:32; 3:6, "all flesh"), and these names fit that, though he does not stress them.

Luke's list also goes the opposite way to Matthew's. It climbs from Jesus up to "Adam, the son of God" (3:38), so the Davidic names here are a stage on the way to a figure who belongs to all humanity. They are not where the list ends.

From the study of Luke 3:32.

Verse by verse

  1. 32the son of Jesse, the son of Obed, the son of Boaz, the son of Sala, the son of Nahshon,

    Luke's family tree climbs from Jesus up to God, one generation at a time, using nothing more than the little Greek word "the" in its "of" form: [the son] of… [the son] of…. These five names are the stretch just above King David:

    …of Jesse, David's father from Bethlehem, the "stump" from which Isaiah promised a new shoot would grow; of Obed, "the servant", the baby Ruth the Moabite bore, whose birth ends the book of Ruth; of Boaz, the Bethlehem kinsman who redeemed Naomi's land and married Ruth; of Sala, the man the Old Testament calls Salmon or Salma; of Nahshon, chieftain of Judah in the wilderness and brother-in-law of Aaron the high priest…

    The list is the same as the closing lines of Ruth (4:18–22) and 1 Chronicles 2:10–15, written in Greek. For a first-century hearer, reciting these names said that Jesus' line ran through Judah's leaders at the Exodus, through the Bethlehem story of Ruth and Boaz, to Jesse and David: the house God had promised to keep on the throne. "Son of" is the natural sense of each link. It need not mean the immediate father every time, since ancient genealogies often skipped generations, and four names to cover the time from the wilderness to David suggests this stretch is shortened.

    Full study →
  2. 33the son of Amminadab, the son of Admin, the son of Arni, the son of Hezron, the son of Perez, the son of Judah,

    Jesus was the son of Amminadab (meaning something like 'my kinsman is noble'). Amminadab was the father of Nahshon, who led the tribe of Judah in the wilderness, and Aaron the high priest was Amminadab's son-in-law. Amminadab was the son of Admin, who was the son of Arni. Arni is almost certainly the ancestor called Ram in Ruth and Chronicles. Admin is a name found nowhere else and may have entered through early copying. Arni was the son of Hezron, who went down to Egypt with Jacob's household. Hezron was the son of Perez, 'Breach', the twin who burst out first when Tamar gave birth to Judah's sons. And Perez was the son of Judah, the son of Jacob named for 'praise', who was promised the scepter.

    The Greek does not repeat the word 'son'. It simply says 'the one of… the one of… the one of…'. The list reads like a recited chain of belonging. Here it steps back through Israel's royal tribe, from the generation of the Exodus to the patriarchs. It follows the same line that ends the book of Ruth (Ruth 4:18–22).

    Full study →

Where the English drifted

  • in v32

    the son of

    tou (genitive article, 'the [one] of')

    What we hear
    Each name is the immediate biological father of the one before, so the list works like a complete birth register that can be added up to date events.
    What they heard
    'Belonging to / descended from'. Usually the father, but the form also covered a grandson or a more distant ancestor, and ancient genealogies often left out generations. Here only four names cover the time from the wilderness generation to David.
  • in v33

    the son of

    tou (genitive article; 'son' supplied)

    What we hear
    A complete, father-to-son record in which every generation is listed.
    What they heard
    'The one of', meaning 'descended from'. Ancient genealogies, including the Old Testament lists Luke draws on, were sometimes selective or compressed. Ruth 4 and 1 Chronicles 2 cover the whole stay in Egypt (traditionally about 430 years, Exodus 12:40) with only a few names: Hezron, Ram, Amminadab. That suggests the lists were not trying to name every generation.
Every word
  1. τοῦ

    tou · G3588

    the · v32, v33

    A genitive article with no noun after it. In Luke's chain it stands for '[the son] of', carrying on from 'being the son… of Joseph' in 3:23. The word 'son' is never written; the grammar supplies it.

  2. Ἰεσσαὶ

    Iessai · G2421

    Jesse · v32

    Hebrew Yishai, the Bethlehemite father of David (1 Samuel 16). Jesse is the link one step above David (3:31), and through Isaiah 11:1 ('a shoot from the stump of Jesse') his name already carried hope for a coming king.

  3. Ἰωβὴδ

    Iōbēd · G5601

    Obed · v32

    Hebrew ʿObed, 'one who serves' or 'worshipper', the son of Boaz and Ruth the Moabite (Ruth 4:13–17). Luke names no mothers, but anyone who knew the scriptures knew this was the child whose birth closes the book of Ruth.

  4. Βόος

    Boos · G1003

    Boaz · v32

    Boaz of Bethlehem, the landowner who acted as kinsman-redeemer (go'el) for Naomi's family and married Ruth (Ruth 2–4). Boos is a Greek spelling of the Hebrew Boʿaz.

  5. Σαλὰ

    Sala · G4527G

    Sala (= Salmon) · v32

    The man the Hebrew Bible calls Salmah/Salmon (Ruth 4:20–21) and Salma (1 Chronicles 2:11), father of Boaz. Sala looks like a short form of the same name. He is a different person from the Sala (Shelah) of Luke 3:35.

  6. Ναασσὼν

    Naassōn · G3476

    Nahshon · v32

    Hebrew Nachshon, son of Amminadab: the chieftain of the tribe of Judah in the wilderness (Numbers 1:7; 2:3), the first leader to bring his offering at the altar's dedication (Numbers 7:12), and brother-in-law of Aaron (Exodus 6:23).

  7. Ἀμιναδὰβ

    Aminadab · G0284

    Amminadab · v33

    This is the Greek form of the Hebrew name Ammi-nadav, probably meaning 'my kinsman is noble' or 'my kinsman is generous'. He was the father of Nahshon, the leader of Judah in the wilderness (Numbers 1:7). His daughter Elisheba married Aaron (Exodus 6:23).

  8. Ἀδμὶν

    Admin · G6002

    Admin · v33

    This name appears nowhere in the Old Testament genealogies. It is found only in the critical text of Luke. Many scholars think it entered through early scribal confusion. The Byzantine text has 'Aram' here instead.

  9. Ἀρνὶ

    Arni · G6095

    Arni · v33

    This is most likely a Greek form or corruption of Ram (Hebrew Ram, Greek Aram), the son of Hezron and father of Amminadab in Ruth 4:19 and 1 Chronicles 2:9–10.

  10. Ἑσρὼμ

    Hesrōm · G2074

    Hezron · v33

    This is the Greek form of the Hebrew name Chetsron. Hezron was a grandson of Judah, and he went down to Egypt with Jacob's family (Genesis 46:12). He founded a main clan of Judah.

  11. Φάρες

    Phares · G5329

    Perez · v33

    This is the Greek form of the Hebrew name Perets, 'breach' or 'breaking out'. Perez was one of the twin sons born to Judah by Tamar (Genesis 38:29). His line became the leading branch of Judah and the line of David (Ruth 4:12, 18).

  12. Ἰούδα

    Iouda · G2455

    Judah · v33

    This is the patriarch Judah, the fourth son of Jacob and Leah. His name was explained as 'praise' (Genesis 29:35). He was the head of the tribe that held the royal promise of Genesis 49:10.

The world behind it

Where the list comes from. From Judah down to David (Luke 3:31–33) Luke follows the genealogy at the end of Ruth (4:18–22) and in 1 Chronicles 2:5–15. Matthew 1:3–6 uses the same names. Luke's list and Matthew's separate after David: Luke goes through David's son Nathan, Matthew through Solomon. In this verse the two Gospels agree completely.

Why genealogies mattered. In Second Temple Judaism, descent decided who could serve as priest, who could own family land, and who could claim to belong to the royal house. Josephus says priestly families kept their records in public archives (Against Apion 1.30–36), and he gives his own pedigree at the start of his Life. Family lines claiming descent from David were known in Jesus' time; Eusebius, quoting Julius Africanus, reports that Jesus' relatives kept their own family records. Putting Jesus in Jesse's line backed the claim already made in Luke 1:32 ("the throne of his father David").

Gaps. The Old Testament places Nahshon in the Exodus generation and has his son Salmon alive at the conquest, yet only Boaz, Obed and Jesse come between Salmon and David. That is very few people for the period of the judges. Most scholars think this stretch was shortened. Ancient genealogies were often trimmed or arranged to fit a pattern (Matthew openly arranges his into sets of fourteen), and they were not meant as complete birth registers.

From the study of Luke 3:32.

Where scholars differ

in v32

Is the genealogy from Nahshon to David complete, or shortened?

  • Shortened: generations have been left out.

    Nahshon belongs to the Exodus generation and Salmon to the conquest, yet only three people (Boaz, Obed, Jesse) come before David, which is too few for the period of the judges as the Old Testament describes it. Ancient genealogies, including Matthew 1, are known to trim and arrange lines to fit a pattern.

  • Complete, with very long lives or a shorter period of the judges.

    The list in Ruth 4 and 1 Chronicles 2 gives no hint of a gap. Some interpreters argue for a shorter judges period, or for each man fathering his heir late in life.

in v32

Did Luke write 'Sala' or 'Salmon'?

  • Sala is original.

    It is found in the earliest and most reliable witnesses (P4, Sinaiticus, Vaticanus), and it is the harder reading, since scribes would tend to change it to Matthew's 'Salmon' (Metzger, Textual Commentary).

  • Salmon is original, and Sala is an early slip.

    It is very widely attested, matches the Old Testament and Matthew, and 'Sala' could have come in by assimilation to the other Sala in 3:35.

in v33

Did Luke originally write 'Admin, Arni' or 'Aram'?

  • Luke wrote 'Admin, Arni' (or something close). The shorter 'Aram' reading is a later correction to match Matthew and the Old Testament.

    The longer reading is the harder one. A scribe was more likely to bring Luke into line with Matthew and Ruth than to invent an unknown 'Admin'. It is supported by early Alexandrian witnesses, and the NA28/UBS5 committee preferred it.

  • Luke wrote 'Aram' (Ram), as in his Old Testament source. 'Admin' and 'Arni' are corruptions that arose from confusing or doubling similar-looking letters.

    Luke is clearly following the Ruth/Chronicles line here, and that line has a single name between Hezron and Amminadab. Most manuscripts have 'Aram'. The forms Admin, Adam, Arni and Aram are close enough in capital letters to explain the confusion. Even the critical editors call their choice the 'least unsatisfactory'.

in v33

Does the extra name reflect a deliberate numerical structure in Luke's genealogy?

  • Yes. With 'Admin' included, the list from Jesus back to God totals 77 names (11 × 7). This may echo Jewish schemes of world history arranged in sevens or 'seventy generations' (compare 1 Enoch 10:12), with Jesus arriving at the start of the final 'week'.

    This has been argued by scholars such as Richard Bauckham. Counting on the critical text gives 77 names. Jewish writings of the period did schematise history in sevens.

  • The count is not secure enough to carry that weight.

    The name total depends on which readings are accepted in this very verse, and elsewhere (e.g. 'Cainan' in 3:36). Luke never states a count, unlike Matthew 1:17. And the pattern could be partly the result of the editorial choice made here.

Sources
  • Nestle-Aland, Novum Testamentum Graece, 28th ed., apparatus at Luke 3:32
  • B. M. Metzger, A Textual Commentary on the Greek New Testament, 2nd ed., on Luke 3:32
  • BDAG s.v. ὁ (article with genitive of relationship); s.v. Σαλά; s.v. Ναασσών
  • HALOT s.v. נַחְשׁוֹן, שַׂלְמוֹן, בֹּעַז, יִשַׁי
  • Ruth 4:17–22; 1 Chronicles 2:5–15; Numbers 1:7; 2:3; 7:12; Exodus 6:23; Isaiah 11:1, 10; Matthew 1:3–6
  • J. A. Fitzmyer, The Gospel According to Luke I–IX (Anchor Bible), on 3:23–38
  • I. H. Marshall, The Gospel of Luke (NIGTC), on 3:23–38
  • R. Bauckham, Jude and the Relatives of Jesus in the Early Church, ch. on Luke's genealogy
  • Josephus, Life 1–6; Against Apion 1.30–36; Antiquities 5.318–337
  • Eusebius, Ecclesiastical History 1.7 (Julius Africanus on the genealogies)
  • Nestle-Aland Novum Testamentum Graece, 28th ed. (apparatus at Luke 3:33)
  • Bruce M. Metzger, A Textual Commentary on the Greek New Testament, 2nd ed., on Luke 3:33
  • BDAG s.v. ὁ (genitive article in kinship expressions)
  • BDB / HALOT s.v. פֶּרֶץ, רָם, עַמִּינָדָב, חֶצְרוֹן, יְהוּדָה
  • Ruth 4:18–22; 1 Chronicles 2:4–15; Matthew 1:3–4 (parallel genealogies)
  • Genesis 29:35; 38:29; 46:12; 49:10; Exodus 6:23; Numbers 1:7
  • Richard Bauckham, Jude and the Relatives of Jesus in the Early Church (on the 77-name structure)
  • Joseph A. Fitzmyer, The Gospel According to Luke I–IX (Anchor Bible), on 3:23–38
  • 1 Enoch 10:12

Original-language data: STEPBible TAHOT/TAGNT (CC BY 4.0).