Domain scope
Start with age, location and household context, then inspect the resident references that connect the wider city.
Read the published guide →Nairobi · People & society
Demographics.
Explore population and household records.
Start with age, location and household context, then inspect the resident references that connect the wider city.
Public sample available
Published domain facts
- Citizens
- 5.1M+
- Birth records
- 5.0M+
- Death records
- 396K+
- Historical range
- 1940–2026
Overview
Public sample access
Public sample available
Preview samples & fields →Known limits
Early population histories use aggregate reconstruction and sometimes national or regional evidence rather than city observations. Migration evidence is uncertain. Aggregate fit does not establish that any individual synthetic life occurred.
Review the source limits →Full scope reference 2 documented sections
Published domain scope.
Published domain scope.
Births, deaths, migration and residence histories form the synthetic population. Persistent citizen references connect these records across the city.
- Compare age bands and residence status
- Inspect population context by ward
- Check the identity fields needed for a join
- Citizens
- 5.1M+
- Birth records
- 5.0M+
- Death records
- 396K+
- Historical range
- 1940–2026
Domain scope.
Domain scope.
Inspect the published scope and deployment boundaries.
Read the published detail
FCTE reconstructs a synthetic population through time — births, deaths, age, sex, migration, origin and other demographic characteristics — creating the citizens that every connected domain builds upon.
These aren't independent demographic records. The same synthetic citizens continue into households, education, employment, health, housing, transport and the rest of the city.
Nairobi City Twin™ · 1940–2026
Samples & fields
Published sample records.
Public sample · rows and field definitions
Public sample
| Resident name | Age | Age group (5 years) | Gender | Ward name | Residency status | Household type | Resident reference |
|---|---|---|---|---|---|---|---|
| Ekiru Ekwam | 39 | 35-39 | M | Eastleigh North | Diaspora | Extended | 4760612 |
| Okingo Nyairo Gesare | 24 | 20-24 | M | Kahawa West | Resident | SinglePerson | 2545925 |
| Nkoitoi Ngugi | 8 | 5-9 | F | Lucky Summer | Resident | Nuclear | 1128385 |
Showing 3 of 100 sample rows and 8 of 54 fields. “Not recorded” is a display label; downloads retain original values.
Published field definitions · 8 visible fields
Resident name
The full name assigned to the synthetic resident.
Original field: FullName
Example: Ekiru Ekwam
Age
The resident’s age in years in this record.
Original field: Age
Example: 39
Age group (5 years)
The five-year age range containing the resident’s age.
Original field: AgeBand5Yr
Example: 35-39
Gender
The gender recorded for the synthetic resident; M and F denote male and female in these samples.
Original field: Gender
Example: Male
Ward name
The name recorded for the ward associated with this record.
Original field: WardName
Example: Eastleigh North
Residency status
The resident’s recorded relationship to the city, such as resident or diaspora.
Original field: ResidencyStatus
Example: Diaspora
Household type
The recorded household structure, such as a single-person or extended household.
Original field: HouseholdType
Example: Extended
Resident reference
The synthetic resident reference used to connect this record to other city data.
Original field: CitizenId
Example: 4760612
Complete published field dictionary · 54 fields
CitizenIdResident reference- The synthetic resident reference used to connect this record to other city data.Example: 4760612
FullNameResident name- The full name assigned to the synthetic resident.Example: Ekiru Ekwam
SnapshotDateSnapshot date- The date represented by this extract of the synthetic data.Example: 2026-07-02
DOBDate of birth- The resident’s recorded date of birth.Example: 1987-05-20
AgeAge- The resident’s age in years in this record.Example: 39
AgeBand5YrAge group (5 years)- The five-year age range containing the resident’s age.Example: 35-39
GenderGender- The gender recorded for the synthetic resident; M and F denote male and female in these samples.Example: Male
EthnicGroupIdEthnic group reference- The reference used to identify the ethnic group associated with this record.Example: 11
EthnicGroupEthnic group- The ethnic group assigned to the synthetic resident.Example: Turkana
HasNationalIdNational ID recorded- Whether a national identity reference is recorded for the resident. In the source file, 1 means yes and 0 means no.Example: Yes
RegistrationDateRegistration date- The date recorded for the registration event.Example: 2020-01-01
ResidencyStatusResidency status- The resident’s recorded relationship to the city, such as resident or diaspora.Example: Diaspora
IsPhysicallyResidentPhysically resident- Whether the resident is recorded as physically living in the city. In the source file, 1 means yes and 0 means no.Example: No
IsCurrentlyPhysicallyResidentCurrently living in the city- Whether the resident is recorded as physically present in the city at the current snapshot. In the source file, 1 means yes and 0 means no.Example: No
CurrentCountryCodeCurrent country code- The country code recorded for the resident’s current location.Example: GB
DepartureDateDeparture date- The recorded date on which the resident left the city.Example: 1990-12-19
WardIdWard reference- The reference used to identify the ward associated with this record.Example: 72
WardNameWard name- The name recorded for the ward associated with this record.Example: Eastleigh North
WardIncomeMultiplierWard income factor- The factor used to adjust modelled income for the ward; it is not a currency amount.Example: 0.55
WardInformalSectorRateWard informal work rate- The ward-level rate used to model informal employment. Values are shown in their published scale.Example: 0.70
HouseholdIdHousehold reference- The reference used to identify the household associated with this record.Example: 516803
HouseholdCodeHousehold code- The published code identifying the household. Codes are retained as supplied in the source.Example: HH001596245
HouseholdTypeHousehold type- The recorded household structure, such as a single-person or extended household.Example: Extended
HouseholdFormationDateHousehold formation date- The date recorded for the household formation event.Example: 1987-06-29
HouseholdSizePeople in household- The number of residents recorded in the household.Example: 3
RelationshipCodeRelationship to household head- The recorded relationship between this resident and the household head.Example: Head
IsHouseholdHeadHousehold head- Whether this resident is recorded as the head of the household. In the source file, 1 means yes and 0 means no.Example: Yes
IsForeignOriginForeign origin recorded- Whether a foreign-origin flag is set for the synthetic resident. In the source file, 1 means yes and 0 means no.Example: No
OriginPathwayOrigin pathway- The recorded route by which the resident entered the modelled population. Coded values retain their published meaning.Example: HistoricalDescent
OriginCountryCodeCountry of origin code- The country code recorded for the resident’s origin.Example: IN
OriginEventDateOrigin event date- The date recorded for the origin event.Example: 2019-05-18
LifetimeMigrationCountRecorded moves- The number of migration events recorded across the resident’s synthetic lifetime.Example: 0
MostRecentMigrationDateMost recent migration date- The date recorded for the most recent migration event.Example: 2019-04-13
MostRecentMigrationTypeLatest move type- The type of the most recently recorded migration event.Example: Out
MostRecentMigrationReasonLatest move reason- The stated reason for the most recently recorded migration event.Example: Safety
MostRecentFromWardLatest move: previous ward- The ward recorded as the origin of the resident’s latest move.Example: 82
MostRecentToWardLatest move: destination ward- The ward recorded as the destination of the resident’s latest move.Example: 85
IsDeceasedDeath recorded- Whether the resident is recorded as deceased in the synthetic lifecycle. In the source file, 1 means yes and 0 means no.Example: No
DeathDateDeath date- The date recorded for the death event.Example: 2022-04-28
AgeAtDeathAge at death- The recorded age, in years, when the synthetic resident died.Example: 26
DeathCauseCategoryCause of death category- The broad cause category recorded for a synthetic death event.Example: Disease
WasBirthRegisteredBirth registered- Whether the resident’s birth was recorded as registered. In the source file, 1 means yes and 0 means no.Example: No
BirthFacilityIdBirth facility reference- The reference used to identify the birth facility associated with this record.Example: Not provided
IsDependencyAgeDependent-age group- Whether the resident falls within the age group the source labels as dependent. The extract does not define the age thresholds. In the source file, 1 means yes and 0 means no.Example: No
IsWorkingAgeWorking-age group- Whether the resident falls within the source’s working-age group. The extract does not define the age thresholds. In the source file, 1 means yes and 0 means no.Example: Yes
EthnicGroupPopCountEthnic group population- The published population count for this ethnic group in the synthetic city.Example: 97000
WardPopCountWard population- The published population count for this ward in the synthetic city.Example: 115801
TotalPopulationTotal city population- The total population figure included in the synthetic city snapshot.Example: 5081174
SampleEthnicGroupSharePctEthnic group share of sample (%)- The percentage of sample records assigned to this ethnic group.Example: 3.0000
PopulationEthnicGroupSharePctEthnic group share of population (%)- The published percentage of the synthetic population assigned to this ethnic group.Example: 1.9090
EthnicGroupReweightFactorEthnic group weighting factor- The published adjustment factor for comparing the ethnic group’s sample share with its population share.Example: 0.6363
SampleWardSharePctWard share of sample (%)- The percentage of sample records assigned to this ward.Example: 4.0000
PopulationWardSharePctWard share of population (%)- The published percentage of the synthetic population assigned to this ward.Example: 2.2790
WardReweightFactorWard weighting factor- The published adjustment factor for comparing the ward’s sample share with its population share.Example: 0.5697
Additional records and schema context 1 documented sections
Records and relationships.
Records and relationships.
Inspect representative records, fields and relationships.
Read the published detail
View Complete Data Dictionary →
Three rows from the same 100-row, 54-field public Demographics sample available in Data Explorer and the CSV download. The sample is synthetic and age-stratified; no row represents a real individual.
Explore all 100 sample rows →
| Entity | Represents |
| Citizen | Persistent synthetic citizen — DOB, Gender, National, Ward, RegistrationDate, ResidencyStatus |
| Birth | Civil birth registration — one row per citizen, linked to MotherCitizen where traceable |
| Death | Civil death registration — one row per citizen, with CauseCategory |
| CitizenOrigin | How a citizen entered the population — HistoricalDescent, Marriage, Descent, Naturalization or Pregnancy |
| Migration | Population movement — In / Out / Internal, with origin and destination ward |
| Household / HouseholdMember | Citizen's household context, including join/leave dates and relationship role |
| PopulationSnapshot | Periodic ward-level population aggregates used for calibration |
| Citizen ID | Age band | Sex | Ethnic group | Ward | Residency | Lifecycle |
| 2545925 | 20-24 | M | Kisii | Kahawa West | Resident | Living resident |
| 4760612 | 35-39 | M | Turkana | Eastleigh North | Diaspora | Diaspora |
| 202036 | 25-29 | M | Kamba | workflow | Resident | Deceased |
Connections
Known and possible relationships
Review the supported links between domains and their availability.
| Domain or context | Relationship and published scope |
| Households | Citizen membership connects residents to household roles and family transitions. |
| Education, Health and Employment | The same synthetic resident identity supplies age, lifespan and location context to these domains. |
| Housing and Land | Households can be followed into housing and location context where the relevant references are supplied. |
| Business and Vehicles | Resident ownership context can be inspected where an owner reference is present. Private vehicle ownership and transport journeys are separate models. |
| Insurance | Coverage and claim activity can be analysed alongside the resident lifecycle. |
Full relationship reference 1 documented sections
Connected records.
Connected records.
Review the supported links between domains and their availability.
Read the published detail
Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.
| Domain or context | Relationship and published scope |
| Households | Citizen membership connects residents to household roles and family transitions. |
| Education, Health and Employment | The same synthetic resident identity supplies age, lifespan and location context to these domains. |
| Housing and Land | Households can be followed into housing and location context where the relevant references are supplied. |
| Business and Vehicles | Resident ownership context can be inspected where an owner reference is present. Private vehicle ownership and transport journeys are separate models. |
| Insurance | Coverage and claim activity can be analysed alongside the resident lifecycle. |
Domain guide
Demographics · archived guide edition
Striped Donkey V5.89 - 7 September 2026
Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.
Published scope and limits
Early population histories use aggregate reconstruction and sometimes national or regional evidence rather than city observations. Migration evidence is uncertain. Aggregate fit does not establish that any individual synthetic life occurred.
Read the source limits →Accessible HTML reference 5 documented sections
Modelled entities.
Modelled entities.
Explore the entities and states represented by this domain.
Read the published detail
Demographics establishes who exists in the synthetic city, when they entered the population, how population composition changes through time, and when citizens leave through death or migration.
Age, sex, birth cohort and population structure — 5.1M+ living and recorded citizens across Nairobi.
Birth histories and historically calibrated fertility behavior, linked to a real mother wherever one can be traced.
Deaths, age-specific mortality and historical mortality patterns, including a cumulative-hazard model for elderly citizens.
Population movement, migration timing, origin and demographic effects — In, Out and Internal movement types.
How citizens enter the synthetic population: historical descent, marriage, birth descent, general naturalization and pregnancy.
Demographic conditions evolve across decades — from a 1940s colonial-era baseline to the present — rather than applying today's structure retrospectively.
Synthetic by design: FCTE citizens do not correspond to real people. Demographic characteristics are generated from aggregate evidence, calibrated distributions and documented modeling rules.
Histories through time.
Histories through time.
Inspect dated lifecycle transitions and historical boundaries.
Read the published detail
A conventional synthetic population often represents a single snapshot. FCTE preserves demographic events and dates so citizens can participate in the evolving City Twin™ — real Household Lifecycle events (Departure, Marriage, Divorce, Widowhood, Remarriage) run against the same dated citizen record used everywhere else.
Demographics isn't merely upstream at initial generation. It remains relevant throughout the citizen's life.
Today's city wasn't generated in 1940
Today's city wasn't generated in 1940
Inspect the published definitions and release context.
Read the published detail
FCTE reconstructs population change across historical periods rather than applying a contemporary demographic distribution to every generation. Nairobi's own registration-event catalog is piecewise-weighted to its real civil-registration history, not spread evenly across the timeline.
colonial-era trickle — a small, slow-growing share of registration events, before Kenya had any independent civil registration system.
independence surge, anchored to the real Kenya ID Act of 1967.
rapid urbanisation and sustained urban migration into Nairobi.
the digital era begins with an eCitizen pilot, interrupted by a real, modeled dip around the 2007–2008 post-election violence period.
digital acceleration and Kenya's devolution wave.
Nairobi: a modeled 2020–2022 slowdown consistent with COVID-era disruption, followed by high-volume current registrations through 2026.
Historical coverage and evidence strength vary by metric and period. FCTE records those differences rather than treating every historical year as equally observed.
Explore Demographic Evidence →
Evidence becomes citizens
Evidence becomes citizens
Inspect the published definitions and release context.
Read the published detail
FCTE combines jurisdiction-specific demographic evidence with repeatable generation rules. Historical parameters determine population structure and change while bounded modeling fills gaps where direct observations do not exist.
Directly supported by published demographic evidence — UN World Population Prospects rates, KNBS census totals.
Calculated from observed statistics, e.g. crude birth/death rates computed against the living population.
Population growth, age structure, fertility, mortality and migration behavior are calibrated to cited demographic evidence and release-level checks. Exact weights, coefficients and thresholds remain controlled.
Individual synthetic assignments are generated under controlled domain rules. Exact sampling, assignment order and parameterization are not published.
View Generation Methodology →
Does the generated population look like the city?
Does the generated population look like the city?
Inspect the published definitions and release context.
Read the published detail
Release distributions from the current Nairobi City Twin™ — one public reality check, not a disclosure of the internal construction details.
Age bands in years, grouped in 10-year bands (80+ combined). Counts are living + deceased citizens by recorded date of birth.
Births and deaths grouped by decade, 1920s–2020s. Bars share one scale per city so the two series are directly comparable.
Every decade nets positive in Nairobi — consistent with certification check (population growth direction), which requires the younger half of the population to outnumber the older half.
Open Full Realism Report →
Evidence & limits
Scope and known limits
Early population histories use aggregate reconstruction and sometimes national or regional evidence rather than city observations. Migration evidence is uncertain. Aggregate fit does not establish that any individual synthetic life occurred.
Evidence, findings and release history 5 documented sections
Known limits.
Known limits.
Early population histories use aggregate reconstruction and sometimes national or regional evidence rather than city observations. Migration evidence is uncertain. Aggregate fit does not establish that any individual synthetic life occurred.
Read the published detail
Evidence before modern census and survey systems is less granular than contemporary demographic evidence. Early-period population and cohort structure are reconstructed from aggregate historical evidence and calibrated trends rather than individual observations.
Some historical demographic parameters are available at national or broad regional level but not at city resolution for Nairobi specifically. Where city-level observations are unavailable, the release records the broader evidence source and applies a disclosed calibration rather than presenting it as a direct city observation.
Historical migration is inherently harder to observe than births and deaths, particularly across informal urban populations — modeled with a variable confidence band, not a fixed benchmark.
Aggregate realism does not imply that any individual synthetic citizen's exact life history occurred in reality — this is a model boundary, not a claim about any one record.
View All Demographic Limitations →
Evidence and assumptions.
Evidence and assumptions.
Review the reference sources and calibration periods.
Read the published detail
National censuses, population estimates and official statistical publications.
Birth rates, fertility surveys and demographic estimates — crude birth rate calibrated to a 20–40 per 1,000 band.
Life expectancy, mortality rates, death statistics and international demographic series — crude death rate calibrated to a 3–15 per 1,000 band.
Census migration measures, urban growth evidence and historical population studies.
National demographic/household surveys used where population structure intersects household formation — mean household size calibrated to a 1.5–7.0 band.
Open Demographics Source Catalogue →
Does the model actually feel history — or just grow smoothly?
Does the model actually feel history — or just grow smoothly?
Inspect the published definitions and release context.
Read the published detail
Nairobi's birth-cohort size is computed two ways — a smooth baseline from pure population-curve interpolation, and a version modulated only by historical events with a documented fertility mechanism — then checked against what the data environment actually contains today. Charted from the platform's population growth model, its historical event calendar, and real generated-citizen birth-year counts, Nairobi.
Event registry
Open Full Population Pulse Dashboard →
See also: Event Ablation — each fertility-relevant historical event removed one at a time and re-tested against demographic survey benchmarks →
5.1 million citizens. Every one still has to make sense.
5.1 million citizens. Every one still has to make sense.
Inspect the published definitions and release context.
Read the published detail
Every release is checked against the full certification check–C21 structural battery, plus a separate 8-check realism pass (certification check–R08) — both run live against the current Nairobi release City Twin™.
A separate realism-adjacent audit (certification check/certification check) additionally checks that ward-level calibration inputs actually predict their own realized outputs, and is reported independently of the checks above.
Explore Every Demographics Check →
- certification check — Every citizen has a valid demographic identity
- certification check — household-member identity resolves to a real citizen
- certification check — No duplicate NationalId values
- certification check — Exactly one current household membership per citizen
- certification check — Death cannot precede birth
- certification check — Household membership cannot start before a citizen's own DOB
- certification check — Migration cannot precede a citizen's own DOB
- certification check — A citizen's household transitions never overlap
- certification check — Sex ratio stays within a 95–112 males-per-100-females band
- certification check / R03 — Crude birth and death rates stay within sourced UN WPP bands
- certification check — Population skews toward the younger half (growth direction)
- certification check — Mean household size stays within a 1.5–7.0 band
- certification check / C13 — Household head resolves to a valid current member
- certification check — Elderly mortality regression guard (≥15% of the 80+ cohort marked dead)
- certification check / C19 — Household role and dissolution coherence after lifecycle events
The population model evolves with the evidence
The population model evolves with the evidence
Inspect the published definitions and release context.
Read the published detail
View Full Demographics Change Log →
Access & datasets
Scope your data request
Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.
Review rights and delivery
Read the terms for public previews and commercial orders before requesting your extract.
Published access and recorded examples 1 documented sections
Explore this domain.
Explore this domain.
Demographics is the spine underneath Households, Health, Employment and Transport — every synthetic citizen's age, birth cohort, migration and mortality history lives here first, before it shows up anywhere else in the City Twin™.
Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™