Adriaan Oosthuizen
25 December 1774 – before 1804-08-16 · Oosthuizen line
Names
- Baptismal name
- Adriaan
- Given
- Adriaan
- 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
- 1769Jacobus Oosthuizen (b.1769)
- 1771Dina Johanna Magdalena Oosthuizen
- 1777Jacoba Cornelia Oosthuizen
A life in the record
- before 1804-08-16 died Died
- 25 December 1774 born Born
Stories
What we don't know
- No dated record ties this person to a specific piece of ground.
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-000666 into this row. PROVEN DUPLICATE, resolved on the FamilySearch id. Both rows carry LVZR-BDT; 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 1774 -> 1774-12-25.
[23 Sep 2026, SRC-467] DEAD BY 16 AUGUST 1804, not 1805: MOOC8/55.42 is the Weeskamer's inventory and taxation of his estate on that date, given in by his widow CATHARINA PETRONELLA HORN, with five minor children - Adriaan 8, Jacobus 6, Cornelia Carolina 5, Johannes Willem 2, Catharina Petronella Hermina 10 months - and no farm; 11 trek oxen, 124 goats, 43 sheep, estate Rd:s 448. Appraised by Willem van Zijl and Abraham le Roux. The place is not named on the sheet.
[2026-09-23] The sheet is transcribed in full with a reading in both languages, DOC-0367, INV-0032.
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.
What the record is missing
-
An estate taken on ground we cannot place
second order · B6 loose-doc
DOC-0367 (MOOC8/55.42, 1804-08-16) lists a household's whole movable estate, which means officials went to where that household lived. It says “not named on the sheet” and no more. No parcel is attached, so the family it describes sits nowhere on the map.
What would settle it The inventory's own heading usually names the farm and the field-cornetcy; where it does not, the deceased's quitrent or opgaaf entry for that year will. This is the shape that produced the de Bruin/Rondabel find.
Found by breaks.py reading the model against itself, not written by hand,
each one is a shape of missing record, not a fault in the data.
The whole set is on the
questions page.
Elders
FamilySearch profile LVZR-BDT