Tyrrell County, North CarolinaEdit This Page

From FamilySearch Wiki

Revision as of 22:03, 28 March 2012 by Jaburgess (Talk | contribs)


Tyrrell County, North Carolina
Map
Map of North Carolina highlighting Tyrrell County
Location in the state of North Carolina
Map of the U.S. highlighting North Carolina
Location of North Carolina in the U.S.
Facts
Founded 1729
County Seat Columbia
Courthouse
Adopt-a-wiki page
Logonew small.gif This page adopted by:
NCGenWeb Project
who welcome you to contribute.
County Coordinator
Tyrrell Co. NCGenWeb
Adopt a page today

United States  Gotoarrow.png  North Carolina  Gotoarrow.png  Tyrrell County

Contents

County Courthouse

Tyrrell County North Carolina
403 Main Street PO box 417
Columbia NC 27925

Reg of Deeds has b & d rec from 1913
m rec from 1862 & land rec
Clk Cup Ct has div rec, pro rec from 1730
& ct rec from 1900
Tyrrell was created from Chowan, Currituck, Pasquotank 27 Nov 1729

History

County seat history - Courthouse on Kendricks Cree (1751); Home of Bejamin Spruill (1774-1776); Courthouse on Scuppernog River (1777-1799); and present Columbia.

Parent County

1729--Tyrrell County was created from Bertie, Chowan, Currituck, and Pasquotank Counties.
County seat: Columbia [1]

Boundary Changes

Record Loss

Some of the early records are missing.

Places/Localities

Populated Places

Neighboring Counties

Resources

Cemeteries

Church

Court

Land

Local Histories

Maps

Military

Civil War

Civil War Confederate units - Brief history, counties where recruited, etc.

Newspapers

Probate

Taxation

Vital Records

Societies and Libraries 

Family History Centers

Web Sites

  • USGenWeb project. May have maps, name indexes, history or other information for this county. Select the state, then the county.
  • Family History Library Catalog

References

  1. The Handybook for Genealogists: United States of America,10th ed. (Draper, UT:Everton Publishers, 2002).

 

Need additional research help? Contact our research help specialists.

Need wiki, indexing, or website help? Contact our product teams.


Did you find this article helpful?

You're invited to explain your rating on the discussion page (you must be signed in).