Statistics for occurrence #1 of “Hartford” in chapter 25, page 589 of Lucius R. Paige, History of Cambridge, Massachusetts, 1630-1877, with a genealogical register:
...
Hooker, Thomas, Rev., arrived in New England 3 Sept. 1633, and settled at Camb.
He rein.
to Hartford July 1636, and d. there 7 July 1647, a. 61.
In his will, dated 7 July 1647, he named his w. Susanna, sons John and Samuel, and dau.,Joanna, deceased (w. of Rev. Thomas Shepard); Mary, deceased (w. ...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
| † |
Hartford (Connecticut, United States) |
1,994 |
427 |
200 |
5 |
0 user votes |
|
Hartford (United Kingdom) |
31 |
28 |
3 |
2 |
0 user votes |
|
Hartford (Maine, United States) |
2 |
0 |
2 |
0 |
0 user votes |
|
Hartford (Alabama, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Arkansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Georgia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Illinois, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Illinois, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Kansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Liberia) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Michigan, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (New Jersey, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (New Mexico, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (New York, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (South Dakota, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Tennessee, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Hartford (Wisconsin, United States) |
0 |
0 |
0 |
0 |
0 user votes |
† This entity has been selected by the automated classifier as the most likely match in this context. It may or may not be the correct match.