Glasgow Surname Project

Individual research record

James Glasgow

1670 – ?

Glasgow-3105 · 1 mapped association

Kilwinning, Ayrshire, Scotland→Death place unknown
View on mapOpen WikiTreeCompareReport a correction

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
2Evidence items
18Candidate leads
Birth
1670 · Kilwinning, Ayrshire, Scotland
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
Margaret (Park) Glasgow
Children
James Glasgow
Gender
Male
WikiTree
Glasgow-3105
Research clusters
Scotland One-Tree profile leads
Mapped descendants
1

Comparison context

These child positions and checks are the subject details used to rank possible parents below.

Naming sequence used by the parentage model

Paternal grandfather positionJames Glasgow (1689)
Maternal grandfather positionNot identifiable from dated child profiles
Maternal grandmother positionNot identifiable from dated child profiles
Paternal grandmother positionNot identifiable from dated child profiles

Known-position checks: 0 support · 0 conflict. Ordinals retain unnamed children and recognise reused names.

Relationship comparison

Potential parents or duplicates

Compare scored leads with the subject details above—not proof.

Higher-signal leadReview carefullyWeak lead

Possible fathers5 leads

Automated fit20/100
Weak Lead
Dates1645–?Generation25 years age gapRecorded placesGlasgow, Lanarkshire, Scotland · GlasgowIndependent clue breadth · 4Age · Same-Sex Generational Naming · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 25-year parent-child age gap (+18)
  • candidate's birth is 44 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 25-year parent-child age gap (+18)
  • candidate's birth is 44 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)
  • candidate's name matches the first dated son James Glasgow, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Automated fit20/100
Weak Lead
Dates1640–1686Generation30 years age gapRecorded placesScotland · Belfast, Ireland · BelfastIndependent clue breadth · 4Age · Same-Sex Generational Naming · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 30-year parent-child age gap (+18)
  • candidate's birth is 49 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 30-year parent-child age gap (+18)
  • candidate's birth is 49 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)
  • candidate's name matches the first dated son James Glasgow, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Show 3 lower-scoring possible fathers
Automated fit20/100
Weak Lead
Dates1634–?Generation36 years age gapRecorded placesBiggar, Lanarkshire, Scotland · Biggar — LanarkshireIndependent clue breadth · 4Age · Same-Sex Generational Naming · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 36-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 36-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)
  • candidate's name matches the first dated son James Glasgow, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Automated fit20/100
Weak Lead
Dates1626–?Generation44 years age gapRecorded placesInveresk and Musselburgh, Midlothian, Scotland · Musselburgh / InvereskIndependent clue breadth · 4Age · Same-Sex Generational Naming · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 44-year parent-child age gap (+18)
  • candidate's birth is 63 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 44-year parent-child age gap (+18)
  • candidate's birth is 63 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)
  • candidate's name matches the first dated son James Glasgow, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Automated fit19/100
Weak Lead
Dates1640–?Generationat least 30 years age gapRecorded placesSaint Cuthberts, Edinburgh, Midlothian, Scotland · EdinburghIndependent clue breadth · 5Age · Same-Sex Generational Naming · Sex-Aware Ordered Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • known spouse Helen (Clerk) Glasgow had a plausible maternal age (30) at the subject's birth (+7)
  • candidate's birth is 49 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • bounded birth date gives a parent-child age gap of at least 30 years (+10; true age remains uncertain)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • bounded birth date gives a parent-child age gap of at least 30 years (+10; true age remains uncertain)
  • candidate's birth is 49 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • known spouse Helen (Clerk) Glasgow had a plausible maternal age (30) at the subject's birth (+7)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)
  • candidate's name matches the first dated son James Glasgow, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Possible mothers5 leads

Automated fit26/100
Weak Lead
Dates1655–?Generation15 years age gapRecorded placesKilwinning, Ayrshire, Scotland · Kilwinning, Ayrshire, Scotland, United Kingdom · Kilwinning — AyrshireIndependent clue breadth · 5Age · Household · Local Sibling Birth · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 15-year parent-child age gap (+10)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • candidate's birth is 34 years before the subject's earliest dated child (1689), a marginal two-generation interval (+1)

No indexed conflict; documentary proof still required

Show complete scoring
  • possible 15-year parent-child age gap (+10)
  • candidate's birth is 34 years before the subject's earliest dated child (1689), a marginal two-generation interval (+1)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • same research cluster (+0; grouping is not kinship evidence)
  • a known child was born within 6 years of the subject (+1)
  • candidate has another child, Hew Glasgow, born 6 years from the subject in the same specific birth locality (+4; possible sibling-household clue)

Deductions and cautions: No indexed conflict; documentary proof still required

Automated fit25/100
Weak Lead
Dates1640–?Generation30 years age gapRecorded placesEdinburghIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 30-year parent-child age gap (+18)
  • candidate's birth is 49 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 30-year parent-child age gap (+18)
  • candidate's birth is 49 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • a candidate spouse matches the first dated son James Glasgow, the expected father position (+3; James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show 3 lower-scoring possible mothers
Automated fit25/100
Weak Lead
Dates1631–?Generation39 years age gapRecorded placesEdinburghIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 39-year parent-child age gap (+18)
  • candidate's birth is 58 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 39-year parent-child age gap (+18)
  • candidate's birth is 58 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • a candidate spouse matches the first dated son James Glasgow, the expected father position (+3; James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit21/100
Weak Lead
Dates1632–?Generation38 years age gapRecorded placesMusselburgh / InvereskIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 38-year parent-child age gap (+18)
  • candidate's birth is 57 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate already has another child named James Glasgow (Glasgow-1376) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show complete scoring
  • plausible 38-year parent-child age gap (+18)
  • candidate's birth is 57 years before the subject's earliest dated child (1689), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • a candidate spouse matches the first dated son James Glasgow, the expected father position (+3; James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate already has another child named James Glasgow (Glasgow-1376) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Automated fit19/100
Weak Lead
Dates1659–?Generationnominally 11 years; approximate dates permit about 15–21 years age gapRecorded placesKilwinning, Ayrshire, Scotland · Kilwinning — AyrshireIndependent clue breadth · 4Age · Local Sibling Birth · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • the nominal 11-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–21 years) (+4)
  • candidate's birth is 30 years before the subject's earliest dated child (1689), a marginal two-generation interval (+1)

parentage requires the approximate birth estimate to be early enough (no deduction)

Show complete scoring
  • the nominal 11-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–21 years) (+4)
  • candidate's birth is 30 years before the subject's earliest dated child (1689), a marginal two-generation interval (+1)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate has another child, John Glasgow, born 9 years from the subject in the same specific birth locality (+4; possible sibling-household clue)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction)

How parent leads are calculated

Automated leads use birth surnames—not married surnames—as parental eligibility, role-specific biological age limits, bounded and approximate-date uncertainty, household chronology, specific time-aware localities, mapped distance, tenancy succession, migration destinations and sex-aware Scottish naming positions across generations. People already attached as the subject's parents stay in the identity summary and are excluded from this alternative-candidate list, regardless of relationship confidence. The main calibration uses clues available on disconnected profiles; existing parent and sibling links are retained as comparison context rather than treated as transferable evidence. Common ordered names and grandparent-to-child echoes receive a small non-zero weight, so a John or James match can support several independent criteria without producing a lead alone. Rare names, repeated bearers and bundles across otherwise distinct branches receive substantially more weight according to catalogue frequency. An exact migration place is weighted by its rarity and repetition across both branches; a shared destination country is worth only one point. Extra weight is added only when at least three independent clue types converge: naming, locality, specific migration, household chronology or collateral networks. Sparse profiles retain a clearly labelled chronology-only fallback instead of disappearing. Countries, states, counties and research clusters do not count as a shared locality, and fallback, broad representative or kin-inferred coordinates are excluded from distance scoring. Shared descendant profiles are removed before branch-name comparison. A candidate already recorded as a parent-in-law is excluded. A confident or independently supported parent is treated as settled; uncertain and unassessed attachments remain open to alternative comparison. A different linked parent, an uncle/aunt or grandparent path, and a matching existing child profile prevent an alternative from being classified as a strong direct-parent lead until the underlying tree conflict or duplicate is resolved. Familiar forms such as Bessie are normalised. Surname remains an eligibility filter worth zero points.

Naming customs, shared farms and occupations are circumstantial. Children, spouses and collateral relatives may be missing, and tree-derived family networks are not independent evidence. Scores rank research leads; they do not prove parentage.

Same-name candidate

James GlasgowGlasgow-3969

Automated fit70/100
Similar Person
Dates1670–?PlacesAyrshire, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)
  • overlapping locality (+8)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)
  • overlapping locality (+8)
  • matching child name: James Glasgow

Conflicts: No indexed conflict

Open side-by-side comparison
Automated fit42/100
Similar Person
Dates1680–1753PlacesIreland → Worcester County, MarylandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 10 (+10)
  • matching child name: James Glasgow

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 10 (+10)
  • matching child name: James Glasgow

Conflicts: No indexed conflict

Open side-by-side comparison

Same-name candidate

James GlasgowGlasgow-2682

Automated fit34/100
Similar Person
Dates1655–?PlacesMidlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 15 (+2)
  • matching child name: James Glasgow

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 15 (+2)
  • matching child name: James Glasgow

Conflicts: No indexed conflict

Open side-by-side comparison

Same-name candidate

James GlasgowGlasgow-1150

Automated fit32/100
Similar Person
Dates1620–?PlacesInveresk and Musselburgh, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • matching child name: James Glasgow

record-derived birth estimates differ by 50; retained without deduction

Full comparison detail
  • same first and last name (+18)
  • matching child name: James Glasgow

Conflicts: record-derived birth estimates differ by 50; retained without deduction

Open side-by-side comparison
Show 4 lower-scoring duplicate lead(s)

Same-name candidate

James GlasgowGlasgow-3337

Automated fit32/100
Similar Person
Dates1640–?PlacesEdinburgh, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • matching child name: James Glasgow

record-derived birth estimates differ by 30; retained without deduction

Full comparison detail
  • same first and last name (+18)
  • matching child name: James Glasgow

Conflicts: record-derived birth estimates differ by 30; retained without deduction

Open side-by-side comparison

Same-name candidate

James GlasgowGlasgow-2988

Automated fit32/100
Similar Person
Dates1720–?PlacesDerryloran, Cookstown, County Tyrone, IrelandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • matching child name: James Glasgow

record-derived birth estimates differ by 50; retained without deduction

Full comparison detail
  • same first and last name (+18)
  • matching child name: James Glasgow

Conflicts: record-derived birth estimates differ by 50; retained without deduction

Open side-by-side comparison

Same-name candidate

James GlasgowGlasgow-3130

Automated fit32/100
Similar Person
Dates1770–?PlacesScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • matching child name: James Glasgow

record-derived birth estimates differ by 100; retained without deduction

Full comparison detail
  • same first and last name (+18)
  • matching child name: James Glasgow

Conflicts: record-derived birth estimates differ by 100; retained without deduction

Open side-by-side comparison

Same-name candidate

James GlasgowGlasgow-3076

Automated fit28/100
Similar Person
Dates1661–?PlacesSaint Cuthberts, Edinburgh, Midlothian, ScotlandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 9 (+10)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 9 (+10)

Conflicts: No indexed conflict

Open side-by-side comparison
How duplicate leads are calculated

Dates are eligibility gates, not merely deductions: chronologically impossible people are excluded. Dates, places, spouses, parent certainty and children's profiles and names are then compared. A high score is a prompt to inspect records, not a merge recommendation.

Open only what you need

Research & records

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1670

Profile-stated birthplace: Kilwinning, Ayrshire, Scotland

Kilwinning — Ayrshire

One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links.

One-Tree profile leadunknown
Source and mapping detail

WikiTree profile export for Glasgow-3105

No sufficiently specific citation match found.

Precision: Settlement/parish centrepoint

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.3 claims
1Derivative
1Tree Only

Documented or strongly supported

No claims in this category have been formally assessed.

Working hypotheses and conflicts

No claims in this category have been formally assessed.

Research questionsOpen problems, missing bridges and the next records to inspect.0 open

No formal open question is recorded for this person.

Sources and provenanceStructured citations and source-quality classifications.2 sources

Source or provenance: quality describes the record layer, not every conclusion drawn from it.

  1. derivative "Scotland Births and Baptisms, 1564-1950", database, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XTVB-3YQ : 16 September 2021), James Glasgow in entry for James Glasgow, 1689.
  2. tree_only WikiTree profile export for Glasgow-3105
Technical profile and raw captureDataset metadata, machine dossier and captured WikiTree biography.Advanced

WikiTree profile information

Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20

Machine-readable dossier

WikiTree biography, citations and relationship snapshot

Glasgow-3105 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2024-09-21.

Profile location claims

EventDateLocationStatus
birth—Kilwinning, Ayrshire, ScotlandWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenJames GlasgowGlasgow-31041689-07-14 · Kilwinning, Ayrshire, Scotland · 0000-00-00
SpousesMargaret GlasgowPark-80501670-00-00 · 0000-00-00

Record-bearing passages

Profile source citations

  1. "Scotland Births and Baptisms, 1564-1950", database, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XTVB-3YQ : 16 September 2021), James Glasgow in entry for James Glasgow, 1689. source link 1
Full captured biography text
Biography
James was born in 1670. 
Sources
* "Scotland Births and Baptisms, 1564-1950", database, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XTVB-3YQ : 16 September 2021), James Glasgow in entry for James Glasgow, 1689.
Raw WikiTree biography markup
== Biography ==

James was born in 1670. 
== Sources ==
<references />
* "Scotland Births and Baptisms, 1564-1950", database, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:XTVB-3YQ : 16 September 2021), James Glasgow in entry for James Glasgow, 1689.