EWoT: Elaiva Walfor

Aes Sedai flag ajah-gray
Elaiva Walfor
Biographical information
Nationality Andoran
Current status Alive
Physical description
Gender Female
Chronological and political information
First mentioned The Wheel of Time Companion
Affiliation White Tower
Rank Aes Sedai
Ajah Gray Ajah

Elaiva Walfor is an Aes Sedai of the Gray Ajah[1].


She has remained loyal to the White Tower during the split.

She was part of the White Tower secret expedition who were to kidnap Rand al'Thor in Cairhien.

She was taken prisoner during the Battle of Dumai's Wells by the Asha'man[2].

Elaiva was one of the captured Aes Sedai[3] to be interrogated by Verin Mathwin in order to discover the White Tower's intentions towards Rand al'Thor[4]. In reality Verin used her mild Compulsion to implant in their minds some instructions about Rand.

Later it is reported by Sorilea that all the Aes Sedai prisoners have sworn fealty to Rand[5].

As with many Aes Sedai sworn to Rand, Elaiva probably fought the Last Battle on the slopes of Thakan'dar[6]. It is not stated whether she survived or not.

Particularity of this characterEdit

Elaiva Walfor is described only in The Wheel of Time Companion, she is never mentioned in the main books of The Wheel of Time. Taking inference from the Companion, she is the second Gray mentioned in the party sent to kidnap Rand in Cairhien.

But this is in contradiction to the description of this group in the main series, because we know well the number of sisters and the Ajah involved in the kidnapping group and no more Gray sisters than one (Coiren) were ever counted in that party.


  1. The Wheel of Time Companion
  2. Lord of Chaos, Chapter 55
  3. A Crown of Swords, Chapter 1
  4. The Path of Daggers, Prologue
  5. Winter's Heart, Chapter 13
  6. A Memory of Light, Chapter 34

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.