Christian Diederich MEYRAN
Characteristics
Type | Value | Date | Place | Sources |
---|---|---|---|---|
name | Christian Diederich MEYRAN |
|
Events
Type | Date | Place | Sources |
---|---|---|---|
death | 7. October 1864 | Bramsche Haus No 10, Bramsche Ksp, Voerden Amt, Hannover Fst Osnabrueck
Find persons in this place |
|
birth | 22. July 1822 | Bramsche Haus No 10, Bramsche Ksp, Voerden Amt, Hannover Fst Osnabrueck
Find persons in this place |
|
marriage | 28. March 1844 | Bramsche Ksp, Osnabrueck, Hannover
Find persons in this place |
|
marriage | 22. May 1856 | Bramsche, Bramsche Ksp, Voerden Amt, Hannover Fst Osnabrueck
Find persons in this place |
|
marriage | 28. May 1857 | Bramsche Ksp, Osnabrueck, Hannover
Find persons in this place |
??spouses-and-children_en_US??
Marriage | ??spouse_en_US?? | Children |
---|---|---|
28. March 1844
Bramsche Ksp, Osnabrueck, Hannover |
Anna Marie Wilhelmine BROCKMANN | |
22. May 1856
Bramsche, Bramsche Ksp, Voerden Amt, Hannover Fst Osnabrueck |
Anna Louise Regine BROCKMANN |
|
28. May 1857
Bramsche Ksp, Osnabrueck, Hannover |
Charlotte Amalie Catharine BRANDT |
Unique identifier(s)
GEDCOM provides the ability to assign a globally unique identifier to individuals. This allows you to find and link them across family trees. This is also the safest way to create a permanent link that will survive any updates to the file.
Identical Persons
GEDBAS contains copies of this person (probably submitted by other researchers). This list is based on the UID feature of GEDCOM.
Name | Details | files | Title | ??submitter_en_US?? | Upload date |
---|---|---|---|---|---|
Christian Diederich MEYRAN | * 1822 Bramsche Haus No 10, Bramsche Ksp, Voerden Amt, Hannover Fst Osnabrueck + 1864 Bramsche Haus No 10, Bramsche Ksp, Voerden Amt, Hannover Fst Osnabrueck | 54637 | BrockmannFamilien | Ingo Brockmann | 2024-12-29 |
files
Title | Brockmann |
Description | Brockmann Familien |
Id | 67273 |
Upload date | 2025-06-01 22:21:43.0 |
Submitter |
![]() |
ingobrockmann@yahoo.de | |
??show-persons-in-database_en_US?? |