Jacobus Oosthuizen (b.1769)
8 October 1769 – ? · Oosthuizen line
Names
- Baptismal name
- Jacobus
- Given
- Jacobus
- Surname
- Oosthuizen
The formal baptismal name and the name a person was actually called are both kept, and neither is derived from the other. Spelling drift between records is evidence, not noise.
Three generations around this person
Work out how this person is related to somebody else →
Click any name and the same three generations are drawn around that person instead. There is no first couple here and no top to the tree: it is only ever the family standing closest to whoever you are reading about, and a blank is a gap in the record rather than a statement about anybody.
Immediate family
- Father
- Jacobus Oosthuizen (b.1722)
- Mother
- Dina Carolina Britz
- Brothers and sisters
-
- 1751Catharina Oosthuizen
- 1753Johannes Jacobus Oosthuizen (b.1753)
- 1755Jacobus Nicolaas Oosthuizen
- 1755Ockert Jacobus Oosthuizen (b.1755)
- 1757Jacobus Petrus Oosthuizen
- 1760Gerrit Johannes Oosthuizen
- 1762Dina Johanna Oosthuizen
- 1764Marthinus Oosthuizen
- 1767Pieter Cornelis Oosthuizen
- 1771Dina Johanna Magdalena Oosthuizen
- 1774Adriaan Oosthuizen
- 1777Jacoba Cornelia Oosthuizen
A life in the record
- 8 October 1769 born Born
Stories
Others of the same name
Afrikaans naming repeats hard, and the Cape Dutch naming pattern reuses a name on purpose, a child who died young has the name given again to a later sibling. These are different people. Never match on a name alone.
What we don't know
- No death date is recorded.
- No dated record ties this person to a specific piece of ground.
- 1 other person in this model carry the same name. Never match on a name alone.
A sourced gap beats an unsourced fill. These are the open questions on this person, stated rather than papered over.
Research notes
[SRC-074] Child of Jacobus OosthuizenL (PER-000230) and Dina Carolina BritzM, Tulbagh 1749 - sibling of the root ancestor's father.
[31 Jul 2026] MERGED PER-000664 into this row. PROVEN DUPLICATE, resolved on the FamilySearch id. Both rows carry LHLG-352; an FS id names one person, so these are one person recorded twice. Created by the 31 Jul 2026 one-degree tree pull, which matched on tree id alone - and 255 model people carry no tree id, so any of them one hop from a tree-linked person was added again. Survivor is the pre-existing row; it carries the prose, sources and land links. Moved across: sex=M; tree id=. Dates sharpened from the merged row: birth_edtf 1769 -> 1769-10-08. DISAGREEMENTS, kept rather than resolved - the FamilySearch id settles these in one click: display_name: kept 'Jacobus OosthuizenL (b.1769)', PER-000664 said 'Jacobus OosthuizenL'.
*** [20 Aug 2026, SRC-093] HE IS NOT AMONG THE NINE HEIRS OF 1802, SO HE DIED BEFORE APRIL 1802 AND WITHOUT ISSUE. *** The inventory lists eight living children by name and, as the ninth heir, the children of the one who had died - which is how a Cape estate represents a predeceased child. A son who had died leaving children would therefore appear the way Marthinus does. This one appears not at all. THE DEATH DATE IS STILL UNKNOWN; what the document fixes is the LATEST it can be. Recorded as an inference from an heir list, not as a reading. [TO VERIFY]
These are working notes, not finished prose: they carry the reasoning, the corrections and the things still marked to verify. They are kept here so the page itself can read as what is known.
Open questions
-
Duplicate candidates from the one-degree pull, settled on FamilySearch ids
priority 2 · LEAD-0035
38 people added on 31 Jul 2026 share a name AND a birth YEAR with somebody already in the model, and 32 share a name with no date at all. Are they the same people?
What would settle it A full birth or baptism date on either side of a pair. Name plus YEAR is not enough here and must not be treated as enough.
Elders
FamilySearch profile LHLG-352