Tietjerksteradeel speciekohieren inschrijving in 1760 in Suameer (Netherlands)

Occupant

  • Symen Gosses, Post 1
    - In 1760 hoofdbewoner, ingekomen van Suameer 12, Tietjerksteradeel
    - In 1761 overleden, de weduwe naar nr. 32
    - Opm.: huis, waaronder meer dan 30 pondematen land, op een koud steed gebouwd 1760
  • Wybe Gerbens, Post 2
    - In 1761 hoofdbewoner, ingekomen van Garijp 35, Tietjerksteradeel
    - In 1764 naar Garijp 77, Tietjerksteradeel
  • Jarich Gerbens, Post 3
    - In 1761 inwonend, ingekomen van Garijp 35, Tietjerksteradeel
    - In 1764 naar Garijp 98, Tietjerksteradeel
  • Jurjen Meinerts, Post 4
    - In 1764 hoofdbewoner, begint
    - In 1779 naar Bergum 4, Tietjerksteradeel
    - Opm.: 1765: huis afgebrand 1764
  • Bouwe Nannes, Post 5
    - In 1779 hoofdbewoner, ingekomen van Suameer 11, Tietjerksteradeel
    - In 1794 naar Suameer 15, Tietjerksteradeel

Remark

Locatie: 81
Gemeente: 1140


Source citation

AlleFriezen in Leeuwarden (Netherlands), Tietjerksteradeel speciekohieren
Speciekohieren Tietjerksteradeel - Tresoar, Part: 1, Period: 1748-1805, Tietjerksteradeel, archive 1731, inventory number 1, 1760, Lijst van bewoners per perceel


View on source website
Report an error

Internet address

  • https://allefriezen.nl/zoeken/deeds/04cec93c-ff89-4f79-b323-2b4e1e2c0ec7
  • https://www.openarchieven.nl/frl:04cec93c-ff89-4f79-b323-2b4e1e2c0ec7

To have Open Archives automatically search for additional information and related documents, you must be logged in.


Comments

Are you the first person who provides additional information?


You are not logged in yet

Login

Not a subscriber? View subscriptions!

Find your ancestors and publish your family tree on Genealogy Online via https://www.genealogieonline.nl/en/

Report an error

You are now going to report an error about the following document:

Tietjerksteradeel speciekohieren inschrijving, 1760, Suameer, Symen Gosses, Wybe Gerbens, Jarich Gerbens, Jurjen Meinerts, Bouwe Nannes, AlleFriezen (Netherlands): Tietjerksteradeel speciekohieren

Where's the error located?

On both the detail page on the website of the archive as well on Open Archives, the report will be sent to AlleFriezen.
Only on Open Archives, the report will be sent to Open Archives.

What is wrong?

Describe what information from the document is incorrect, why and what you believe is the correct information. The historical document cannot be modified, only the values as copied can be modified - if incorrect. The link to the document on Open Archives and the source website are automatically included in the message, you do not need to include these.


Thanks in advance for your report! Beware, checking and processing these reports is done by hand. It can take a while before the corrected data is visible on the websites of the archive and Open Archives.

Note: Your email address will be provided by Open Archives to AlleFriezen so that they can reach you with any questions or inform you of the handling of this error message.

Download as GEDCOM or PDF

If the information you find on Open Archives, is useful for your research, you can download it in PDF and GEDCOM format.

GEDCOM files can be imported into your family tree program. This way you do not need to type all the information in your family tree program.

To use this feature, you need to login first.

Mark document as favorite

You can add the documents you find on Open Archives that are useful for your research to your list of favorite documents. You can organize this list and when searching you will immediately see which documents are already on your list of favorite documents.

Favorite person entries can be downloaded in PDF format (ideal for printing) and GEDCOM format (ideal for reading into your family tree program).

To use this feature, you need to login first.

Add comment

Do you have additional information about the historical document? Then add it so that other researchers can benefit from it as well.

To avoid spam and invasion of privacy of living personas, comments are checked before being published.

To use this feature, you need to login first.