Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

The Simpsons fan theory could prove where Springfield is in real life

We know for sure it is next to Shelbyville, right?

Jack Shepherd
Sunday 21 February 2016 18:02 GMT
Comments

Support truly
independent journalism

Our mission is to deliver unbiased, fact-based reporting that holds power to account and exposes the truth.

Whether $5 or $50, every contribution counts.

Support us to deliver journalism without an agenda.

Louise Thomas

Louise Thomas

Editor

While The Simpsons may have been going for well over 25 years now, there’s still one question no-one really knows the answer to: where is Springfield?

Fans of the series have been asking that same question since the first season, yet little is known except Shelbyville is next door, and there are a lot of Shelbyville’s in the US.

Well, luckily those guys over at Film Theorists think they have the answer, giving a long-winded explanation as to where Springfield really is.

So where is it? Using evidence from various episodes, the detectives narrow their search down to either Washington or Oregon. But which one, I hear you say.

Well, in the episode ‘Much Apu About Nothing’, a classic episode in which a Bear Tax is introduced, outraging Homer, there’s a little clue as to which of the two states Springfield is in.

At one point, Homer gets charged state tax, which is not applicable in 9 states, including Washington State, meaning The Simpsons’ home state – according to these theorists - is Oregon.

The icing on the cake isn’t any of the geographical evidence though, it is the fact show creator Matt Groening grew up in Oregon and based Homer on his own father, as explained at the end of the video. Lovely.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in