Navigation Systems

Jump Planner

Awaiting Navigation Data

Initialize route parameters to visualize

EVE Online Jump Planner

Plan capital routes mixing jump drives and stargates: isotopes per jump, range by Jump Drive Calibration, forced waypoints and a tactical map.

The jump planner on Capsuleers.app builds the fastest capital route between two EVE Online systems by combining jump drives and stargates. Pick origin, optional intermediate waypoints, destination, ship class and maximum range: the tool computes the optimal path and shows it jump by jump.

The algorithm is a Dijkstra/BFS variant working on the union of the stargate graph (extracted from the SDE) and the jump-drive graph (computed dynamically over the jumpable-system set). For each segment the planner indicates whether it's a gate jump or a jump-drive jump, the system traversed, the region, the distance in light years and the security status, surfacing alternatives when similar paths exist. The route renders on a map with a 2D/3D toggle.

It's useful for alliance deployments, dread-bombing a contested keepstar, hauling Jump Freighters across multi-jump chains or evacuating structures under timer. Unlike a stargate-only route planner, it threads multiple jump-drive hops and gates into one path. Works without login.

How the jump planner builds a route

Enter an origin and a destination, pick the hull class and set your Jump Drive Calibration, and the planner returns the shortest path it can find between them. What makes the answer different from a plain jump calculator is that the graph it searches contains both kinds of edge: every jump your drive can make at your current range, and every stargate.

The result is a leg-by-leg sequence. Each leg says whether it is a jump-drive jump or a stargate transit, how far it is in light years, and how many isotopes that specific jump burns. The totals underneath give the jump distance, the split between jumps and gates, and the fuel one way and for the round trip.

Stargate transits burn no fuel, so only jump-drive legs count towards the isotope totals. That sounds obvious and is exactly why mixed routes are worth planning: a single gate hop in the middle can cut a leg short enough to save thousands of isotopes.

Isotopes per light year, by hull class

The base consumption below is the hull's own value before any skill. Jump Fuel Conservation reduces it by ten percent per level, and the four jump freighters get a further ten percent per level of the Jump Freighters skill on top of that. Both multiply cleanly, with no stacking penalty.

The rounding happens per jump, not on the total, which is why a route split into more short legs can cost slightly more than the same distance in fewer long ones.

Dreadnought, Carrier, Force Auxiliary: 3,000 isotopes per light year, 3.5 LY base range
Supercarrier: 3,000 per light year, 3.5 LY base range
Titan: 3,000 per light year, 3.0 LY base range
Rhea: 10,000 per light year, 5.0 LY base range
Anshar: 9,400 per light year, 5.0 LY base range
Ark: 8,800 per light year, 5.0 LY base range
Nomad: 8,200 per light year, 5.0 LY base range
Rorqual: 4,000 per light year, 5.0 LY base range
Black Ops: 700 per light year, 4.0 LY base range

Range and Jump Drive Calibration

Your maximum jump range is the hull's base range multiplied by one plus twenty percent per level of Jump Drive Calibration. At level five that is double the base: a dreadnought goes from 3.5 to 7.0 light years, a jump freighter from 5.0 to 10.0, a Titan from 3.0 to 6.0.

This is the single setting that changes a route the most. Dropping from Jump Drive Calibration V to IV takes a dreadnought from 7.0 to 6.3 light years, and on a long move that is often the difference between four jumps and five. The planner recalculates the whole path the moment you change it, so it is worth stepping the level up and down to see which legs actually depend on that last skill level.

Forced waypoints and alternatives

Intermediate nodes let you force the route through systems you have chosen, in order. Use them to route through a staging system, to keep a leg inside friendly space, or to avoid a chokepoint the shortest path would otherwise take.

For any system on the route you can open its alternatives: the local stargate connections, and every other system within jump range of the previous leg. That turns the planner from a single answer into something you can argue with, which is what route planning under a hostile hotdrop threat actually is. You can also disconnect a stargate leg to force the planner to solve that stretch with the jump drive instead.

Reading the tactical map

The route is drawn on a map that can be switched between a rotatable three-dimensional camera and a flat top-down view, and expanded to fill the screen. Systems on the route are full nodes, systems near it are context dots that gain their names as you zoom in.

The marks follow the in-game map: the alliance holding sovereignty is shown as its logo inside the node, the security value sits next to the system name in its own colour, and a diamond outlines the origin. Forced waypoints, jump-drive jumps, stargate transits and off-route systems each have their own colour, listed in the legend on the map.

Frequently asked questions

Does the jump planner calculate jump fatigue?

No, and that is deliberate. Fatigue is a property of your character at this moment rather than of the route: it depends on the timer you are already carrying when you undock, so the same route costs a pilot who has not jumped all week nothing and a pilot mid-move a great deal. What the planner gives you is the input fatigue is calculated from, which is the light-year distance of every leg, leg by leg. Your current fatigue and cooldown are shown in the game client.

Why does a route with more stargates sometimes cost less fuel?

Because stargate transits burn nothing. The planner searches a graph containing both kinds of edge, so it will happily take a gate hop that shortens the following jump. On a jump freighter at ten thousand isotopes per light year, cutting one light year off a leg saves more than most people expect.

Can I plan a route for a hull that is not in the list?

The list covers every hull class that has its own jump characteristics rather than every hull by name, so a Revelation and a Moros are both the dreadnought entry because their jump drive behaves identically. The four jump freighters are listed separately because their base isotope consumption genuinely differs.

Does it avoid any systems automatically?

It skips the regions CCP keeps out of normal play, so a route will never be built through them. Everything else is reachable, and if you want to avoid a specific system you can steer around it with forced waypoints.