They were the sons of Benjamin
Cited passages
The sons of Benjamin: Bela, Becher, Ashbel, Gera, Naaman, Ehi, Rosh, Muppim, Huppim, and Ard.
Genesis 46:21 lists Naaman and Ard as sons of Benjamin who migrated to Egypt. Numbers 26:40 lists Ard and Naaman as sons of Bela — making them Benjamin's grandsons, not his sons. Same names, different generational slots.
People have answered this in several ways; GEBible presents them as equal peers.
Cited passages
The sons of Benjamin: Bela, Becher, Ashbel, Gera, Naaman, Ehi, Rosh, Muppim, Huppim, and Ard.
And the sons of Bela were Ard and Naaman. Numbers 26:40
Cited passages
The sons of Bela were Ard and Naaman: the family of the Ardites; and of Naaman, the family of the Naamites.
Examining the tension
What follows is one scholar’s way of reading this disagreement — a critical-historical view that often concludes the texts genuinely disagree. It draws on the peer-reviewed sources listed below and stands as one position among the answers above, presented for transparency, not as GEBible’s position.
How critical scholarship weighs this: Leans toward a genuine contradiction
This summarizes where critical scholarship tends to land on this tension — a report on the field’s center of gravity, not GEBible’s own ruling.
Genesis 46:21 lists ten "sons of Benjamin" who went down to Egypt with Jacob: Bela, Becher, Ashbel, Gera, Naaman, Ehi, Rosh, Muppim, Huppim, and Ard. Numbers 26:40, in the wilderness census taken a generation or more later in the plains of Moab, places two of those names — Ard and Naaman — one rung lower on the family tree, listing them as "the sons of Bela" (Bela himself being Benjamin's firstborn in both rosters). On the Genesis reading the two men are Benjamin's sons; on the Numbers reading they are his grandsons through Bela. The names are identical and the relationship is incompatible.
The customary harmonization, argued by Archer and Walter Kaiser, is telescoping in reverse: Genesis 46:21 supposedly gathers Benjamin's wider household — sons and grandsons alike — under the loose clan-heading "sons of Benjamin," while Numbers 26 supplies the precise pedigree. The Hebrew בֵּן (ben) carries the burden, since it can denote a descendant generally rather than an immediate son, much as "the sons of Israel" names a whole nation. This is not impossible. The recurrence of the same names makes it plausible that the same individuals are in view, and "sons of Benjamin" can function as an eponymous header collecting later-attested family names under the founding ancestor. As a way of rendering Genesis and Numbers formally compatible, the move has genuine force.
Two problems weigh against treating the matter as cleanly resolved. First, the chronology strains. In the Joseph narrative Benjamin is repeatedly cast as the youngest son and as the *naʿar* ("lad"), the "little one" whose safety obsesses Jacob during the earlier journeys to Egypt (Genesis 43-44). Although the narrative spans years and Benjamin is no longer a small child by the descent in Genesis 46, the portrait of him as Jacob's tender, late-born favorite sits awkwardly with crediting him with ten sons — and, on the Numbers data, grandsons — at the migration. The friction is not that Benjamin must be an infant in chapter 46 but that the list's demographic depth pulls against the narrative's consistent characterization of him as the youngest, which is one reason critics read these rosters as schematic constructs rather than reportage.
Second, and more decisively, the Benjaminite genealogies do not merely disagree between Genesis and Numbers; they triangulate into incompatibility once the Chronicler is added — and, crucially, Chronicles is internally inconsistent with itself. 1 Chronicles 7:6 gives Benjamin three sons (Bela, Becher, Jediael), a roster matching neither Genesis nor Numbers in names or generation counts. But 1 Chronicles 8:1-2 then supplies a different set entirely (Bela, Ashbel, Aharah, Nohah, Rapha), so the divergence is not only between books but within a single book. There are thus at least three distinct Benjaminite list-traditions that cannot all be literally true together. It is fair to note that Numbers 26 is a clan census and 1 Chronicles 7-8 a multi-generational genealogy, so part of the divergence reflects differing genealogical scope; but the name discrepancy between 1 Chronicles 7:6 and 8:1 is not a matter of scope at all — it is two incompatible lists of Benjamin's own sons inside one composition.
Source and composition critics — Friedman, Baden, and Carr — locate Genesis 46:8-27 within the Priestly tribal-list tradition and observe that the Numbers 26 census, while related, draws on overlapping but non-identical data shaped to the needs of a military and inheritance census. The textual witnesses confirm that ancient readers already felt the friction: the Septuagint of Genesis 46:21 differs substantially from the Masoretic Text, redistributing the Benjaminite names across generations and even introducing grandsons in language drawn partly from Numbers 26, and the Samaritan Pentateuch preserves its own variant arrangement. Some scholars read these as harmonizing assimilation toward one another; whatever the precise intent, the variant readings show the lists were unstable and that scribes reworked them. Gary Knoppers's analysis of the Chronicler shows him reshaping received genealogies for theological and demographic purposes, not transcribing a fixed archive.
The telescoping defense can render Genesis and Numbers formally compatible by absorbing a generation into the elastic word "sons." But it does so by conceding that the tribal lists are schematic and divergent, and it cannot absorb the third, Chronicler tradition — discordant both with the Pentateuch and with itself — without admitting that the censuses do not fully agree.
Where the critical reading lands: superficially harmonizable via telescoping, but the broader multi-source list tradition (Genesis, Numbers, and an internally inconsistent Chronicles) is genuinely discordant.
Sources for this reading