Stats for the NGS Conference in Charleston, South Carolina

I just received the following information from Erin Wood at NGS:

The National Genealogical Society is pleased to announce attendance of 2,270 at the NGS 2011 Family History Conference held in Charleston, South Carolina, 11-14 May.

Over 1,500 people purchased a full conference registration and over one hundred people purchased a daily registration. In addition, conference attendance included speakers, vendors and their booth staff, and many volunteers provided by the South Carolina Genealogical Society and its local chapters.

On Saturday, Ancestry.com sponsored an Ancestry Day program which brought an additional 575 people to the convention center. Over 2,000 meals were served at the local convention center and social events sponsored by the South Carolina Genealogical Society, providing genealogists many opportunities to share stories about their research and their ancestors.

The NGS 2012 Family History Conference will be 9-12 May 2012 at the Duke Energy Convention Center in Cincinnati, Ohio. The conference hotel is the Hyatt Regency Cincinnati, 151 W. Fifth St., Cincinnati, OH 45202. Conference registration will open 1 December 2011.

Author: Leland Meitzler

Leland K. Meitzler founded Heritage Quest in 1985, and has worked as Managing Editor of both Heritage Quest Magazine and The Genealogical Helper. He currently operates Family Roots Publishing Company (www.FamilyRootsPublishing.com), writes daily at GenealogyBlog.com, writes the weekly Genealogy Newsline, conducts the annual Salt Lake Christmas Tour to the Family History Library, and speaks nationally, having given over 2000 lectures since 1983.

3 thoughts on “Stats for the NGS Conference in Charleston, South Carolina”

  1. Ron,

    My dad was Gunther E. Pohl of the NYPL. I’m trying to get in touch with you regarding his NY Genealogical and Biographical index.

    Thanks, Ron

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.