Researched biography · Glasgow-3165
Andrew Glasgow Esq
c. 1760 – November 1819
Peeblesshire, Scotland, United Kingdom
About Andrew
This is a weak chronological candidate for A. Glascow in a June 1794 Dutch shipping report. Chronologically adult in 1794, with a later reported Scottish death. The captured public profile cites an October 1819 Blackwood’s Magazine result but supplies no occupation or event bridge. The title ‘Esq’ is not maritime evidence. No forename expansion, maritime occupation, migration or family relationship is established for this profile.
Connected pages
Other pages on this site that name Andrew Glasgow Esq: family studies, places, source pages and other people's research.
Places 1 place
Sources 2 source pages
Research and WikiTree study pages 1 page
What the research found
Summary of the research
Initial-only newspaper lead, 5 October 2026
This summary is given in full at the top of the page.
What the records show
Source findings
Rotterdamse courant, 26 June 1794, p.2, original and separate arrival-heading/name excerpts inspected. The entry names A. Glascow from Glasgow; the departure port does not prove personal residence or birth.
Identity and family
Identity assessment — newspaper candidates withdrawn, 6 October 2026
- Rotterdamse courant, 1794-06-26, p.2: no longer a candidate for this profile. June 1794 Rotterdam arrival list: 'A. Glascow' from Glasgow. Initial only, no vessel; cannot be identified.
Still open
Questions the records have not yet answered, suggested next searches and suggested corrections.
Next questions
Check the full shipping sequence, Dutch arrival registers and Glasgow customs/master lists to identify vessel and given name. Compare signatures and family evidence before profile assignment or creation.
Family and relationships
No family members are recorded for this person in the tree.
Life and records
Explore the dated recordsChronology, roles and locations
Historical chronology
Profile-stated death place: Peeblesshire, Scotland
Record association
Records mentioning this personRecord detail
The profile snapshot records this fact, but it is not an independent historical record; the linked historical evidence is assessed separately.
Birth
Subject
Life eventsDeath
Subject
Life eventsSources
The only source so far is the WikiTree profile itselfReferences and source limitations
Profile-stated death place: Peeblesshire, Scotland
b. 1760 · Peeblesshire, Scotland · Source association
The profile snapshot records this fact, but it is not an independent historical record; the linked historical evidence is assessed separately.
Each entry is a separately identified record. Shared URLs may represent one transcription or search page containing more than one record; they are not independent confirmations.
Original notes and downloadsNotes as written, replaced interpretations, comparisons and data exports
The material the page is built from: research notes as originally written, earlier interpretations that have been replaced, automated comparisons and data downloads. The account above is the current one; nothing here overrides it.
Research notes as originally written
Current conclusion — initial-only newspaper lead, 5 October 2026
This is a weak chronological candidate for A. Glascow in a June 1794 Dutch shipping report. Chronologically adult in 1794, with a later reported Scottish death. The captured public profile cites an October 1819 Blackwood’s Magazine result but supplies no occupation or event bridge. The title ‘Esq’ is not maritime evidence. No forename expansion, maritime occupation, migration or family relationship is established for this profile.
Source findings
[Rotterdamse courant, 26 June 1794, p.2](https://www.newspapers.com/image/1335425007/), original and separate arrival-heading/name excerpts inspected. The entry names A. Glascow from Glasgow; the departure port does not prove personal residence or birth.
Next questions
Check the full shipping sequence, Dutch arrival registers and Glasgow customs/master lists to identify vessel and given name. Compare signatures and family evidence before profile assignment or creation.
Identity assessment — newspaper candidates withdrawn, 6 October 2026
- [Rotterdamse courant, 1794-06-26, p.2](https://www.newspapers.com/image/1335425007/): no longer a candidate for this profile. June 1794 Rotterdam arrival list: 'A. Glascow' from Glasgow. Initial only, no vessel; cannot be identified.
Automated parent comparison (research aid, not a recommendation)
Stored scores are preserved for audit only. They are not probabilities or genealogical evidence, and a reviewed exclusion remains excluded.
- Andrew Glasgow: 23/100 · Stored classification: weak lead
- Andrew Glasgow: 23/100 · Stored classification: weak lead
- Andrew Glasgow: 23/100 · Stored classification: weak lead
- Andrew Glasgow: 18/100 · Stored classification: weak lead
- Andrew Glasgow: 15/100 · Stored classification: weak lead
- Margaret (Martin) Glasgow: 5/100 · Stored classification: weak lead
- Mary (Crosier) Glasgow: 24/100 · Stored classification: chronology-only fallback
- Ruth (Gregory) Glasgow: 24/100 · Stored classification: chronology-only fallback
- Mary (Robertson) Glasgow: 24/100 · Stored classification: chronology-only fallback
- Mary (Cranmer) Glasgow: 24/100 · Stored classification: chronology-only fallback
Research data and downloads
Person data (JSON) · Family network
{
"id": "Glasgow-3165",
"vitals": {
"birth": {
"date": "c. 1760",
"place": null,
"status": "estimated"
},
"death": {
"date": "1819-11",
"place": "Peeblesshire, Scotland, United Kingdom",
"status": "uncertain"
}
},
"relationships": {
"parents": [],
"spouses": [],
"children": [],
"siblings": []
},
"claims": [
{
"id": "C-693a2c9d6f51",
"type": "recorded_occurrence",
"subject_ids": [
"Glasgow-3165"
],
"claim": "Andrew Glasgow Esq was recorded in Peeblesshire, Scotland (b. 1760).",
"status": "unknown",
"status_label": "One-Tree profile lead",
"evidence_ids": [
"E-693a2c9d6f51"
],
"notes": "Profile-stated death place: Peeblesshire, Scotland",
"provenance": "mapped_record"
}
],
"research_assessments": null,
"shared_relationship_assertions": null,
"relationship_history": null
}