Statistics for occurrence #1 of “Wickham” in chapter 95 of Southern Historical Society Papers, Volume 12.:
...valry Division, with General Wilson's division, to follow the enemy up the Luray valley and to push them vigorously.
Pond says, page 178:
Unfortunately Torbert did not succeed in driving Wickham 's cavalry from its strong defensive position at Millford, and hence the portion of Sheridan's plan which contemplated cutting off the enemy's retreat by seizing the pike at New Market was not carried...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | W. C. Wickham | 152 | 80 | 14 | 2 | 0 user votes | |
Wickham | 483 | 0 | 129 | 0 | 0 user votes | ||
Williams C. Wickham | 57 | 0 | 13 | 0 | 0 user votes | ||
William C. Wickham | 35 | 0 | 5 | 0 | 0 user votes | ||
C. Wickham | 34 | 0 | 0 | 0 | 0 user votes | ||
Williams Carter Wickham | 30 | 0 | 2 | 0 | 0 user votes | ||
William Fanning Wickham | 26 | 0 | 0 | 0 | 0 user votes | ||
Charles P. Wickham | 18 | 0 | 2 | 0 | 0 user votes | ||
John Wickham | 18 | 0 | 4 | 0 | 0 user votes | ||
Williams Wickham | 17 | 0 | 1 | 0 | 0 user votes | ||
W. F. Wickham | 14 | 0 | 4 | 0 | 0 user votes | ||
William Wickham | 10 | 0 | 0 | 0 | 0 user votes | ||
Wms Carter Wickham | 10 | 0 | 0 | 0 | 0 user votes | ||
J. Wickham | 8 | 0 | 0 | 0 | 0 user votes | ||
William F. Wickham | 8 | 0 | 2 | 0 | 0 user votes | ||
Joseph A. Wickham | 7 | 0 | 1 | 0 | 0 user votes | ||
William S. C. Wickham | 6 | 0 | 0 | 0 | 0 user votes | ||
Jr. Wickham | 4 | 0 | 0 | 0 | 0 user votes | ||
W. H. Wickham | 4 | 0 | 2 | 0 | 0 user votes | ||
W. S. Wickham | 4 | 0 | 0 | 0 | 0 user votes | ||
H. T. Wickham | 2 | 0 | 0 | 0 | 0 user votes | ||
Jno Wickham | 2 | 0 | 0 | 0 | 0 user votes | ||
W. L. Wickham | 2 | 0 | 0 | 0 | 0 user votes | ||
Williams Fanning Wickham | 2 | 0 | 0 | 0 | 0 user votes | ||
Wms C. Wickham | 2 | 0 | 0 | 0 | 0 user votes | ||
Joseph Wickham | 1 | 0 | 1 | 0 | 0 user votes | ||
Williams F. Wickham | 1 | 0 | 1 | 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.