4

At the end of Solo: A Star Wars Story when Han and Chewie are talking about the Kessel Run, Han says:

not if you round down.

What is he rounding down from? I guess it's not 12.5-12.9 as it seems Han is being a bit liberal with his counting.

3 Answers 3

7

Probably about 12.5 parsecs.

In the Solo film's official novelisation, L3 notes that the run was completed in "a little over twelve parsecs". At this point in the film she's become integrated into the Falcon's primary memory core so we can assume her opinion is solid.

And then the Millennium Falcon had made the Kessel Run in a little over twelve parsecs.

Not bad.


In the Solo film's junior novel we actually have Chewie's dialogue translated for us. He feels that it was closer to "thirteen" parsecs.

“See that ship?” he said. “She just made the Kessel Run in twelve parsecs.”

The worker paused momentarily, stone-faced and clearly skeptical, and Chewie growled: “Actually, it was more like thirteen.”

“Not if you round down,” Han said, and walked over to Lando, who was looking up at his baby with visible anguish. The ship looked nothing like it had when they’d left Vandor. Running the gauntlet had ripped off all her precious added adornment, leaving a stripped-down, mean-looking freighter covered in dents and scrapes.


This inconsistency may be due to Chewie rounding up rather than down which suggests that it was probably close to the halfway mark between twelve and thirteen. There may also be some inconsistency about what represents the start and finish of the 'run' given that the ship looped around a black hole.

1
  • 1
    you must have the library of Alexandria!! Mar 6, 2019 at 17:22
2

In the movie, it's not specified just how many parsecs they traveled in the run, so the line simply indicates that, while he did decrease the distance traveled (according to Star Wars: The Essential Atlas, the Kessel Run was an 18-parsec trip), it was not actually as low as twelve, although he's stating it as such. Presumably, it's not high enough to reach another whole number.

Notably, by the time of Episode IV, he's claiming that he "made the Kessel Run in less than twelve parsecs", indicating that his exaggeration has grown.

4
  • 2
    And now I wait for Valorum to step in with a quote from the novelization...
    – FuzzyBoots
    Mar 5, 2019 at 23:35
  • 2
    I've not checked (I'm mobile at the mo and don't have access to my library) but I would be dumbfounded if they put an actual number in the Solo novelisation. The whole point is that it's a language gag.
    – Valorum
    Mar 6, 2019 at 9:43
  • It'll just say something like "Chewie barked a correction"
    – Valorum
    Mar 6, 2019 at 9:44
  • Holy crap. The junior novel actually gives us a figure.
    – Valorum
    Mar 6, 2019 at 14:23
-1

According to Wookieepedia, he made the Kessel run in about 11.5 parsecs

A parsec is a unit of distance, not time. Solo was not referring directly to his ship's speed when he made this claim. Instead, he was referring to the shorter route he was able to travel by skirting the nearby Maw black hole cluster, thus making the run in under the standard distance. By moving closer to the black holes, Solo managed to cut the distance down to about 11.5 parsecs.

This says he made the Kessel run in about 11.5 parsecs, which probably means he did it in 12.1 parsecs to 12.4 parsecs. This is the closest reference about how long it took him, so we can assume that he did the Kessel Run in about 12.3, or so parsecs.

3
  • 3
    I like your appeal to sources, but how are you getting form 11.5 to 12.1 to 12.4?
    – FuzzyBoots
    Mar 6, 2019 at 0:43
  • He says if you round down...12.1 is the closest of the possible to 11.5
    – Ginge
    Mar 6, 2019 at 3:14
  • 2
    @Ginge in the film Han says that he rounded down, rounding down down from 11.5 would be 11? Give the fact that rounding down was even mentioned and Han is a 'scoundrel' shouldn't we assume he isn't using a normal counting system and the actual number of parsecs is higher than it should be? Mar 6, 2019 at 4:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.