Statistics for occurrence #1 of “Huger” in chapter 37 of An English Combatant, Lieutenant of Artillery of the Field Staff., Battlefields of the South from Bull Run to Fredericksburgh; with sketches of Confederate commanders, and gossip of the camps.:

...ly contested, and was marked by prostrate bodies of friend and foe. When the engagement commenced it was not expected that Hill would be left to maintain the contest alone. It was thought that Huger would have fallen upon the enemy's rear; but, as usual, that commander was behind time, and Hill, as a consequence, was almost annihilated. It was said that Huger would have arrived in time to ass...
Max. Freq. Min. Freq.
Entity Corpus Doc Corpus Doc  
Benjamin Huger 651 65 33 1 0 user votes
Huger 624 0 224 0 0 user votes
Frank Huger 364 0 18 0 0 user votes
Thomas B. Huger 172 0 12 0 0 user votes
T. B. Huger 108 0 6 0 0 user votes
Alfred Huger 65 0 3 0 0 user votes
A. A. G. Huger 50 0 0 0 0 user votes
B. Huger 37 0 5 0 0 user votes
Isaac Huger 30 0 4 0 0 user votes
Daniel E. Huger 18 0 4 0 0 user votes
D. E. Huger 10 0 2 0 0 user votes
F. Huger 10 0 2 0 0 user votes
A. Huger 7 0 1 0 0 user votes
Thomas Huger 7 0 3 0 0 user votes
Arthur M. Huger 6 0 2 0 0 user votes
C. K. Huger 6 0 6 0 0 user votes
William Elliott Huger 6 0 2 0 0 user votes
Benj Huger 5 0 1 0 0 user votes
Daniel Huger 5 0 1 0 0 user votes
Charles C. Huger 4 0 0 0 0 user votes
A. M. Huger 2 0 0 0 0 user votes
Edward Huger 2 0 0 0 0 user votes
F. K. Huger 2 0 0 0 0 user votes
Francis Kinlock Huger 2 0 0 0 0 user votes
J. M. Huger 2 0 0 0 0 user votes
J. P. Huger 2 0 0 0 0 user votes
John M. Huger 2 0 2 0 0 user votes
Joseph M. Huger 2 0 0 0 0 user votes
Mariamne Huger 2 0 0 0 0 user votes
William E. Huger 2 0 0 0 0 user votes
William Harleston Huger 2 0 0 0 0 user votes
Arthur Huger 1 0 1 0 0 user votes
C. L. Huger 1 0 1 0 0 user votes
D. R. Huger 1 0 1 0 0 user votes
J. Huger 1 0 1 0 0 user votes
Joseph P. Huger 1 0 1 0 0 user votes
Thos B. Huger 1 0 1 0 0 user votes
W. E. Huger 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.