Luke Chapter 3

Luke 3:33

Studied by claude-opus-5-5 Checked against the Greek

Luke 3:33

Greek

τοῦ Ἀμιναδὰβ τοῦ Ἀδμὶν τοῦ Ἀρνὶ τοῦ Ἑσρὼμ τοῦ Φάρες τοῦ Ἰούδα

tou Aminadab tou Admin tou Arni tou Hesrōm tou Phares tou Iouda

the [one] of Amminadab, the [one] of Admin, the [one] of Arni, the [one] of Hezron, the [one] of Perez, the [one] of Judah

What it meant

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).

Where the English drifted

  • 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.

    Where the later meaning came from: Modern expectations of complete family-tree records and exact chronology.

What the first hearers heard

For Luke's first readers, a mix of Jewish and Gentile believers who knew the Greek Old Testament, this verse was a recognisable stretch of sacred history. It was the line from Judah to the house of Boaz, which ends the book of Ruth and leads to David.

Hearing it read aloud did several things:

  • Royal standing. It placed Jesus in the tribe that held the scepter promise (Genesis 49:10), backing the angel's words that he would receive 'the throne of his father David' (Luke 1:32).
  • Israel's whole story. It passed through the patriarchs, the going down into Egypt (Hezron) and the wilderness generation (Amminadab and Nahshon). Jesus is rooted in all of Israel's history, not just a slice of it.
  • Toward all humanity. It was part of a chain that does not stop at Abraham, as Matthew's does. Luke's list goes on to Adam and to God. This verse is a stage on that climb: Judah leads to Abraham, Abraham to Adam, and Adam to God. That suits Luke's concern that the salvation in Jesus is for 'all flesh' (3:6).

The names also carried echoes of irregular grace. Perez came from Judah's encounter with Tamar, and the next verse back in the chain (3:32) includes Boaz, husband of Ruth the Moabite. Luke does not draw attention to this, but hearers who knew the stories would have recognised it.

Every word

Tap any word for its full meaning and everywhere it appears.

  1. τοῦ

    tou · G3588

    the

    This is the genitive (possessive) form of the article. It means 'the one belonging to' or 'the [son] of'. The word 'son' is not in the Greek. It is implied by the pattern that began in 3:23: Jesus was 'son, as was supposed, of Joseph, the [one] of Heli…'.

  2. Ἀμιναδὰβ

    Aminadab · G0284

    Amminadab

    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).

  3. τοῦ

    tou · G3588

    the

    'The [son] of'. It links Amminadab to the next ancestor up the line.

  4. Ἀδμὶν

    Admin · G6002

    Admin

    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.

  5. τοῦ

    tou · G3588

    the

    'The [son] of'. The chain continues upward.

  6. Ἀρνὶ

    Arni · G6095

    Arni

    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.

  7. τοῦ

    tou · G3588

    the

    'The [son] of'.

  8. Ἑσρὼμ

    Hesrōm · G2074

    Hezron

    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.

  9. τοῦ

    tou · G3588

    the

    'The [son] of'.

  10. Φάρες

    Phares · G5329

    Perez

    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).

  11. τοῦ

    tou · G3588

    the

    'The [son] of'.

  12. Ἰούδα

    Iouda · G2455

    Judah

    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.

Key words, in depth

τοῦ tou G3588

Range of meaning

The Greek article ('the') in the genitive case, the form that expresses belonging or origin. Used alone before a personal name, it means 'the one of X'. In genealogies this means 'son of X', or more broadly 'descended from X'.

Against the English

English versions supply 'the son of' (BSB, WEB) or '[the son] of' (KJV, YLT, with brackets marking words added for sense). This is a fair rendering. The Greek is leaner, though. It names a link of belonging and origin without spelling out 'son' each time.

Used elsewhere in the period

The same compact pattern appears in Greek documents of the period. Papyri identify people as 'X of Y', meaning 'X son of Y'. The Septuagint, the Greek Old Testament, uses similar genitive shorthand in its lists. Luke opens the chain once with 'son' (huios) in 3:23 and then lets the article carry the rest all the way to 'of Adam, of God' (3:38).

What it does in this verse

The whole verse is a run of 'of… of… of…'. It works like a chant of belonging. Every name lies on the same line of origin that ends in God (3:38). That ending recalls the voice at the baptism just before: 'You are my beloved Son' (3:22).

Ἀδμίν Admin G6002

Range of meaning

A personal name found only in this verse in the critical text. It has no Hebrew counterpart in Ruth 4, 1 Chronicles 2 or Matthew 1.

Against the English

BSB and ESV print 'Admin'. KJV, WEB and YLT have no Admin; they read 'Aram'. NIV prints 'Ram' and puts Admin/Arni in a footnote.

Used elsewhere in the period

Admin does not appear in the Old Testament or in the Septuagint list of Judah's descendants. It turns up only in a group of early Egyptian-type manuscripts and versions of Luke. Metzger reports that the editorial committee chose this reading as 'the least unsatisfactory' form of text, one that was current in the Alexandrian church at an early period.

What it does in this verse

Admin adds a generation between Hezron and Amminadab that the Old Testament does not record. Readers should know that this name rests on a disputed textual decision, not on an independent tradition about an otherwise unknown ancestor.

Ἀρνί Arni G6095

Range of meaning

A personal name. It is almost certainly a variant or corrupted form of Ram (Hebrew Ram, 'high' or 'exalted'), the son of Hezron (Ruth 4:19; 1 Chronicles 2:9).

Against the English

BSB and ESV have 'Arni'. Some modern versions write 'Ram' in its place, and KJV and WEB have 'Aram'.

Used elsewhere in the period

The Hebrew Old Testament has Ram. The Septuagint manuscripts vary (forms such as Aram and Arran appear). Matthew 1:3–4 has Aram. In Greek capital-letter script, ΑΡΑΜ, ΑΡΝΙ and ΑΔΜΙΝ look close enough for copyists to confuse them, and the forms could easily have been doubled.

What it does in this verse

Arni stands in Ram's place. So the line Perez–Hezron–Ram–Amminadab from Ruth 4 is still there under the critical text. The only change is the extra name, Admin.

Φάρες Phares G5329

Range of meaning

The Greek form of the Hebrew name Perets, from parats, 'to break through' or 'to burst out'. A perets is a 'breach'.

Against the English

KJV keeps the Greek spelling 'Phares'. Modern versions restore the Hebrew 'Perez'. The meaning of the name is lost in every English version.

Used elsewhere in the period

Genesis 38:29 explains the name. At the birth of Tamar's twins, Perez 'broke out' ahead of his brother Zerah, and the midwife said, 'What a breach you have made for yourself!' Ruth 4:12 blesses Boaz's house to be 'like the house of Perez'. 1 Chronicles 27:3 and Nehemiah 11:4–6 show Perezite clans as the leading branch of Judah.

What it does in this verse

Jewish hearers would have known the story behind this name: Judah's dealings with Tamar, and a younger twin who pushed ahead to take first place. Matthew names Tamar outright (Matthew 1:3). Luke names only the men, but the story was in the name all the same.

Ἰούδας Ioudas G2455

Range of meaning

The Greek form of Yehudah, Judah. It names the patriarch, the tribe, and the territory and people of Judea. 'Jew' (Ioudaios) comes from it.

Against the English

'Judah' is accurate. KJV's 'Juda' follows the Greek spelling.

Used elsewhere in the period

Genesis 29:35 explains the name as 'This time I will praise the LORD'. Genesis 49:8–10 gives Judah the scepter: 'The scepter shall not depart from Judah.' In the Dead Sea Scrolls and other Jewish writings of Jesus' day, this blessing was read as a promise of a king to come from Judah (e.g. 4Q252).

What it does in this verse

As Luke's list climbs upward, Judah is where it passes from the royal tribe to the patriarchs (Jacob, Isaac, Abraham, 3:34). Placing Jesus in Judah's line, through Perez and David, supports Gabriel's promise of 'the throne of his father David' (1:32).

The world behind it

Where this verse sits. Luke's genealogy (3:23–38) runs backward, from Jesus up to 'Adam, the son of God'. Matthew's runs forward, from Abraham down. Luke places it straight after the baptism, where Jesus is declared God's Son (3:22), and straight before the temptation, where that sonship is tested (4:3, 9).

The source of this stretch. Verses 32–33 (Boaz back to Judah) follow the short family line at the end of Ruth (4:18–22) and its parallel in 1 Chronicles 2:4–15: Judah, Perez, Hezron, Ram, Amminadab, Nahshon, Salmon, Boaz, Obed, Jesse, David. This list was the standard record of the house of David's descent, and Luke and Matthew both draw on it.

What the names called up. For a Jewish hearer, these names were stories, not empty labels:

  • Judah held the royal promise (Genesis 49:10).
  • Perez was born of the Judah–Tamar episode (Genesis 38), and his house was a byword for blessing (Ruth 4:12).
  • Hezron went down to Egypt with Jacob (Genesis 46:12).
  • Amminadab's son Nahshon was the leader of Judah at Sinai (Numbers 1:7; 7:12), and his daughter married Aaron (Exodus 6:23). So the royal line and the priestly line were joined in his household.

Genealogies in the ancient world. Family lines established identity, inheritance and standing. For a figure presented as royal, a line through David and Judah was a claim to legitimacy. Some Jewish writings of the period also arranged history in symbolic numbers of generations. In 1 Enoch 10:12, for example, the fallen watchers are bound 'for seventy generations'. Some scholars think Luke's list has a structure of this kind (see Debates).

How the translations handle it
BSB

“the son of Amminadab, the son of Admin, the son of Arni, the son of Hezron, the son of Perez, the son of Judah,”

Gets right
Follows the modern critical Greek text exactly and uses Hebrew-based spellings that readers can find in the Old Testament.
Loses
Gives no sign in the main text that 'Admin' and 'Arni' are disputed, or that Arni stands where the Old Testament has Ram. A reader comparing Ruth 4 will find a name that isn't there.
KJV

“Which was [the son] of Aminadab, which was [the son] of Aram, which was [the son] of Esrom, which was [the son] of Phares, which was [the son] of Juda,”

Gets right
Brackets honestly mark 'the son' as a word added for sense. The text follows the Byzantine manuscripts and agrees with Matthew 1:3–4 and the Old Testament line.
Loses
Greek spellings (Esrom, Phares, Juda) hide the fact that these are the same people as Hezron, Perez and Judah in Genesis and Ruth. It also lacks the critical text's extra generation, Admin.
WEB

“the son of Amminadab, the son of Aram, the son of Hezron, the son of Perez, the son of Judah,”

Gets right
Follows the Majority Text (the reading of most surviving manuscripts) but uses the Old Testament spellings Hezron, Perez and Judah, so readers can follow the line back into the Old Testament.
Loses
'Aram' could be confused with the land of Aram (Syria). In the Old Testament this ancestor is called 'Ram'.
YLT

“the [son] of Amminadab, the [son] of Aram, the [son] of Esrom, the [son] of Pharez,”

Gets right
Very literal. It brackets '[son]' to show that the Greek has only the article.
Loses
Its verse division differs: 'the [son] of Judah' falls at the start of its verse 34. It also mixes spellings (Esrom from the Greek, Pharez from the Hebrew).
ESV

“…the son of Admin, the son of Arni…”

Gets right
Follows the critical text, as BSB does, and footnotes the variant.
Loses
As with BSB, a reader of the main text alone will not see that the names differ from Ruth and Matthew.
NIV

“…the son of Ram…”

Gets right
Prints the name that matches Ruth 4:19, 1 Chronicles 2:9 and Matthew 1:3–4, and gives Admin/Arni in a footnote. This avoids an apparent clash with the Old Testament.
Loses
Departs from the text most critical editors print. In effect it harmonises Luke with the Old Testament in the main text.
NLT

“…Amminadab was the son of Admin. Admin was the son of Arni.…”

Gets right
Readable full sentences. Follows the critical-text names.
Loses
Recasting the list as full sentences loses the bare 'of… of…' rhythm of the Greek. Like BSB and ESV, it does not show the textual problem in the main text.
Text and manuscripts

One of the most unsettled verses in the Gospel manuscripts. The stretch between Amminadab and Hezron survives in many forms. They include:

  • of Amminadab, of Aram: the Byzantine/Majority text, behind the KJV and WEB. It matches Matthew 1:3–4.
  • of Amminadab, of Admin, of Arni: the reading printed in NA28/UBS5, the standard critical editions. It is supported mainly by early Egyptian (Alexandrian) witnesses.
  • Other forms add Joram, omit Amminadab, or spell the names Adam, Admein, Arnei, Aram and so on.

Bruce Metzger's Textual Commentary says the committee faced 'a bewildering variety of readings'. It chose what seemed 'the least unsatisfactory form of text', one current in the Alexandrian church at an early period. In other words, even the editors who print 'Admin, Arni' admit low confidence. The supplied source text follows the critical reading. It is reported here without change, but readers should treat 'Admin' in particular as uncertain.

The Old Testament line. The Hebrew text of Ruth 4:19 and 1 Chronicles 2:9–10 has Hezron → Ram → Amminadab. Septuagint manuscripts vary in how they spell Ram, with forms including Aram and Arran. This instability in the Greek Old Testament probably helped produce the confusion in Luke's manuscripts. In Greek capital-letter script, ΑΡΑΜ, ΑΡΝΙ and ΑΔΜΙΝ are close enough for copyists to confuse or double them.

Verse division. The supplied YLT ends at 'Pharez'. YLT places 'the [son] of Judah' at the start of its verse 34, a difference in verse numbering, not in text.

Vulgate. The Latin Vulgate follows the shorter line (qui fuit Aminadab, qui fuit Aram, qui fuit Esrom, qui fuit Phares, qui fuit Iudae). Like the Byzantine Greek, it has no Admin or Arni.

  • The critical Greek text (NA28/UBS5) reads 'of Amminadab, of Admin, of Arni', while the Byzantine text behind the KJV reads 'of Amminadab, of Aram', a name that matches Matthew 1:3–4 and the Old Testament 'Ram'. The critical text therefore has one more generation than the Byzantine text.
  • Other manuscripts add 'Joram', drop 'Amminadab', or spell Admin and Arni in other ways. Metzger calls the evidence a 'bewildering variety' of readings, and this is one of the most unstable verses in the Gospels.
Where scholars differ

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'.

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: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).

What readers are saying

Loading…