Fandom

The Three Kingdoms Wiki

Guan Hai 管亥

1,017pages on
this wiki
Add New Page
Comments0 Share

Guan Hai 管亥 was a bandit who was active in the Shandong 山東 area. He fought in name of the Yellow Turban rebels, but he is not mentioned as active during the 184 Yellow Turban Rebellion. Chronologically he first appears in 193.

BiographyEdit

Guan Hai was a Yellow Turban leader who was active in the Shandong area. In 193 he besieged Kong Rong 孔融, who was sent out to Duchang 都昌 to quell some remnant Yellow Turban forces. In response, Guan Hai led his army to surround Duchang and laid siege to it. In response, Kong Rong sent Taishi Ci 太史慈 to seek help from Liu Bei 劉備, who agreed to lend Taishi Ci three thousand soldiers to relief the siege. When the reinforcements arrived, Guan Hai's men scattered.

NotesEdit

  • There are no records of activity Guan Hai in 184. In fact, the Yellow Turban Rebellion is covered primarily in the biography of Huangfu Song and Zhu Jun in History of the Later Han, chapter 71, but his name is not mentioned there, nor in the biographies of other men active in 184 such as He Jin, Lu Zhi, or Emperor Ling. It therefore seems assumable that Guan Hai was not active in 184.
  • The biography of Kong Rong in History of the Later Han and the biography of Taishi Ci in Records of the Three Kingdoms call Guan Hai a Yellow Turban.[1][2] Because he is not mentioned in any text covering 184 it's more likely he was a bandit who claimed affiliation with the Yellow Turbans, rather than him being a survivor of the 184 rebellion.

Fact vs. FictionEdit

  • Historically, Guan Hai wasn't slain by Guan Yu. He and his men just scattered when reinforcements came.

ReferencesEdit

  1. "時,黃巾複來侵暴,融乃出屯都昌,為賊管亥所圍。" Fan Ye. History of the Later Han, 70.
  2. "時融以黃巾寇暴,出屯都昌,為賊管亥所圍。" Chen Shou. "Book of Wu 4," Records of the Three Kingdoms.

SourcesEdit

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.