Luke Chapter 3 Read as one passage
Luke 3:36–37
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.
36the son of Cainan, the son of Arphaxad, the son of Shem, the son of Noah, the son of Lamech, 37the son of Methuselah, the son of Enoch, the son of Jared, the son of Mahalalel, the son of Cainan,
What the first hearers heard
To Luke's first readers, who were mostly Greek-speaking and many of them Gentile believers, this verse was a familiar run of names from their own Greek Bible. Naming the flood generations did several things:
- It tied Jesus to all humanity. Every nation traced itself to Noah's sons. A Messiah whose line ran through Noah to Adam was not only Israel's king but heir of the whole human family. This fits Luke's interest in Gentiles: Simeon's 'light for revelation to the Gentiles' (2:32), and 'all flesh shall see the salvation of God' (3:6).
- It recalled judgment and new creation. Noah stood for God's judgment on a corrupt world and a fresh start with a rescued remnant. Lamech's hope that his son would bring 'relief' from the curse was half-fulfilled in Noah. Readers who knew the story could hear that hope still waiting in the line that leads to Jesus.
- It gave weight through order. In an honor-conscious culture, a long, unbroken line back to the first ancestors was itself a claim to legitimacy. A neatly patterned list (possibly built on sevens, see Debates) suggested that history had moved by God's plan towards this person.
Hearers would not have noticed anything odd about Cainan. He was in their Bible. The difference from the Hebrew text became a question only later, for readers who compared the two.
From the study of Luke 3:36.
Verse by verse
-
36the son of Cainan, the son of Arphaxad, the son of Shem, the son of Noah, the son of Lamech,
Full study →Read upward, this verse continues the chain that started at Jesus in 3:23: …Shelah, who was the son of Cainan, who was the son of Arphaxad, who was the son of Shem, who was the son of Noah, who was the son of Lamech…
The five names take the reader back through the flood. Arphaxad was the first of the chosen line born into the renewed world, two years after the waters went down. Shem, whose name means 'name' or 'renown', received Noah's blessing. Noah saved humanity through judgment, and every nation descends from him. Lamech, Noah's father, named his son in hope that he would bring 'comfort' or 'relief' from the cursed ground (Genesis 5:29). He is the godly Lamech of Seth's line, not the violent Lamech of Cain's line.
Cainan is the striking name. He stands between Shelah and Arphaxad because Luke follows the Greek Bible his readers knew (the Septuagint, which has him in Genesis 10–11), not the Hebrew text, which does not. The Greek itself is very spare: no verbs and no word for 'son', only 'the [one] of…' repeated. In this kind of list, 'son of' means a line of descent and inheritance. It does not have to mean that every father–son pair is listed. By running the line past Abraham, through Noah, back to Adam and finally 'of God' (3:38), Luke presents Jesus, whom the heavenly voice has just called 'my Son' (3:22), as belonging to the whole human race that came from Noah's family.
-
37the son of Methuselah, the son of Enoch, the son of Jared, the son of Mahalalel, the son of Cainan,
Full study →Luke is walking Jesus' family line back up through the generations before the Flood. Following the line upward: Jesus is descended from Methuselah, the man who lived longer than anyone; from Enoch, Methuselah's father, who "walked with God" and was taken up by God without dying, and who stands seventh in line from Adam; from Jared, Enoch's father; from Mahalalel, Jared's father; and from Cainan (Kenan), Mahalalel's father, whose own father was Enosh, son of Seth, son of Adam.
The Greek is even barer than the English. Each link is just "of the…", "the one of Methuselah, the one of Enoch…", and "son" is understood rather than written. The names and their spellings come straight from the Greek translation of Genesis 5 that Luke's readers used as their Bible. The effect is deliberate. Having said that Jesus was "son, as was supposed, of Joseph" (3:23), Luke keeps climbing past David and Abraham, through these first ancestors of the human race, until he reaches "Adam, the son of God" (3:38). This verse is part of the climb that ties Jesus to all humanity, not only to Israel.
Where the English drifted
-
in v36
the son of
tou (article only; 'son', huios, carried over from 3:23)
- What we hear
- Each person was the immediate biological child of the next, so the list is a complete, gap-free record from which years can be added up.
- What they heard
- 'The [one] of': belonging to and descending from, in a line of inheritance. Ancient genealogies could skip or add generations. This very verse includes a man the Hebrew Genesis does not list.
Where popular teaching often drifts
in v37
The names before the Flood don't spell out a hidden gospel
- What's often taught
- A popular teaching says the meanings of the names from Adam to Noah, found in Genesis 5 and repeated in Luke 3:36–38, form a hidden sentence. A common version reads: 'Man (is) appointed mortal sorrow; (but) the Blessed God shall come down teaching (that) His death shall bring (the) despairing rest.' Here Kenan = 'sorrow', Mahalalel = 'the Blessed God', Jared = 'shall come down', Enoch = 'teaching', Methuselah = 'his death shall bring'.
- What the text supports
Several of these meanings have little support in the Hebrew lexicons (HALOT, BDB):
- Methuselah most likely means 'man of the javelin' or 'man of Shelah'. 'His death shall bring' rests on a stretched reading of the second part.
- Kenan is probably related to qayin (Cain), possibly meaning 'smith'. 'Sorrow' is not a standard meaning.
- Mahalalel is usually explained as 'praise of God' or 'God shines forth', which is close to 'Blessed God' but not the same.
- Jared does sound like yarad, 'go down', and Enoch may come from a root meaning 'dedicate' or 'train'. Those two links have some basis, and ancient Jewish writers did play on Jared's name (1 Enoch 6:6).
The sentence, though, is assembled by choosing a convenient meaning for each name and adding linking words in brackets. Neither Genesis nor Luke points to any message hidden in the names. Luke wrote the names as Greek transliterations for readers who mostly knew no Hebrew, so they could not have heard any such sentence. The list's purpose shows in its context: it ties Jesus to Adam and to God (3:38), between the baptism and the temptation. The teaching is right that the genealogy points to Christ, but it does so by its line of descent, not by a code in the names.
- Where the English feeds it
- English translations do not cause this reading. It comes from name-meaning lists in some study Bibles and popular materials that give one firm meaning for names whose origins are actually uncertain.
Ἐνώχ enōch Ἰάρεδ iared Καϊνάν, Καϊνάμ kainan, kainam Μαθουσάλα mathousala Μαλελεήλ maleleēl
Every word
-
τοῦ
tou · G3588
-
Καϊνὰμ
Kainam · G2536
Cainan · v36, v37
A post-flood ancestor placed between Shelah and Arphaxad. He appears in the Greek Old Testament (Genesis 10:24; 11:12–13) and in Jubilees, but not in the Hebrew text of Genesis or Chronicles. He is a different person from the earlier Cainan (Hebrew Qenan) of 3:37.
-
Ἀρφαξὰδ
Arphaxad · G0742
Arphaxad · v36
Greek form of Hebrew Arpakhshad, a son of Shem born two years after the flood (Genesis 11:10). Through Eber he is the line's ancestor of the Hebrews.
-
Σὴμ
Sēm · G4590
Shem · v36
Noah's son who received the blessing ('Blessed be the LORD, the God of Shem', Genesis 9:26). His name in Hebrew means 'name'. He is the ancestor of the peoples later called 'Semitic', including Israel.
-
Νῶε
Nōe · G3575
Noah · v36
The flood survivor from whom, in Genesis 10, every nation on earth descends. Naming him signals that the line runs back through the father of all peoples, not just of Israel.
-
Λάμεχ
Lamech · G2984
Lamech · v36
Noah's father in Seth's line (Genesis 5:28–31). He named Noah in hope of relief from the cursed ground. He is not the violent, boasting Lamech of Cain's line (Genesis 4:18–24).
-
Μαθουσαλὰ
Mathousala · G3103
Methuselah · v37
Methuselah, son of Enoch and grandfather of Noah (Genesis 5:21–27). He is famous for living 969 years, the longest life recorded. The spelling matches the Greek Old Testament, which shows Luke was copying from it.
-
Ἑνὼχ
Henōch · G1802
Enoch · v37
Enoch, who 'walked with God, and he was not, for God took him' (Genesis 5:24). In Luke's list he is the seventh name counting from Adam. Jewish and early Christian writers knew that 'seventh from Adam' detail well (Jude 14), and Enoch was a major figure in Jewish writing of Jesus' day.
-
Ἰάρετ
Iaret · G2391
Jared · v37
Jared, father of Enoch (Genesis 5:15–20). Luke's critical text spells it with a final -t. Many manuscripts and the Septuagint end it in -d.
-
Μαλελεὴλ
Maleleēl · G3121
Mahalalel · v37
Mahalalel, father of Jared (Genesis 5:12–17). The Greek form comes from the Septuagint. That is why the KJV has 'Maleleel'.
The world behind it
Where this verse sits. Matthew's genealogy (Matthew 1) opens his Gospel and runs down from Abraham. Luke's runs up from Jesus to 'Adam, the [son] of God' (3:38). Luke places it between Jesus' baptism, where God declares 'You are my Son' (3:22), and the temptation, where the devil says 'If you are the Son of God' (4:3). The list explains in what sense Jesus is God's son: as the true heir of Adam, who was also called God's son.
Why go back past Abraham? A Jewish genealogy would normally stop at Abraham, the father of Israel. Luke continues through Noah, whose three sons were the source of all seventy (or seventy-two) nations in the 'Table of Nations' of Genesis 10. For Luke's largely Gentile, Greek-speaking readers this matters. Luke–Acts is about salvation reaching 'all flesh' (Luke 3:6, quoting Isaiah) and 'the ends of the earth' (Acts 1:8).
Luke's Bible was the Greek Old Testament. Luke's writing style and quotations follow the Septuagint, the Greek translation made in Egypt in the last centuries BC. In LXX Genesis 11:12–13 Arphaxad fathers Kainan and Kainan fathers Sala, and the Greek numbers for the ages differ from the Hebrew. Luke copied the list as his readers knew it. Jubilees, a Jewish retelling of Genesis from the 2nd century BC, also knows Kainam and attaches a story to him: he found and copied forbidden star-lore taught by the fallen 'Watchers'. So the name was in Jewish tradition before Luke wrote.
How ancient genealogies worked. In the ancient world a genealogy was less a birth register than a claim about identity, inheritance and standing. Lists could skip generations, add names, or be arranged into symbolic numbers. Luke himself signals that legal sonship is in view: 'being the son, as was supposed, of Joseph' (3:23).
From the study of Luke 3:36.
Where scholars differ
in v36
Did Luke himself write 'the son of Cainan', or was it added later?
-
It is original to Luke.
Almost all manuscripts, including the oldest complete codices, have it. Luke consistently follows the Septuagint, which has Kainan in Genesis 10–11. Jubilees shows the name existed in Jewish tradition before Christianity. If Luke's list is built on a count of 77 names, Cainan is needed to reach it. Most textual critics and commentators (e.g. Fitzmyer, Marshall) accept it.
-
It is an early scribal addition.
Papyrus 75 apparently omits it, and so does Codex Bezae. A copyist's eye could have picked up 'Cainan' from the very next verse (3:37). Several early Christian chronographers and Josephus do not count him. Some older writers have also argued that the Kainan in surviving Septuagint manuscripts was itself copied in from Luke. Against that, Jubilees independently has the name.
in v36
Is Luke's list arranged in a symbolic number pattern?
-
Yes, around 77 names, or eleven 'weeks' of seven generations.
Richard Bauckham (Jude and the Relatives of Jesus, 1990) argues that the list, counted with this Cainan, puts Jesus at the start of the final, twelfth 'week' of world history. He links this to 1 Enoch 10:12 (seventy generations until judgment) and to Enoch's place as seventh from Adam (Jude 14). On this view the extra name is deliberate.
-
The pattern is uncertain or accidental.
The total depends on textual variants and on whether 'God' and 'Jesus' are counted. Luke never draws attention to a number, unlike Matthew's explicit 'fourteen generations' (Matthew 1:17).
in v36
Why does the Septuagint have a Cainan that the Hebrew Genesis lacks?
-
The Greek tradition (or the Hebrew text it was translated from) added him.
With Cainan, the line from Arphaxad (the first born after the flood) to Abraham has ten generations. That mirrors the ten from Adam to Noah. The Septuagint also changes many ages and dates in these chapters, which suggests deliberate chronological editing.
-
The Hebrew tradition lost him.
This is a minority view. Its supporters point to his presence in Jubilees and the Septuagint as two independent early witnesses. However, the Hebrew Genesis, Chronicles and Josephus all agree in lacking him.
in v37
Is Enoch's position as seventh from Adam part of a deliberate number pattern in Luke's genealogy?
-
Yes. Luke's list has 77 generations from God/Adam to Jesus, arranged in sevens, and Enoch at the seventh place is a marker. Some scholars connect this with 1 Enoch's scheme of generations of history (1 Enoch 10:12, seventy generations), which would put Jesus at the decisive end-time point.
The total count in the critical text is 77 names when the list is counted a certain way (Jesus to God, 3:23–38). Enoch is seventh, as Jude 14 also stresses from 1 Enoch 60:8 and 93:3. Richard Bauckham argues this view in Jude and the Relatives of Jesus.
-
Not demonstrable. The count depends on disputed readings (for example the Admin/Arni names in 3:33 and the Cainan of 3:36), and Luke never points to the number. Enoch's seventh place simply comes from Genesis 5.
Manuscripts differ in the number of names, so any total is fragile. Luke, unlike Matthew 1:17, says nothing about structure. Enoch is seventh in every list of Adam's line, so his position needs no special design to explain it.
Sources
- Nestle-Aland, Novum Testamentum Graece, 28th ed., apparatus at Luke 3:36
- BDAG s.v. Καϊνάμ, Ἀρφαξάδ, Νῶε
- Septuagint (Rahlfs-Hanhart), Genesis 10:24; 11:12–13; 1 Chronicles 1:24
- Jubilees 8:1–5
- Josephus, Antiquities 1.143–150
- 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 (1990), ch. 7
- HALOT s.v. נֹחַ, שֵׁם, אַרְפַּכְשַׁד
- Nestle-Aland Novum Testamentum Graece, 28th ed., apparatus at Luke 3:36–37
- Septuagint (Rahlfs-Hanhart), Genesis 5:9–25; 1 Chronicles 1:1–3
- BDAG s.v. Ἑνώχ, Μαθουσαλά, Ἰάρετ, Μαλελεήλ, Καϊνάμ
- HALOT s.v. חֲנוֹךְ, מְתוּשֶׁלַח, יֶרֶד, מַהֲלַלְאֵל, קֵינָן
- 1 Enoch 6:6; 81–82; 91; 93:3; 106–107
- Jubilees 4:15–25; 8:1–5
- Sirach 44:16; 49:14; Hebrews 11:5; Jude 14–15
- Joseph A. Fitzmyer, The Gospel According to Luke I–IX (Anchor Bible), on 3:23–38
- I. Howard Marshall, The Gospel of Luke (NIGTC), on 3:23–38
- Richard Bauckham, Jude and the Relatives of Jesus in the Early Church, ch. on Luke's genealogy
- Marshall D. Johnson, The Purpose of the Biblical Genealogies
Original-language data: STEPBible TAHOT/TAGNT (CC BY 4.0).