Archival family tree · South African Tamil roots

Ammanee

Yathavoor, Salem

Father
Velu Niaken
Yathavoor, Salem
Indentured ancestor
Ammanee
male · Yathavoor, Salem
The crossing
Origin
Yathavoor
Salem
Ship
LAUREL
no. 32696
Year
1884
Arrived
Natal, South Africa
The origin village

Ammanee’s family came from Yathavoor, Salem district. Living relatives may still be there — a voter-roll lookup can name them, and the modern village page shows land records and families we already track.

Others from Yathavoor

5 other indentured arrivals from the same village indexed in this archive. They may be siblings, cousins, or unrelated neighbours who left around the same time — the village link alone doesn’t prove a shared line, but it’s the strongest starting point for widening the search.

About this record

Ammanee appears in the Natal indenture register as an arrival from the Madras Presidency. Between 1860 and 1911, roughly 152,000 indentured labourers were shipped from Madras to Natal under a five-year contract to work on the sugar, tea, coffee and wattle estates of what is today KwaZulu-Natal. Each arrival was recorded at the Durban depot with a name, father’s name, age, native district (zillah), often a specific village, the ship they came on, the arrival date, and the estate they were assigned to. The Gandhi-Luthuli Documentation Centre at the University of KwaZulu-Natal (GLDC) holds the master copies of these registers today; the National Archives and Records Service of South Africa (NARSSA) maintains parallel estate-employment records that name spouses and children not always captured on the arrival register. TamizhConnect indexes both, cross-referenced by immigration number.

This arrival falls in the middle expansion phase, when Natal sugar acreage had roughly doubled since 1865 and Madras depots were shipping between three and five thousand labourers per year. Estate wages had by this stage been standardised at ten shillings per month for adult men, with the return passage guaranteed after ten years of continuous service — a clause many labourers in this cohort exercised and many others did not, choosing instead to accept a Crown grant of land and stay on as free settlers.

Salem district was a mid-tier sending zone, most recruitment focused on the plains around the modern Salem and Namakkal areas. The district's mixed Tamil-Kannada linguistic border meant that some register entries carry name spellings that make more sense phonetically in Kannada than in Tamil — a clue when reconciling the paper spelling against family memory.

The LAUREL crossing, 1884

The LAUREL sailed to Natal in 1884. A typical crossing from Madras to Durban took ten to twelve weeks under sail and steam. Ships boarded at the Madras roads offshore of Chennai, called at Karaikal or Nagapattinam to complete the Madras-side manifest, then ran a great-circle course across the Indian Ocean towards Port Natal. Conditions below decks were tight — most vessels carried 400 to 700 labourers per voyage in bunks stacked three deep — and colonial regulations required a ship’s surgeon, cooked rice rations twice a day, and separate quarters for women and children. Departure spellings of names were often Anglicised phonetically by the Madras depot clerk; arrival spellings were sometimes corrected, sometimes compounded further by the Durban clerk. Either way the spelling on the paper record is rarely how the family spells the name today.

Reading the record like a historian

Colonial spelling drift is the single hardest thing about using indenture records. Because the ancestor on this page is recorded as Ammanee, Common Tamil name shifts include vowel doubling (“oo” for “u”), terminal consonants losing their trailing vowel (“Padayat” for “Padayachi”), and French-transliterated names from Karaikal or Pondicherry appearing with “ou” where English would use “u”. Alongside those name-specific shifts, the general rules apply: vowel doubling (“oo” for “u”) was common; terminal consonants often lost their trailing vowel (“Padayat” for “Padayachi”); French-transliterated names from Karaikal (Karikal) or Pondicherry appear with “ou” where English would use “u”; and names starting with an aspirated consonant (Th, Ch, Dh) were often written without the h. When you compare this record against family memory, treat the paper spelling as one candidate variant and check against three or four phonetic alternatives before dismissing a match.

Reaching the Tamil Nadu side

The origin village on this record (Yathavoor, Salem district) is the anchor point for finding the extended family that stayed behind. The Tamil Nadu Election Commission publishes annual voter rolls at village-level detail; if a family with the same surname still lives at Yathavoor, they may well descend from the siblings and cousins Ammanee left behind in the 1860s to 1900s. Search the voter roll for the village and any surname pattern you can guess; a match is not proof of a shared line by itself, but it usually surfaces a living contact who knows the family history the archive can’t reach. For the mechanics of that reverse- lookup, the guide Find Tamil ancestors by village name walks the exact search sequence.

Next steps if this is your ancestor

If this record matches what your family already knew, the practical next step is to save it as an anchor point in a documented family tree and start pulling the related records that radiate from it — the ship manifest for other same-village passengers, the estate register for co-workers who arrived together, and the Tamil Nadu voter roll for the origin village. If the match is only partial (right name, wrong village, or right village, wrong ship year), it’s worth treating this as a lead rather than a confirmation and looking for a second and third source before incorporating it. The three-source rule from the records-search guide is the standard bar, and the three sources have to be genuinely independent: an indenture register, an oral history from an elder who did not learn it from the same paper, and a third source of a DIFFERENT type — a temple archanai or marriage record, a land/patta title, a school admission register, or a colonial-era postcard, letter, or photograph. Two land documents (a patta plus another land record) are the same type of evidence and don’t count as separate corroboration.

Ammanee's record carries no other named kin in the NARSSA estate index, which is more common than descendants expect — the estate clerks recorded a spouse or child only when a specific event (marriage, birth, death, insurance claim) triggered the entry. The absence of kin here doesn't mean the ancestor was alone; it means the estate paperwork never had a reason to record the family. Ship-manifest co-passengers and same-village emigrants (both listed on this page) are the strongest alternative anchors when kin is thin.

Verify with your elders

Colonial ship-clerks often mangled Tamil names. Before treating this as your ancestor, ask the oldest person in your family:

  • Was there a great-great-grandfather named Ammanee or Velu Niaken?
  • Did family ever mention coming from Yathavoor, Salem?
  • Do the dates line up with when your family arrived in Natal? (Record: 1884)
  • Any family memory of a ship named LAUREL, or a passage to Natal around then?
Ask elders on WhatsApp
Is this your ancestor?

Claim this record to start your family tree — Ammanee and Velu Niaken are added instantly, ready for you to extend with living relatives.

This is my family — build my tree

Two paths: build your tree if this is your ancestor, or submit evidence to help a South African family verify their village link. See the Village Verification Project.

More families from Yathavoor

Source: theiii.in Natal indenture register (digitised ship record). Names and places are the colonial spellings as recorded; verify against family memory before treating a lineage as certain.

Privacy — no living person’s details are ever shown in public

Ammanee appears here only because this is a historical indenture record (1860–1911) — the person named sailed over a century ago. Family trees, voter matches and any living-relative data sit behind a login and are visible only to the account owner they belong to.