1 CHRONICLES: CHAPTER 1

1:1KJV Adam, Sheth, Enosh,

B:E Project The list begins with Adam, then his son Seth, then Seth's son Enosh.

Context: This opens 1 Chronicles by reaching all the way back to Genesis 5, the very first human family tree, rather than starting with Israel's own recent history.

Meaning: Before Chronicles tells the story of Israel's kings, it roots that story in the story of everyone - starting with the first human being. It's a reminder that the Israelite nation isn't presented as separate from the rest of humanity; it emerges from the same single origin as every other person and people.

Lesson: I want you to notice: before any nation, any religion, any tribe, there was simply one human family. Whatever divides people later, we all start from the same place - so hold every other person as genuinely your relative, not a stranger.

See Also: Genesis 5:1-8 - the fuller version of this same early family record; Luke 3:38 - Luke's genealogy of Jesus traces back through this same line to Adam.

1:2KJV Kenan, Mahalaleel, Jered,

B:E Project Next in the line: Kenan, then Mahalaleel, then Jered.

Context: These three continue the pre-flood genealogy taken directly from Genesis 5, each named as father to the next.

Meaning: There's nothing dramatic recorded about these men individually - just their place in an unbroken chain. Chronicles is making a quiet point: ordinary generations, however unremarkable to us now, are the necessary links that carry life and memory forward.

Lesson: Most of your days won't feel historic. That's fine - you are still a link that matters, carrying something forward to people who come after you, even if their names are the only part anyone remembers.

See Also: Genesis 5:9-18 - the same names with their lifespans given in full.

1:3KJV Henoch, Methuselah, Lamech,

B:E Project Then Henoch (Enoch), then Methuselah, then Lamech.

Context: Enoch is famous elsewhere for having 'walked with God' and being taken without dying (Genesis 5:24); Methuselah is remembered as the longest-lived person in the Bible; Lamech is Noah's father.

Meaning: Chronicles doesn't repeat the remarkable detail Genesis gives about Enoch - it just slots him into the list. Readers who know the fuller story bring that meaning with them; the genealogy trusts its audience to remember.

Lesson: Not every good life needs to be explained in full to matter. Some of the most significant things about a person - like walking closely with what's true and good - never make it into the official record, and that's alright.

See Also: Genesis 5:21-24 - Enoch's walk with God and his unusual departure from life; Hebrews 11:5 - Enoch remembered for his faith.

1:4KJV Noah, Shem, Ham, and Japheth.

B:E Project Noah, then his three sons: Shem, Ham, and Japheth.

Context: This verse jumps straight past the flood story to name Noah's sons, who become - according to Genesis 10 - the ancestors of every nation and people that follows.

Meaning: One verse carries the weight of the entire flood narrative and skips to its outcome: three brothers from whom, the Bible says, 'the whole earth was overspread.' Chronicles isn't interested in retelling the drama, only in the family tree it produced.

Lesson: After loss and upheaval, life keeps finding a way forward through the people who remain. Whatever you've survived, you can still be someone through whom good things multiply afterwards.

See Also: Genesis 9:18-19 - Noah's three sons named as the source of the whole earth's population; Genesis 10:1 - the start of the 'Table of Nations' this chapter compresses.

1:5KJV The sons of Japheth; Gomer, and Magog, and Madai, and Javan, and Tubal, and Meshech, and Tiras.

B:E Project The sons of Japheth were Gomer, Magog, Madai, Javan, Tubal, Meshech, and Tiras.

Context: This begins the 'Table of Nations' (compressed from Genesis 10), tracing Japheth's descendants, generally understood as the peoples who settled to the north - Anatolia, the Aegean, and beyond.

Meaning: These aren't Israelites - they're the ancestors of distant, non-Israelite peoples: forerunners of groups like the Medes and the Greeks. Chronicles includes them anyway, showing the writer's interest in the whole human family, not just the part that becomes Israel.

Lesson: Take an interest in people who aren't 'your people.' A truly wide heart keeps room on the map for everyone, not just those in your own nation or tradition.

See Also: Genesis 10:2-5 - the source list with more detail on where these peoples settled.

1:6KJV And the sons of Gomer; Ashchenaz, and Riphath, and Togarmah.

B:E Project The sons of Gomer were Ashchenaz, Riphath, and Togarmah.

Context: Gomer's descendants are generally linked to peoples of the region around Armenia and eastern Anatolia; Ashchenaz (Ashkenaz) later became a name applied to peoples further north and, much later in history, to European Jewish communities.

Meaning: A single name here, Ashchenaz, travelled an enormous distance through history to become a label many people still use today. It's a small window into how ancient names keep echoing forward, changing meaning as they go.

Lesson: Names and identities shift and travel across centuries in ways you can't predict. Hold your own identity with some lightness - it's part of a much longer story than you can see the end of.

See Also: Jeremiah 51:27 - Ashchenaz named among kingdoms summoned against Babylon, showing the name still in use centuries later.

1:7KJV And the sons of Javan; Elishah, and Tarshish, Kittim, and Dodanim.

B:E Project The sons of Javan were Elishah, Tarshish, Kittim, and Dodanim.

Context: Javan is generally understood as the ancestor of the Greek/Ionian peoples; Tarshish became known as a distant western trading destination, and Kittim refers to Cyprus.

Meaning: These names mark out the edges of the known world for ancient Israel - far-off trading nations across the sea. Tarshish especially recurs later in the Bible as a byword for the furthest place a ship could sail.

Lesson: There will always be a horizon further than you can currently see. That's not a threat - it's an invitation to stay curious about how much bigger the world, and the family of humanity, actually is.

See Also: Jonah 1:3 - Jonah tries to flee 'to Tarshish', showing the name still meant 'the far edge of the map' centuries later.

1:8KJV The sons of Ham; Cush, and Mizraim, Put, and Canaan.

B:E Project The sons of Ham were Cush, Mizraim, Put, and Canaan.

Context: Ham's line, in the Table of Nations, is generally associated with peoples to the south and southwest of Israel: Cush (the region of Nubia/Ethiopia), Mizraim (Egypt), Put (likely Libya), and Canaan, the land Israel would later settle.

Meaning: Canaan's naming here matters a great deal for the rest of the Bible's story - it's the land promised to Abraham's family, currently inhabited by Canaan's own descendants, whom Israel will later displace. The tension of that future story is quietly seeded in this one word.

Lesson: Land, home, and belonging carry deep and complicated histories. Before judging any conflict over territory, remember that real families and real histories sit underneath every line on a map.

See Also: Genesis 9:25 - the earlier account of a curse spoken over Canaan; Genesis 10:6 - the source verse for this list.

1:9KJV And the sons of Cush; Seba, and Havilah, and Sabta, and Raamah, and Sabtecha. And the sons of Raamah; Sheba, and Dedan.

B:E Project The sons of Cush were Seba, Havilah, Sabta, Raamah, and Sabtecha. And the sons of Raamah were Sheba and Dedan.

Context: These names trace peoples generally located along the Arabian peninsula and Horn of Africa, regions later associated with the spice and incense trade - Sheba especially becomes famous through the Queen of Sheba who visits Solomon.

Meaning: Buried in this list is the ancestral root of a nation that will, generations later, produce a famous visiting monarch. The genealogy plants seeds whose fruit appears much further into the biblical story.

Lesson: Small, unnoticed beginnings can grow into something that later commands real respect and attention. Don't judge the value of a start by how little fanfare it gets.

See Also: 1 Kings 10:1-13 - the Queen of Sheba's visit to Solomon, a descendant of this same Sheba's namesake region.

1:10KJV And Cush begat Nimrod: he began to be mighty upon the earth.

B:E Project Cush also fathered Nimrod, who became a mighty man on the earth.

Context: Nimrod appears more fully in Genesis 10:8-12 as a powerful hunter and the founder of major early cities and kingdoms, including Babel (Babylon) and Nineveh - both of which later become enemies or oppressors of Israel.

Meaning: Nimrod represents raw human ambition and empire-building - impressive by worldly standards, but the cities he founds become synonymous, later in the Bible, with pride and opposition to God. His single verse here hints at a much bigger, more troubling legacy.

Lesson: Strength and achievement aren't the same as goodness. Ask what your power is actually being used for - power that only serves itself tends to build something that, generations later, needs to be pulled down.

See Also: Genesis 10:8-12 - Nimrod's fuller story and his founding of Babel and Nineveh; Genesis 11:1-9 - the tower of Babel, built in the region Nimrod founded.

1:11KJV And Mizraim begat Ludim, and Anamim, and Lehabim, and Naphtuhim,

B:E Project Mizraim (Egypt) fathered Ludim, Anamim, Lehabim, and Naphtuhim.

Context: This continues the descendants of Mizraim, the biblical name for Egypt, listing sub-groups or regions within or near Egyptian territory.

Meaning: Egypt will loom enormously over the rest of the Bible's story - as the place of both refuge (Joseph) and slavery (Exodus). This verse quietly establishes Egypt's ancient roots before any of that history unfolds.

Lesson: The place that later becomes your hardship may once have been, or could again be, a place of welcome. Don't fix a person, a nation, or even a season of your own life permanently as 'the enemy' - stories change.

See Also: Genesis 10:13 - the source list; Genesis 45:9-10 - Egypt later becomes a place of rescue for Jacob's family.

1:12KJV And Pathrusim, and Casluhim, (of whom came the Philistines,) and Caphthorim.

B:E Project And Pathrusim, Casluhim (from whom the Philistines came), and Caphthorim.

Context: This verse notes, almost in passing, that the Philistines - who become one of Israel's most persistent enemies, including Goliath's people - trace back to this Egyptian-linked branch.

Meaning: A throwaway genealogical note actually explains where one of Israel's fiercest recurring opponents came from. The Bible doesn't dramatise it here; it simply records the fact and moves on, letting later books tell that story.

Lesson: Conflict often has a long, ordinary ancestry behind it, not a cosmic one. Understanding where an opponent actually comes from can turn blind hostility into something more like understanding.

See Also: 1 Samuel 17 - David and Goliath, Goliath being a Philistine; Amos 9:7 - the prophet later notes God brought the Philistines from Caphtor, echoing this verse.

1:13KJV And Canaan begat Zidon his firstborn, and Heth,

B:E Project Canaan fathered Zidon, his firstborn son, and Heth.

Context: Zidon (Sidon) becomes a major Phoenician coastal city; Heth is the ancestor of the Hittites, a people who show up repeatedly in later Israelite history.

Meaning: Two names here open onto real later stories: Sidon becomes a wealthy trading city often linked with idol worship that tempts Israel, and Heth's descendants include figures like Ephron, who sold Abraham a burial site, and Uriah the Hittite, whose wife Bathsheba David later takes.

Lesson: Every name on a list like this was, to someone, an ancestor worth remembering and telling stories about. Take that seriously about the people around you now - each one is somebody's whole world.

See Also: Genesis 23:3-16 - Abraham buying land from Ephron the Hittite; 2 Samuel 11 - Uriah the Hittite, wronged by King David.

1:14KJV The Jebusite also, and the Amorite, and the Girgashite,

B:E Project Also the Jebusite, the Amorite, and the Girgashite.

Context: These are Canaanite peoples who will later occupy the land promised to Abraham's descendants, including the Jebusites, who hold Jerusalem itself until David captures it.

Meaning: The city that becomes the centre of Israel's worship and kingship - Jerusalem - starts out here simply as the home of the Jebusites, a Canaanite tribe with no special status yet. History will turn that around dramatically.

Lesson: Nothing is destined to stay as it currently is. A place, or a person, written off as ordinary or even as an obstacle now can become the very centre of something meaningful later.

See Also: 2 Samuel 5:6-9 - David capturing Jebusite Jerusalem and making it his city.

1:15KJV And the Hivite, and the Arkite, and the Sinite,

B:E Project Also the Hivite, the Arkite, and the Sinite.

Context: More Canaanite tribal groups, part of the wider list of peoples inhabiting the land before Israel's conquest under Joshua.

Meaning: These names carry little individual story in the Bible, but together they build the picture of a land already full of established peoples and cities long before Israel arrives - the 'promised land' was never empty.

Lesson: Wherever you're headed in life, other people are usually already there, with their own claims and histories. Walking in with humility about that reality serves you far better than assuming you're starting on a blank page.

See Also: Joshua 3:10 - a later list naming these same Canaanite peoples as nations Israel would face.

1:16KJV And the Arvadite, and the Zemarite, and the Hamathite.

B:E Project Also the Arvadite, the Zemarite, and the Hamathite.

Context: These final names close out Canaan's genealogy, generally placed further north along the Syrian coast, near cities like Arvad and Hamath.

Meaning: This closes the descendants of Ham with a full sweep of Canaan's neighbouring or related peoples - completing the picture before the text turns to Shem's line, which will eventually lead to Abraham and Israel.

Lesson: Big stories need a full backdrop before the main plot begins. Your own life has a wider cast of people and circumstances behind it too - it's worth knowing that backdrop rather than only focusing on the foreground.

See Also: Genesis 10:18-19 - the source verses noting the eventual spread of Canaanite peoples.

1:17KJV The sons of Shem; Elam, and Asshur, and Arphaxad, and Lud, and Aram, and Uz, and Hul, and Gether, and Meshech.

B:E Project The sons of Shem were Elam, Asshur, Arphaxad, Lud, Aram, Uz, Hul, Gether, and Meshech.

Context: The text now turns to Shem's line, the branch of Noah's family that will eventually lead to Abraham and Israel; it includes ancestors associated with Elam (Persia), Asshur (Assyria), and Aram (the Arameans/Syrians).

Meaning: This is the pivotal genealogical branch for the whole Bible - Shem's line is the one the story will follow. Interestingly, it also names Uz, generally understood as the homeland of Job, tying this list to another major biblical book.

Lesson: The line that matters most to your future often looks, at first, just like one option among several others. Pay attention to where you're actually heading, not just where you could go.

See Also: Job 1:1 - Job is 'of the land of Uz', linking that story to this genealogy; Genesis 10:22 - the source list.

1:18KJV And Arphaxad begat Shelah, and Shelah begat Eber.

B:E Project Arphaxad fathered Shelah, and Shelah fathered Eber.

Context: This narrows the focus from Shem's many sons down to a single line, heading towards Eber - the name from which 'Hebrew' is generally thought to derive.

Meaning: The genealogy is now funnelling down, generation by generation, from 'everyone' to one specific family line - the one that will eventually be called Hebrew, and then Israelite.

Lesson: Focus matters. A wide, general calling in life often needs to narrow down, generation by generation or decision by decision, into one specific, faithful path.

See Also: Genesis 10:24 - the source verse for this narrower Shem-to-Eber line.

1:19KJV And unto Eber were born two sons: the name of the one was Peleg; because in his days the earth was divided: and his brother’s name was Joktan.

B:E Project Eber had two sons: one was named Peleg, because the earth was divided in his lifetime, and his brother was named Joktan.

Context: Peleg's name is explicitly tied to a 'division' of the earth - widely understood to reference the scattering of peoples and languages at the tower of Babel (Genesis 11), which happens around this point in the genealogy's timeline.

Meaning: This is one of the few verses in the chapter where a name is explained rather than just listed - and it's explained by an event of fracture and separation. Even amid all this list-making of unity and connection, division gets a name and a permanent place in the record.

Lesson: Division and separation are part of human history - I don't pretend otherwise. But naming what divided people, honestly, is the first step towards one day working to bring them back together.

See Also: Genesis 11:1-9 - the Babel account of languages and peoples being scattered, the event Peleg's name commemorates.

1:20KJV And Joktan begat Almodad, and Sheleph, and Hazarmaveth, and Jerah,

B:E Project Joktan fathered Almodad, Sheleph, Hazarmaveth, and Jerah.

Context: Joktan's sons are generally linked to peoples and regions of the Arabian peninsula, continuing the branch of Shem's family that heads south rather than towards Abraham.

Meaning: Not every branch of this family tree leads to Israel - Joktan's descendants spread out across Arabia instead. The Bible records this whole side branch fully, even though the main story won't follow it further.

Lesson: Not every path you or people you love take will be 'the main story' - and that doesn't make those paths worthless or unrecorded. Every direction a life takes is still worth honouring.

See Also: Genesis 10:26-29 - the fuller source list of Joktan's descendants.

1:21KJV Hadoram also, and Uzal, and Diklah,

B:E Project Also Hadoram, Uzal, and Diklah.

Context: More of Joktan's Arabian-associated descendants; Uzal is sometimes linked to the ancient name for what became Sana'a in Yemen.

Meaning: These names root a whole later region and its people into this single ancient family tree, connecting distant geography back to one shared ancestor.

Lesson: However far apart people end up living, or however different their lives look now, this kind of list keeps insisting on a shared root beneath it all.

See Also: Genesis 10:27 - the parallel listing in Genesis.

1:22KJV And Ebal, and Abimael, and Sheba,

B:E Project Also Ebal, Abimael, and Sheba.

Context: Continuing Joktan's line; this Sheba is a separate figure from the earlier Sheba descended from Cush (verse 9), a reminder that biblical names often repeat across different family branches.

Meaning: The repetition of names like Sheba across different genealogical branches shows how ancient naming worked - names were reused, not treated as unique identifiers, which is worth remembering when reading Bible genealogies generally.

Lesson: Don't assume two things that share a name are the same thing. Look closer, understand context, before drawing conclusions - that applies to people and their reputations too.

See Also: 1 Chronicles 1:9 - an earlier, different Sheba in Cush's line, showing the name's reuse.

1:23KJV And Ophir, and Havilah, and Jobab. All these were the sons of Joktan.

B:E Project Also Ophir, Havilah, and Jobab. All these were the sons of Joktan.

Context: This closes Joktan's genealogy; Ophir becomes famous later in the Bible as a source of exceptionally fine gold, especially associated with Solomon's wealth.

Meaning: Ophir's mention here is a quiet seed for a much later story - centuries on, Solomon's ships will sail for Ophir's gold to help build the Temple. The genealogy plants names that pay off much further down the biblical timeline.

Lesson: Resources and opportunities you'll need later in life are often already in place long before you need them. Trust that groundwork laid early - even unnoticed - has its purpose.

See Also: 1 Kings 9:28 - Solomon's ships bringing gold from Ophir.

1:24KJV Shem, Arphaxad, Shelah,

B:E Project Shem, Arphaxad, Shelah,

Context: The text now restates a condensed, direct line from Shem down to Abraham, repeating names already given but stripped of side branches - this begins that streamlined list.

Meaning: After all the sprawling branches of the Table of Nations, the text pulls back to just the single direct line that matters most for what follows: the ancestry of Abraham, and through him, Israel.

Lesson: After exploring the full breadth of options and connections, sometimes you need to refocus back onto the one path that actually leads where you're going.

See Also: Genesis 11:10-12 - the source for this direct line from Shem.

1:25KJV Eber, Peleg, Reu,

B:E Project Eber, Peleg, Reu,

Context: Continuing the direct, condensed genealogical line from Shem towards Abraham, this time without the explanatory detail about Peleg given earlier in verse 19.

Meaning: Having already explained Peleg's name once, the text now simply lists him as a link in the chain - showing how this second, condensed list serves a different purpose (tracing lineage efficiently) than the earlier, fuller one.

Lesson: Sometimes the full story only needs telling once. After that, simply remembering and carrying it forward is enough.

See Also: Genesis 11:18-20 - the source verses for Reu and the generations following.

1:26KJV Serug, Nahor, Terah,

B:E Project Serug, Nahor, Terah,

Context: This continues the direct line towards Abraham; Terah is Abraham's father, who according to Genesis began the journey from Ur towards Canaan before settling in Haran.

Meaning: Terah's generation is the one that begins the great geographic move west that Abraham will later complete - the family was already migrating before God's specific call to Abraham in Genesis 12.

Lesson: Big turning points in a family's or a person's life are often prepared for by a previous generation's smaller steps. You may be laying groundwork now for a future you won't personally see finished.

See Also: Genesis 11:31 - Terah's family first setting out from Ur towards Canaan.

1:27KJV Abram; the same is Abraham.

B:E Project Abram - that is, Abraham.

Context: This single short verse marks the arrival of Abraham, the pivotal figure the whole genealogy has been building towards, and the man with whom God makes the covenant that shapes the rest of the Bible's story.

Meaning: After twenty-six generations of names, the text finally lands on Abraham - noting that he was originally called Abram before his name was changed. Chronicles treats this as the true hinge point of the whole human story it has been tracing since Adam.

Lesson: A name change, in the Bible, often marks a new identity and a new calling. Whatever your past name or reputation, you are never locked into it - a fresh start, and a new purpose, is always genuinely possible.

See Also: Genesis 17:5 - God changing Abram's name to Abraham, meaning 'father of many nations'; Galatians 3:29 - the New Testament describing all who have faith as Abraham's spiritual children.

1:28KJV The sons of Abraham; Isaac, and Ishmael.

B:E Project The sons of Abraham were Isaac and Ishmael.

Context: This introduces Abraham's two sons: Isaac, born to his wife Sarah as the child of promise, and Ishmael, born earlier to Sarah's servant Hagar.

Meaning: Both sons are named here with no hint of favouritism in the wording itself - though the Bible's larger story does follow Isaac's line towards Israel while still honouring Ishmael's story in its own right, as the chapter shows next.

Lesson: Family situations are rarely simple, and both of Abraham's sons carried real pain from how their story unfolded. I don't dismiss anyone's place in a complicated family - both sons mattered, and both are named with dignity here.

See Also: Genesis 21:1-21 - the fuller story of Isaac's birth and Ishmael's departure with his mother Hagar.

1:29KJV These are their generations: The firstborn of Ishmael, Nebaioth; then Kedar, and Adbeel, and Mibsam,

B:E Project These are their family records: Ishmael's firstborn was Nebaioth, then Kedar, Adbeel, and Mibsam.

Context: The text now gives Ishmael's own genealogy in full before moving to Isaac's line - Ishmael's twelve sons became, according to Genesis 25, twelve princes of their own tribes.

Meaning: Even though the covenant promise runs through Isaac, Ishmael isn't erased or diminished - he gets his own full genealogical record, named son by son, exactly as Isaac's line will. The text treats him with real respect.

Lesson: Being 'not the chosen path' in someone else's story doesn't make your own life any less worth recording and valuing. I see everyone fully, not just the ones who end up in the spotlight of someone else's plan.

See Also: Genesis 25:12-16 - the fuller account of Ishmael's twelve sons becoming princes of their tribes.

1:30KJV Mishma, and Dumah, Massa, Hadad, and Tema,

B:E Project Then Mishma, Dumah, Massa, Hadad, and Tema.

Context: This continues Ishmael's twelve sons, several of whom - like Tema and Dumah - lend their names to real Arabian regions and oases known in the ancient world.

Meaning: These names aren't abstract - some correspond to actual places later mentioned in prophetic writing, showing that Ishmael's descendants became real, identifiable communities across Arabia.

Lesson: Whole communities and cultures can trace real, lasting identity back to a name most readers skim past. Every people group has a beginning worth respecting, even if history remembers it only faintly.

See Also: Isaiah 21:14 - Tema mentioned as a real place offering hospitality to fleeing travellers, generations later.

1:31KJV Jetur, Naphish, and Kedemah. These are the sons of Ishmael.

B:E Project Also Jetur, Naphish, and Kedemah. These were the sons of Ishmael.

Context: This closes Ishmael's genealogical list; Jetur's descendants (the Itureans) appear again much later in biblical-era history around the region of Galilee.

Meaning: Twelve named sons complete Ishmael's own tribal structure - mirroring the twelve tribes that will later come from Jacob/Israel. The parallel is deliberate: both of Abraham's sons become the fathers of substantial nations.

Lesson: Two very different destinies can still each carry real weight and blessing. Comparing your path to someone else's misses that both can matter enormously in their own right.

See Also: 1 Chronicles 5:19 - the Itureans (Jetur's descendants) mentioned again in conflict with Israelite tribes.

1:32KJV Now the sons of Keturah, Abraham’s concubine: she bare Zimran, and Jokshan, and Medan, and Midian, and Ishbak, and Shuah. And the sons of Jokshan; Sheba, and Dedan.

B:E Project The sons of Keturah, Abraham's concubine, were Zimran, Jokshan, Medan, Midian, Ishbak, and Shuah. And the sons of Jokshan were Sheba and Dedan.

Context: After Sarah's death, Abraham took Keturah, and this verse lists their sons - among them Midian, whose descendants later become significant, sometimes as allies (Moses' father-in-law Jethro) and sometimes as opponents (the Midianite oppression in Judges) of Israel.

Meaning: Abraham's family tree keeps expanding even in his old age, producing yet more nations. Midian in particular will have a long, complicated relationship with Israel - by turns connected by marriage and locked in real conflict.

Lesson: Relationships between families and peoples are rarely simply good or bad across their whole history - they shift. Hold space for that complexity rather than reducing any group to a single story.

See Also: Exodus 3:1 - Moses' father-in-law Jethro, a priest of Midian; Judges 6-7 - Gideon's later war against Midianite oppression.

1:33KJV And the sons of Midian; Ephah, and Epher, and Henoch, and Abida, and Eldaah. All these are the sons of Keturah.

B:E Project The sons of Midian were Ephah, Epher, Henoch, Abida, and Eldaah. All these were descendants of Keturah.

Context: This closes the genealogy of Abraham's sons by Keturah, before the text turns fully to Isaac's line in the next verse.

Meaning: This finishes off the 'side' branches of Abraham's family - the sons of Ishmael and now the sons of Keturah - so that the narrative can properly focus on Isaac, the promised line, without losing sight that these other families were real and counted too.

Lesson: Before moving on to what matters most to your own story, it's worth pausing to properly honour the people and paths that aren't your main focus. Nobody should feel like an afterthought.

See Also: Genesis 25:1-4 - the source list of Keturah's sons and grandsons.

1:34KJV And Abraham begat Isaac. The sons of Isaac; Esau and Israel.

B:E Project Abraham fathered Isaac. Isaac's sons were Esau and Israel.

Context: This verse marks the pivotal transition into Jacob's story - here called by his later name Israel - though the birth of the twins and the whole account of Esau selling his birthright and Jacob receiving Isaac's blessing lie behind this single compressed line.

Meaning: Using the name 'Israel' rather than 'Jacob' here is deliberate - it looks past all the deception and struggle of Jacob's early life straight to what he became: the man whose name the entire nation would carry.

Lesson: You are not only your worst or most complicated choices. Jacob wrestled - literally, in the story - with who he was, and came out the other side renamed and repurposed. Growth like that is always available to you too.

See Also: Genesis 25:24-26 - the birth of the twins Esau and Jacob; Genesis 32:28 - Jacob renamed Israel after wrestling through the night.

1:35KJV The sons of Esau; Eliphaz, Reuel, and Jeush, and Jaalam, and Korah.

B:E Project The sons of Esau were Eliphaz, Reuel, Jeush, Jaalam, and Korah.

Context: The text now turns to Esau's genealogy, tracing the line that becomes the nation of Edom, Israel's neighbour and frequent rival, before circling back to Jacob/Israel's own twelve sons in chapter 2.

Meaning: Esau, who lost the birthright and blessing to his brother Jacob, still gets a full genealogical record here, becoming the ancestor of an entire, historically significant nation. The Bible doesn't diminish him just because the covenant line ran elsewhere.

Lesson: Losing out on one specific opportunity doesn't mean your whole future is diminished. Esau still built a substantial legacy - what you do with what remains matters just as much as what you didn't get.

See Also: Genesis 36:1-5 - the fuller Genesis account of Esau's sons and his identification with Edom.

1:36KJV The sons of Eliphaz; Teman, and Omar, Zephi, and Gatam, Kenaz, and Timna, and Amalek.

B:E Project The sons of Eliphaz were Teman, Omar, Zephi, Gatam, Kenaz, Timna, and Amalek.

Context: This lists Esau's grandsons through Eliphaz, including Amalek - ancestor of the Amalekites, who become one of Israel's most persistent and bitter later enemies, from the wilderness attack in Exodus through to Saul's and David's wars.

Meaning: Amalek's name here, tucked into an otherwise routine list, is genealogically significant - it explains that Israel's ancient enemy the Amalekites actually descended from Esau's own family, making the later Israel-Amalek conflict, in a sense, a fight within an extended family.

Lesson: Some of the deepest conflicts happen between people who are, underneath it all, closer relatives - literally or figuratively - than either side remembers. Recognising a shared root doesn't excuse harm done, but it can soften how you carry the grievance.

See Also: Exodus 17:8-16 - Amalek's first attack on Israel in the wilderness; 1 Samuel 15 - Saul's later war against the Amalekites.

1:37KJV The sons of Reuel; Nahath, Zerah, Shammah, and Mizzah.

B:E Project The sons of Reuel were Nahath, Zerah, Shammah, and Mizzah.

Context: This continues Esau's genealogy through his son Reuel, one of several grandsons who become tribal ancestors within Edom.

Meaning: As with earlier lists, these names build out the structure of a real, organised neighbouring nation - Edom wasn't a loose collection of wanderers but had its own clear tribal and family organisation, just like Israel.

Lesson: It's worth remembering that people and nations you might think of mainly as rivals or outsiders have just as much internal structure, history, and dignity as your own. Nobody is a footnote in their own story.

See Also: Genesis 36:13 - the parallel Genesis listing of Reuel's sons.

1:38KJV And the sons of Seir; Lotan, and Shobal, and Zibeon, and Anah, and Dishon, and Ezar, and Dishan.

B:E Project The sons of Seir were Lotan, Shobal, Zibeon, Anah, Dishon, Ezar, and Dishan.

Context: The text now shifts to Seir 'the Horite', the original inhabitant of the region that becomes Edom before Esau's descendants settled and intermarried there - Seir's people were absorbed into or displaced by Esau's line.

Meaning: This is a genealogy of the land's earlier population, not Esau's own bloodline - a reminder that Edom, like Canaan, had prior inhabitants whose story is preserved here rather than simply erased.

Lesson: When you inherit a place, a role, or an opportunity, remember there were usually people there before you, with their own full lives. Recording their names, as this chapter does, is a small act of respect worth imitating.

See Also: Genesis 36:20-21 - the parallel Genesis listing of Seir's Horite descendants.

1:39KJV And the sons of Lotan; Hori, and Homam: and Timna was Lotan’s sister.

B:E Project The sons of Lotan were Hori and Homam; and Timna was Lotan's sister.

Context: This continues the Horite genealogy; this Timna, sister of Lotan, is likely connected to the concubine Timna mentioned later in Esau's family (Genesis 36:12), whose son was Amalek.

Meaning: Naming a sister here, not just sons, is notable - genealogies in this era usually record only male lines, so Timna's specific mention suggests she was a person of some particular importance or memorable connection within the family's history.

Lesson: Notice who tends to get left out of the record, and make a point of remembering them anyway. Everyone's contribution to a family's or a community's story deserves to be counted, not just the ones the usual system tracks.

See Also: Genesis 36:12 - a Timna named as Eliphaz's concubine and Amalek's mother, likely the same figure.

1:40KJV The sons of Shobal; Alian, and Manahath, and Ebal, Shephi, and Onam. And the sons of Zibeon; Aiah, and Anah.

B:E Project The sons of Shobal were Alian, Manahath, Ebal, Shephi, and Onam. The sons of Zibeon were Aiah and Anah.

Context: This continues the Horite tribal genealogy of Seir, listing further grandsons within the region that becomes Edom.

Meaning: The steady accumulation of names across this section builds a detailed, almost administrative picture of how thoroughly this neighbouring people's family structure was recorded - on a level of detail matching Israel's own tribal lists elsewhere in Chronicles.

Lesson: Thoroughness and care in keeping track of people - even people outside your own group - reflects a kind of respect worth practising in ordinary life: really knowing the people around you by name, not treating anyone as a blur in the background.

See Also: Genesis 36:23-24 - the parallel Genesis source for these same names.

1:41KJV The sons of Anah; Dishon. And the sons of Dishon; Amram, and Eshban, and Ithran, and Cheran.

B:E Project The sons of Anah were Dishon. The sons of Dishon were Amram, Eshban, Ithran, and Cheran.

Context: This continues the detailed Horite genealogy, narrowing in on Anah's branch of the family within the region of Seir/Edom.

Meaning: This verse is purely structural - it exists to preserve exact family relationships for a community whose detailed history mattered enough to record precisely, even though almost none of these individuals appear anywhere else in the Bible.

Lesson: Most people who have ever lived leave no dramatic story behind - just their place in a family. That quiet, unremarked existence is still worth honouring; you don't need to be famous for your life to have counted.

See Also: Genesis 36:25-26 - the parallel Genesis listing, with minor spelling variations of these same names.

1:42KJV The sons of Ezer; Bilhan, and Zavan, and Jakan. The sons of Dishan; Uz, and Aran.

B:E Project The sons of Ezer were Bilhan, Zavan, and Jakan. The sons of Dishan were Uz and Aran.

Context: This closes the genealogy of Seir the Horite, completing the list of the land's earlier tribal inhabitants before the chapter turns to list the actual kings who ruled Edom.

Meaning: This final verse of the Horite section notably reuses the name Uz - the same name given earlier (verse 17) to a son of Aram in Shem's line - another reminder that ancient names recur across unrelated branches of these genealogies.

Lesson: Don't assume a shared label always means a shared identity. Look past the surface name to the actual person or situation underneath before drawing conclusions.

See Also: Genesis 36:28 - the parallel Genesis listing closing the Horite genealogy.

1:43KJV Now these are the kings that reigned in the land of Edom before any king reigned over the children of Israel; Bela the son of Beor: and the name of his city was Dinhabah.

B:E Project These are the kings who reigned in the land of Edom before Israel had any king at all: Bela son of Beor, whose city was called Dinhabah.

Context: The text now shifts from genealogy to a king list - explicitly noting that Edom had an organised monarchy before Israel ever did, which is a striking detail for a book largely about Israel's own kings, especially David.

Meaning: This deliberate comparison - Edom had kings 'before any king reigned over the children of Israel' - sets up a quiet contrast the original readers would have felt keenly: Israel was, in a sense, 'behind' its neighbour in forming a kingdom, yet the following chapters of Chronicles will show Israel's kingship, under David, becoming something far more significant.

Lesson: Someone else starting before you, or seeming further ahead, doesn't determine how meaningful your own path will ultimately be. What matters isn't who arrives first, but what you build with faithfulness once you do arrive.

See Also: Genesis 36:31-32 - the parallel list in Genesis; 1 Samuel 8:5 - Israel later asking for a king 'like all the nations', including neighbours like Edom.

1:44KJV And when Bela was dead, Jobab the son of Zerah of Bozrah reigned in his stead.

B:E Project When Bela died, Jobab son of Zerah, from Bozrah, reigned in his place.

Context: This begins a sequence showing that Edom's kingship, unlike Israel's later hereditary dynasty under David, passed between different families and cities rather than father to son - suggesting a more elective or contested monarchy.

Meaning: Notice that Jobab isn't Bela's son - the throne moves to an entirely different family and city (Bozrah). This pattern, repeated throughout the list, shows Edom's kingship worked very differently from the dynasty Israel would establish under David, where the throne passed within one family line.

Lesson: Different communities organise leadership differently, and no single model is automatically 'correct'. Judge a system of leadership by whether it serves people justly, not simply by how closely it matches what you're used to.

See Also: Genesis 36:33 - the parallel Genesis account of Jobab's reign.

1:45KJV And when Jobab was dead, Husham of the land of the Temanites reigned in his stead.

B:E Project When Jobab died, Husham, from the land of the Temanites, reigned in his place.

Context: The kingship again transfers to another region entirely - the Temanites, whose name derives from Teman, a grandson of Esau mentioned earlier in verse 36.

Meaning: The recurring pattern - throne moving between regions rather than within one family - continues, reinforcing that Edom's early monarchy functioned more like a rotating leadership among its major clans than a single dynasty.

Lesson: Leadership doesn't have to be inherited to be legitimate. Different communities have found different fair ways to decide who leads, and it's worth respecting that variety rather than assuming only one way is 'proper'.

See Also: Genesis 36:34 - the parallel Genesis account; 1 Chronicles 1:36 - Teman named earlier as Eliphaz's son, the namesake of this region.

1:46KJV And when Husham was dead, Hadad the son of Bedad, which smote Midian in the field of Moab, reigned in his stead: and the name of his city was Avith.

B:E Project When Husham died, Hadad son of Bedad reigned in his place - the same Hadad who defeated Midian in the territory of Moab; his city was called Avith.

Context: This is one of the few Edomite kings given a specific accomplishment - a military victory over Midian, fought notably in Moabite territory, showing Edom actively engaged in regional conflicts of its own.

Meaning: Unlike most names in this chapter, Hadad gets an actual deed attached to his name - he won a real battle in a real place. It's a small but telling detail: this isn't just an abstract list, it's the record of an active, contending nation with its own history of war and territory.

Lesson: Behind every list of names in history are real struggles, real victories, and real losses that shaped people's lives. It's worth remembering that every nation and every family has had to fight for what it holds, in one way or another.

See Also: Genesis 36:35 - the parallel Genesis account of this same battle and king.

1:47KJV And when Hadad was dead, Samlah of Masrekah reigned in his stead.

B:E Project When Hadad died, Samlah, from Masrekah, reigned in his place.

Context: The kingship passes again to a new region, continuing the non-hereditary pattern seen throughout this list of early Edomite kings.

Meaning: Samlah's brief mention keeps the pattern going without adding new detail - by this point in the list, the repeated formula itself becomes the point: kingship in Edom kept moving, generation after generation, without settling into one family.

Lesson: Sometimes life keeps moving in a steady, repeating rhythm without a dramatic highlight in every chapter, and that's completely normal. Not every stage of your life needs a headline; steady continuation has its own value.

See Also: Genesis 36:36 - the parallel Genesis listing of Samlah's reign.

1:48KJV And when Samlah was dead, Shaul of Rehoboth by the river reigned in his stead.

B:E Project When Samlah died, Shaul, from Rehoboth by the river, reigned in his place.

Context: This Shaul (a name later shared, in Hebrew, by Israel's first king Saul) ruled from a city by a river - likely referring to a location near the Euphrates.

Meaning: It's worth noting this Edomite king shares a name with Israel's own first king, Saul - purely coincidental in terms of family, but a small reminder that the same names recur across different nations in the ancient Near East, not just within one people's genealogy.

Lesson: Sharing a name, a role, or a title with someone else doesn't make your story the same as theirs. Every person still has to write their own chapter, regardless of who else has carried the same name before.

See Also: Genesis 36:37 - the parallel Genesis account; 1 Samuel 9:2 - Saul, Israel's first king, sharing this Edomite king's name.

1:49KJV And when Shaul was dead, Baalhanan the son of Achbor reigned in his stead.

B:E Project When Shaul died, Baalhanan son of Achbor reigned in his place.

Context: The list of Edomite kings continues its pattern of transfer between families, nearing its end as it approaches the final named king, Hadad.

Meaning: Baalhanan's name contains 'Baal', the name of a Canaanite god, embedded within it - a small but telling detail about the religious world Edom's royal family lived in, quite different from Israel's calling to worship one God alone.

Lesson: The names and language people use often carry the beliefs of their culture, even without anyone consciously choosing them. Pay attention to what's baked into the language and habits you've inherited, and decide deliberately what you actually want to carry forward.

See Also: Genesis 36:38 - the parallel Genesis listing of Baalhanan's reign.

1:50KJV And when Baalhanan was dead, Hadad reigned in his stead: and the name of his city was Pai; and his wife’s name was Mehetabel, the daughter of Matred, the daughter of Mezahab.

B:E Project When Baalhanan died, Hadad reigned in his place; his city was called Pai, and his wife's name was Mehetabel, daughter of Matred, daughter of Mezahab.

Context: This is the final named king in Edom's early list, and unusually, his wife and her family line are recorded too - a level of personal detail not given for any of the earlier kings.

Meaning: Naming a queen and tracing her own family back two generations is unusual in this chapter and signals her particular significance - genealogies in this period rarely bothered to record women's names at all, so Mehetabel's inclusion, in some detail, stands out as deliberate and meaningful.

Lesson: When a record goes out of its way to include someone the usual pattern would have skipped, that's worth noticing and honouring. Look for the people in your own life who are quietly significant even when the usual spotlight passes them by.

See Also: Genesis 36:39 - the parallel Genesis account, also naming Mehetabel and her family.

1:51KJV Hadad died also. And the dukes of Edom were; duke Timnah, duke Aliah, duke Jetheth,

B:E Project Hadad also died. Then the chiefs of Edom were: chief Timnah, chief Aliah, chief Jetheth,

Context: The text shifts from kings back to a list of tribal chiefs ('dukes' in the KJV's older translation, more accurately clan leaders), marking a transition after the last named king, possibly reflecting a later period of Edom's history without a single monarch.

Meaning: After Hadad, no further king is named - instead, Edom is shown governed by a council of clan chiefs. This shift in structure, quietly noted, shows that Edom's political organisation kept changing over time, just as Israel's own would later shift between judges, kings, and other forms of leadership.

Lesson: How a community organises its leadership can change more than once across history, and that's not a failure - it's often just an honest adaptation to a new season. Don't assume the current arrangement of anything is permanent.

See Also: Genesis 36:40 - the parallel Genesis account of Edom's chiefs.

1:52KJV Duke Aholibamah, duke Elah, duke Pinon,

B:E Project Chief Aholibamah, chief Elah, chief Pinon,

Context: This continues the list of Edomite clan chiefs, several of whose names - like Aholibamah - match names of Esau's actual wives mentioned in Genesis, suggesting these chiefly clans were named after specific ancestral women and men.

Meaning: Aholibamah was, according to Genesis 36:2, actually one of Esau's wives - so this clan is likely named directly after her, showing again how women's names could become permanently attached to entire family and tribal identities.

Lesson: A person's name and legacy can outlast them by centuries, shaping how an entire community identifies itself long after they're gone. What you build your life around has a way of becoming part of something much bigger than just you.

See Also: Genesis 36:2 - Aholibamah named as one of Esau's wives; Genesis 36:41 - the parallel chief-list in Genesis.

1:53KJV Duke Kenaz, duke Teman, duke Mibzar,

B:E Project Chief Kenaz, chief Teman, chief Mibzar,

Context: This continues the list of Edom's clan chiefs, with names like Kenaz and Teman echoing earlier names in Esau's genealogy (verse 36), reinforcing that these chiefdoms were rooted in specific family branches.

Meaning: By this point the chapter is drawing clear lines between individual ancestors named earlier and the territorial or clan identities that grew out of them - a pattern of 'a person's name becomes a place's or a people's name' that runs right through ancient genealogies.

Lesson: The influence of one life can spread outward to shape a whole community's identity for generations. Live in a way that, whatever legacy follows your name, it's something genuinely worth carrying forward.

See Also: Genesis 36:42 - the parallel Genesis listing of these same chiefs.

1:54KJV Duke Magdiel, duke Iram. These are the dukes of Edom.

B:E Project Chief Magdiel, chief Iram. These were the chiefs of Edom.

Context: This closes both the list of Edom's chiefs and the entire chapter, completing the sweep from Adam, the first human, all the way down through Noah, Abraham, Esau, and now Edom's full leadership structure.

Meaning: The chapter's very last words - 'these are the dukes of Edom' - quietly close out an enormous span of history, from the creation of humanity to a detailed neighbouring nation's leadership, before Chronicles turns, in chapter 2, to finally focus on Israel's own twelve tribes, which is the real subject the whole book is building towards.

Lesson: A long, patient build-up often precedes the part of the story that actually matters most to you. I ask you to have that same patience - the foundational, unglamorous work of establishing context is never wasted, even when the real point is still to come.

See Also: Genesis 36:43 - the parallel closing verse in Genesis; 1 Chronicles 2:1 - the very next chapter, finally turning to list Israel's own twelve sons.