Could a very small population grow dramatically over many generations? Change the assumptions, follow the arithmetic, and compare the results yourself.
Interactive Table of Nations experiment
Loading the experiment…
Visual Note: Character appearances are stylized for educational gameplay. They are not exact reconstructions of biblical individuals or a definitive map of how modern peoples descended from Noah's family.
What the model does
It begins with eight founder characters, applies explicit birth, death, aging, household, migration, and event assumptions, then switches mature settlements to bounded cohorts so large populations do not create millions of browser objects.
What it does not prove
Population arithmetic shows what follows from selected inputs. By itself it does not establish a historical founder count, chronology, migration route, or genetic feasibility.
Story and experiment
Story mode includes educational milestones. Free Experiment mode removes story anchors so presets such as the One Child Challenge can succeed, stagnate, or fail on their modeled assumptions.
Scripture, interpretation, and scenario assumptions
Scripture: Genesis 7:13 identifies Noah, his wife, his three sons, and their wives aboard the Ark.
Scripture: Genesis 8 uses the “mountains of Ararat” wording; the simulation does not claim an exact modern landing coordinate.
Scripture: Genesis 10–11 supplies the Table of Nations and Babel narrative context. Nimrod—not Nero—is associated with Babel’s kingdom context.
Scenario: Babel placement is configurable. Exact date not stated in Scripture.
Simulation: Fertility, mortality, settlement thresholds, events, and migration timing are visible model inputs—not biblical constants.
Methodology
Runs are deterministic for an engine version, seed, and parameter set. Simulation randomness is isolated from visual animation. Mature regions use cohorts grouped by region, lineage, sex, age band, and abstract marker class.
Appearance methodology
Founders use a broadly ancient Near Eastern / Mediterranean art direction. Later visual variation is cosmetic only and never changes fertility, mortality, migration, or success. The model does not equate Noah’s sons with modern races or continents.
Privacy
Active runs remain local to the application. Choosing Complete local run sends only a terminal aggregate summary—never individual people, yearly ticks, IP addresses, user agents, or biographies.
Frequently asked questions
Why use WebAssembly?
The simulation is built Wasm-first for predictable high-scale processing, while retaining Flutter’s generated JavaScript fallback for browsers that need it.
Are the routes exact history?
No. The map is a stylized educational route graph, not a claim about exact ancient borders or post-Flood paths.
Can I compare assumptions?
Yes. Choose a preset and seed, complete a terminal run, change one variable or preset, and compare the resulting population and elapsed years.