Leafeon Icon
Contestant Profile
Series Pokemon


Tribes ██ Violet
Placement 12/18
Challenges Won 3
Votes Against 6
Days Lasted 19

Destiny Isles

Tribes ██ Salani
Placement 17/20
Challenges Won 4
Votes Against 5
Days Lasted 10

Leafeon's Statistics

Challenges Won 7
Votes Against 11
Days Lasted 29
Prize $ Earned $6,000

Leafeon is a grass-type pokemon originating from Pokemon, and a contestant on Survivor: Cuties and Survivor: Destiny Isles. She placed 12th and 17th respectively.

Survivor: CutiesEdit

Leafeon's Voting History
Episode Leafeon's
Voted Against
1 Violet Tribe Immune
2 Amiga -
3 Violet Tribe Immune
4 Tiny Amiga, Tiny
5 Violet Tribe Immune
6 Amiga -
7 Freddi Blaze, Bombette,
Etna, Freddi
Voted Out, Day 19

Survivor: Destiny IslesEdit

Leafeon's Voting History
Episode Leafeon's
Voted Against
1 Salani Tribe Immune
2 Salani Tribe Immune
3 Salani Tribe Immune
4 Cloud Ashton, Cloud,
Dexter, Hartman, N. Tropy
Eliminated, Day 10


  • Leafeon is married to Survivor: Singapore runner-up Glaceon. Together, they have a daughter, who happens to be a shiny.
  • Leafeon was considered to be a part of the cancelled Survivor: Fans vs. Second Chances season.
  • Leafeon was orginally going to be on the Survivor: Unfinished Business poll, but was removed when she turned the offer down due to being pregnant.
  • Leafeon was deemed the Most Popular Player of Survivor: Cuties. She would later move onto the Top 22.

Survivor: Cuties Contestants
Amiga · Blaze · Bombette · Cynder · Eevee · Etna · Freddi · Gabby · Kazooie ·
Konata · Lady · Leafeon · Midna · Pipsy · Sagwa · Tiny · Vixey · Zobiko
Survivor: Destiny Isles Contestants
Ashton · B.D. Joe · Barney · Bomberman · Cloud · Dexter · Hartman · Jared · Leafeon · Luigi ·
N. Tropy · Niko · Quan Chi · Rain · Rizzo · Samara · Shadow · Tails · Urcle · Vixey

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.