← The land

Farm PAR-000365

Elsenbosch (Vier-en-Twintig Riviere, Piketberg)

· on record 1794 · show on the map

Also recorded as
Elsenbosch 24 Rivieren; de Klijne Elsenbosch
District
Elsenbosch, Vier-en-Twintig Riviere (Piketberg district)

This parcel has no matched survey polygon, so it cannot be drawn on the map. That is a gap in the cadastre match, not an absence from the record.

Why this farm is here

Carel Aaron van der Merwe (1771-1850) lived on this ground. Not yet placed on the map.

Carel Aaron van der Merwe (1771-1850) is on record on this ground directly. No trace needed.

What the record holds, in order

  1. before 1794-02-01 lived here Carel Aaron van der Merwe (1771-1850) (1771–1850)
    death notice

Research notes

[30 Sep 2026, SRC-346 / SRC-707] THE BOLAND GROUND OF THIS LINE, AND THE ONE FARM ON IT THAT THE CADASTRE DOES NOT CARRY. Schalk Willem van der MerweL (PER-001635) was born here on 1 February 1794, and his 1866 death notice writes the place as 'Elsenbosch 24 Rivieren (Dist. Piketberg)'. MOOC8/50.39 of 1788 (SRC-707) has a van der Merwe household on 'de Klijne Elsenbosch geleegen over de Vier en Twintig Rivieren'. *** THE PIKETBERG CADASTRE WAS PULLED FOR THIS AND HOLDS NO ELSENBOSCH. *** 305 farms and 1717 portions fetched from the national CSG portal on 30 Sep 2026, searched on P_FARMNAME and FARM_NAME: no Elsenbosch of any spelling, and none among the neighbours of the farm that does carry the area's name. That is 5's second rule and not a reason to doubt the place - the cadastre records TITLE, not what people called the ground they lived on. WHAT THE CADASTRE DOES CARRY is VIER EN TWINTIG RIVIERE No. 240, 1379 morgen-equivalent 1379 ha at -33.1735, 18.9374, with thirteen portions, key W013C058000000000240000000. THE FARM IS NOT PINNED TO IT. The death notice reads 'Elsenbosch 24 Rivieren', which places Elsenbosch IN that country, and the inventory reads 'over de Vier en Twintig Rivieren', which places Klijne Elsenbosch BEYOND it. Neither is a statement that Elsenbosch is farm 240, and a wrong pin is worse than none. No. 240 is the anchor to search outward from, not the answer. [TO VERIFY]

The research behind this page, kept separate from it: dated working notes, open questions, and what is not yet settled.

What the record is missing

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.