Seth's Genealogy

Question?  -   Contact  -   Revised

Genesis 5 traces a named line from Adam through Seth to Noah. Its repeated pattern gives an age at the birth of the next named son, years lived afterward, and a total lifespan. Enoch’s account differs, and Noah’s final lifespan appears later in Genesis 9.

Adam to Noah: A Referenced Age Table

KJV figures; the named son is not automatically the firstborn
Person Next named son and parent's age Total years reported Reference
Adam Seth, 130 930 Genesis 5:3–5
Seth Enos, 105 912 Genesis 5:6–8
Enos Cainan, 90 905 Genesis 5:9–11
Cainan Mahalaleel, 70 910 Genesis 5:12–14
Mahalaleel Jared, 65 895 Genesis 5:15–17
Jared Enoch, 162 962 Genesis 5:18–20
Enoch Methuselah, 65 365; God took him Genesis 5:21–24
Methuselah Lamech, 187 969 Genesis 5:25–27
Lamech Noah, 182 777 Genesis 5:28–31
Noah Shem, Ham, and Japheth are introduced at the 500-year marker; individual birth ages are not given there. 950 Genesis 5:32; 9:28–29

Other translations may use Enosh, Kenan, and Mahalalel where the KJV uses Enos, Cainan, and Mahalaleel. Within Genesis 5, these spelling differences should not be mistaken for extra people.

The chapter repeatedly mentions other sons and daughters. It selects one continuing line rather than listing every descendant. Noah’s three-son notice should not be read as saying that they were triplets or all born when he was exactly five hundred.

Why Does Genesis Follow Seth?

Genesis 4:25 records Eve’s explanation of Seth’s name in connection with another offspring in place of Abel, whom Cain killed. Genesis 4:26 introduces Seth’s son Enos and says that people then began to call upon the name of the Lord. Genesis 5 follows this family line toward the flood narrative.

Enoch is described as walking with God (Genesis 5:22–24), and Noah is called just and is also said to walk with God (Genesis 6:9). Those descriptions concern particular people. They do not establish that every descendant of Seth was righteous.

The Enoch and Lamech in this chapter have different parentage from the people with those names in Cain’s genealogy. Compare the two family settings before connecting a name to a story.

What Is Different about Enoch?

Most entries in Genesis 5 end with “and he died.” Enoch’s entry instead says that he walked with God and that God took him (5:24). Hebrews 11:5 adds that Enoch was translated so that he should not see death.

A table therefore should not label his 365 years as an ordinary age at death. Genesis does not explain the destination or mechanics of his being taken, and it does not say that he was moved elsewhere on earth to escape attackers. Detailed explanations go beyond what this passage supplies.

Can These Ages Be Turned into a Timeline?

Adding the nine ages from Adam at Seth’s birth through Lamech at Noah’s birth gives 1,056 years in the KJV sequence. Adding Noah’s age of 600 when the flood came (Genesis 7:6) gives 1,656. These are calculations from the listed figures, using the succession as a continuous chronology. Neither figure is a BC calendar date.

The calculation does not establish the cause of Methuselah’s death or say that he drowned. Genesis 5:27 supplies his total years and death notice, without a cause. It also does not explain biologically why the reported lifespans are long. Those questions require arguments beyond an age table.

Among the totals in this table, Methuselah’s 969 is the largest. That is a comparison within the biblical list, rather than a claim supported by independently verified modern longevity records.

For the next stage of the family line, see the genealogy from Shem to Abraham. For the distinct question of how Luke’s genealogy relates to Mary, see our comparison of Jesus’ genealogies; Luke does not explicitly call its list Mary’s genealogy.

Sources and Method

The relationships and ages were checked against the local digital KJV corpus. Direct figures appear in the table; the 1,056 and 1,656 totals are editorial additions of those figures. No absolute creation date is assumed.

Content revised October 29, 2026. Send factual corrections or source questions through our contact page.