FANDOM


"Mundungus Fletcher is a wizard. A short, squat man, he has long straggly ginger hair and bloodshot, baggy eyes, which give him the look of a basset hound."

From the Story

Harry Potter and the Goblet of Fire

Discovered in Book 4, Chapter 10, Dress Robes

"In the wake of the events at the Quidditch World Cup, many people have sent Howlers to the Ministry demanding compensation for their ruined property. Mundungus puts in a claim for a twelve-bedroomed tent with en-suite jacuzzi, but Percy says he knows for a fact Mundungus slept under a cloak propped on sticks."

Discovered in chapter 36, The Parting of the Ways

Sirius Black is sent by Professor Dumbledore to alert Mundungus Fletcher, one of the 'old crowd', about the events at the Triwizard Tournament.

Harry Potter and the Order of the Phoenix

Mundungus Fletcher is, albeit reluctantly, a member of the Order of the Phoenix. He frequents 12 Grimmauld Place more for the chance to steal many of the Black family's treasured possessions than out of any loyalty to the cause. Subsequent to Dumbledore's death and the Order's headquarters being moved to the Burrow, Mundungus returns and starts selling everything he can lay his hands on.

Discovered in chapter 6, The Noble and Most Ancient House of Black

Mundungus Fletcher arrives at number twelve, Grimmauld Place carrying a stack of precariously balanced cauldrons. He is shouted at by Mrs Weasley for bringing the stolen cauldrons into the house. He redeems himself slightly a few days later, by rescuing Ron from an ancient set of purple robes that attempt to strangle the boy when removed from their wardrobe.

Harry Potter and the Deathly Hallows

Discovered in chapter 4, The Seven Potters

Mundungus is paired with Moody for the journey from Privet Drive, as he is felt to be untrustworthy.

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.