EVE Wormhole Calculator

Overview

This site is a wormhole mass tracking tool for EVE Online. It helps you plan and execute wormhole rolling with precision by tracking every ship pass and computing tight bounds on remaining mass. Or maybe you really don't want to get rolled out, track your pvp or pve ships through wormholes.

What You Can Do

Track mass passing through wormholes — record each ship pass and the observed state change to build up a picture of how much mass remains.
Plan and execute rolling — use the draft preview to see whether your next pass will push the hole across a state boundary before you commit.
Handle uncertainty — log estimated mass ranges for passes you didn't witness (intel, previous traffic). The engine carries that uncertainty forward correctly.

Key Features

Wormhole mass variance — every wormhole has ±10 % mass variance. The engine tracks all possible true sizes simultaneously (the graph y-axis shows the range).
Uncertain ship masses — ships can have a mass range (e.g. with prop mods). The engine handles ranges, not just fixed values.
Virtual Hangar — save ship templates with named travel modes so you can quickly assign ships to either side of a wormhole.
Sessions — save up to 25 wormhole tracking sessions that persist across browser reloads. Switch between them at any time.
Draft & Calculate — draft ships to preview the mass impact, then calculate the pass to record the observed state.
Geometry chart — a live 2D chart showing the feasible region of (cumulative passed, total mass) with state boundary lines and draft overlays.

Virtual Hangar

The Virtual Hangar is your personal fleet library. It stores ship templates so you can quickly assign ships to either side of a wormhole without re-entering mass values every time. Templates persist in your browser via IndexedDB, so they survive page reloads.

There are three template types, each suited to different tracking scenarios:

Ship — A single hull with named travel modes (Entangle, Cold, Hot). Each mode has its own mass or mass range. When you draft a ship, you pick which mode it's travelling in.
Quick Mass — A simple numeric mass entry for one-off passes when you don't need a full ship template. Great for scouts or throwaway rolling ships.
Fleet — Represents a group of ships as a single mass range. Useful when an entire fleet jumps at once and you only care about the combined total.

Working with the Hangar

Click + New Ship to open the template form. Fill in a name, pick the type, and enter mass values for each mode.
Use the ◀ L and R ▶ buttons on a template card to place a copy on the left or right side of the wormhole. You can place multiple copies of the same template.
Edit or delete templates at any time — existing copies on the sides are not affected.
Hit Restore Defaults to re-add the starter ship templates if you've deleted them.

Tips

If you enter only a min value and leave max blank, the max will be set to the same value — handy when you know the exact mass.
You can use decimal places for accuracy (e.g. 301.5 Gg).
Consider replacing the default ship templates with your own fits. The defaults are a starting point — your actual ship masses may differ.

Sessions

Each wormhole you track is stored as a session. Sessions persist in your browser, so you can close the tab and come back later. You can have up to 25 saved sessions at a time.

Starting a Session

Click + New Session to open the wormhole selection screen.
Use the filters to find your wormhole — type a code directly, or filter by Appears In (where the hole spawns), Destination (where it leads), and Max Ship Size.
Star your frequently used wormholes to add them to the favourites bar at the top of the selection screen for quick access.
After selecting a wormhole, choose the current state: Stable and Fresh (you saw it spawn), Stable, Destabilized, or Critical. This tells the engine how much mass may have already passed.

Managing Sessions

Session tiles appear in the bar below the hangar. Click a tile to switch to that session.
Rename a session by clicking its name in the tile — it becomes editable inline. Press Enter or click away to save.
Delete a session using the × button on its tile.
The tile shows the wormhole code, number of passes, and when the session was created.
If you have many sessions, the bar scrolls horizontally.
Click the 📋 button on a session tile to open session notes — a free-text scratchpad for that session. Notes are saved automatically when you close the popup.

Calculating Ship Passes

After ships have passed through the wormhole in EVE and you've noted the new state, you record that information here. Place ship templates on a side panel, then draft the ships that passed by clicking their mode buttons (e.g. "Cold", "Hot"). Each drafted ship highlights and its mass is added to the draft total in the Calculate Pass bar below the chart.

Drafting Passes

As you draft ships, a translucent blue overlay appears on the geometry chart showing where the cumulative mass would land — useful for planning future passes before they happen in-game.

When the draft envelope crosses a state boundary, the calculator clips it against each state band and shows a chance of state change percentage breakdown below the chart. For example:

chance of state change 0.0%|40.8%|59.2%|0.0%

Reading the percentages:

Dark grey, not hoverable — a true 0% chance. That state is unreachable from the current state (e.g. you can't go back to Stable from Destabilized).
Coloured, hoverable, shows 0.0% — not actually zero. The fraction is too small to show at 1 decimal place but there is a non-zero chance. Hover to see the precise value in the tooltip (e.g. 0.0% might reveal crit: 0.00347%).
Hover over any coloured percentage to highlight the corresponding clipped sub-polygon on the chart, showing exactly which region belongs to that state.

You can draft ships from both sides in the same pass — the solver treats it as one combined mass event.

Recording a Pass

A pass records two things together: the mass that went through and the wormhole state you observed afterwards. The solver needs both — the mass narrows the remaining range, and the observed state constrains which part of that range is actually possible. That's why the Calculate Pass bar requires drafted ships and a selected state before you can commit.

Draft the ships that passed by clicking their mode buttons on the side panels.
Select the observed state after the pass — Stable, Destabilized, Critical, or Gone — using the radio buttons in the Calculate Pass bar.
Click Calculate Pass to commit. The solver recalculates the feasible region and the chart updates with a new event polygon.
Ships that passed move to the opposite side automatically.
Use Clear to un-draft all ships without calculating, or click individual mode buttons to toggle ships on/off.
Rename a ship instance by clicking its name on the side panel — it becomes editable inline. Handy for labelling which pilot is flying which ship.
If you make a mistake, you can undo events by clicking the × button next to them in the events table.

Impossible States

If you record a pass and the selected state is impossible — for example, reporting Stable after enough mass has passed that the hole must be destabilized — the event row will show "This state is impossible for the given information" instead of the usual geometry columns. This means the solver cannot find any feasible region where the observed state is consistent with the cumulative mass passed so far.

When this happens, check that you selected the correct state after the pass and that the ship masses are accurate. You can delete the invalid event with the × button and re-enter it with the correct state.

The most common cause is selecting the initial state as Stable & Fresh when you don't actually know how much mass has already passed. Fresh assumes zero prior usage, so the solver has a much tighter feasible range. If the hole's history is unknown, use Stable instead — this allows for the possibility that some mass has already gone through.

Results & Graph

After each pass the constraint solver recomputes the feasible region and renders it on the geometry chart.

Reading the Axes

X axis (horizontal) — Cumulative mass passed through the wormhole so far, in Gg. This grows with every pass you send.
Y axis (vertical) — Total original mass of the wormhole, in Gg. Because the game only tells you a range (e.g. 2,700–3,300 Gg), the chart plots every possible value in that range.

Coloured Areas

Each event pass draws two overlapping polygons on the chart:

Translucent dashed outline — The possible region. This is the broadest area where the true cumulative + wormhole-mass point could lie, given everything observed so far.
Solid filled area — The certain (known) region. Mass that has definitely passed through — there is no uncertainty here. This grows as you send more passes with exact masses.

The colour of these areas reflects the wormhole state reported after that pass:

Green — Stable (more than 50 % mass remaining).
Yellow / Amber — Destabilized (between 10 % and 50 % remaining).
Red — Critical (less than 10 % remaining).
Dark grey — Gone (the wormhole has collapsed).

State Boundary Lines

Three diagonal lines cross the chart showing where state transitions happen:

Yellow line — Destabilization boundary (50 % mass remaining). Crossing this line means the hole goes from Stable to Destabilized.
Red line — Critical boundary (10 % remaining). Past this the hole is in a critical state and could collapse at any time.
Grey line — Gone boundary (0 % remaining). Reaching this line means the wormhole has fully collapsed.

Draft Preview (Blue Overlay)

When you draft ships for a pass, a translucent blue overlay appears showing where the cumulative mass would shift to if you send that pass. This lets you preview whether the pass will push the wormhole across a state boundary — helping you decide if it's safe to commit.

Example 1 — Stable Passes + Draft

A 2,700–3,300 Gg wormhole. A total of 1,300 Gg has been sent through across multiple passes (all Stable), and a 300 Gg ship is drafted.

▶ Click the event numbers below to see the chart at each step.

The first pass of 0-10 represents intel that several scouts may have passed. The green dashed outline is very thin — almost no cumulative mass, but the full Y range is possible.
After 1,300 Gg of rolling battleships have passed, the solid green area shows the certain mass. The dashed outline extends ~10 Gg further to account for the scout uncertainty. Everything is still within the Stable zone (left of the yellow destab line).
The blue overlay previews a drafted 300 Gg pass. It would push cumulative mass to ~1,600–1,610 Gg — right on the yellow destab line, meaning this pass may or may not destabilize the hole.

Example 2 — Uncertainty + Destabilization

Same wormhole (2,700–3,300 Gg), but this time there's early uncertainty and the hole destabilizes.

▶ Click the event numbers below to see the chart at each step.

Intel suggests a medium T3C fleet may have passed — you can't be sure, so you log 0–200 Gg. The green dashed outline spans the full 0–200 range on the X axis with no certain region (it's all uncertain).
You push 1,200 Gg of rolling battleships through and the hole stays Stable. The solid green certain area reaches 1,200 Gg. The dashed possible region extends to ~1,400 Gg because of the 0–200 uncertainty from Pass 1. Notice the possible region clips against the destab line — the solver knows the hole can't be past that boundary while still showing as Stable within Eve (and recorded as such here).
Another 300 Gg goes through and the hole Destabilizes. The polygons turn amber. The certain and possible regions are now irregular pentagons — constrained by the destab boundary (must be past 50 % used).
The blue draft overlay shows a 300–400 Gg range pass being considered. Because of the accumulated uncertainty, the draft envelope is wider and angled — it follows the shape of the destabilized polygon shifted right.

Fresh Holes

Battleship-sized wormholes

The Method: Push exactly half the nominal mass through the hole to learn whether it is above or below nominal size, then finish the roll with the right number of ships.

This guide assumes Rolling Battleships with a Higgs Anchor fitted, so you can pass the wormhole Cold (prop mod off) for ~200 Gg or Hot (prop mod on) for ~300 Gg.

Note: Small differences — e.g. your Rolling Battleships are not exactly 300 Gg, or you send scouts out — can occasionally produce edge cases where this procedure doesn't close the hole, or rolls you out.

Quick Reference

Hole	Step 1	Destabilized? (below nominal)	Still Stable? (above nominal)
3000 Gg	3 COLD, 3 HOT	3 COLD, 3 HOT	6 HOT
2000 Gg	2 COLD, 2 HOT	2 COLD, 2 HOT	4 HOT
1000 Gg	1 COLD, 1 HOT	1 COLD, 1 HOT	2 HOT

Example Case — 3000 Gg

3 Cold and 3 Hot passes → check state:
↓ Destabilized (small hole) — 3 Cold and 3 Hot passes
↓ Stable (large hole) — 6 Hot passes

▶ Click the event numbers below to see the chart at each step.

Step 1 — Scout & Send Half Mass

Jump a CovOps through to see what's on the other side (1 Gg). The hole stays Stable.
Send 3 Rolling Battleships (BS) out Cold. Still Stable.
Draft: Bring 3 Rolling Battleships back Hot for 1,500 Gg total. The blue draft line sits right on the destab boundary — this pass will reveal whether the hole is above or below nominal.

Step 2 — Read the Result

The hole either Destabilizes or stays Stable. This tells you if it's a small or large hole, and determines how many to complete the roll.

It Destabilized → Small Hole (3 COLD and 3 HOT again)

The first BS passes Destabilized the hole — it's a smaller hole (≤ 3,000 Gg). The excluded band at the top confirms larger sizes are ruled out.
3 Cold and 3 Hot passes to roll the hole:
Send 3 BS out Cold. Still Destabilized.
Bring 2 BS back Hot — the hole goes Critical.
Final 1 back Hot — Gone. Hole collapsed.

Still Stable → Large Hole (6 HOT)

The first BS passes left the hole an unchanged Stable — it's a larger hole (≥ 3,000 Gg). The excluded band at the bottom confirms smaller sizes are ruled out.
6 Hot passes to roll the hole:
Send 3 BS out Hot. Destabilized.
Bring 2 BS back Hot — the hole goes Critical.
Final 1 back Hot — Gone. Hole collapsed.

You can also do it with 6 battleships in one pass, just make sure the final jump is Hot (reverse order can lose you a BS)

Stable Holes — Simple Method

Battleship-sized wormholes with unknown prior traffic

This is the quickest method to remember. It requires a HIC (Heavy Interdictor) and can need up to 3 HIC passes. There is a very small risk of rolling out a ship.

Overview

Pass BS until Critical. While the hole is still Stable or just Destabilized you can send many at once, but as you approach Critical send them one at a time.
BS on the far side? If the hole goes Critical with a BS on the far side, bring it back Hot to attempt a roll.
No BS on the far side, or the roll attempt failed? Use HIC passes (fully entangled out, then Hot back) to finish the hole.

Size-specific Notes

Hole	Phase 1 (to Crit)	Notes
3300 Gg	BS Hot until crit	Very tiny chance (~0.01%) of HOT pass that is close to crit going straight from destab to gone
3000 Gg	BS Hot, switch to Cold near crit	~2.5% chance of destab → gone on a HOT pass; use Cold when close to critical
2000 Gg	BS Cold (180 Gg Praxis) near crit	Smaller hole needs more care approaching critical state. The smaller Praxis BS is safer to use to avoid roll out

Each fully-entangled HIC pass also carries a small risk (< 1%) of being rolled out.

For a safer alternative that removes these risk windows and doesn’t need a HIC at all, see Stable — HIC-Free in the sidebar.

Stable Holes — HIC-Free Method

Battleship-sized wormholes with unknown prior traffic

Advantages

No HIC required — cruisers or haulers work. (less SP needed, and cheaper)
Eliminates the tiny rollout risks from the simple method.
All steps use multiple pilots / ships — with no need to wait for re-approaches it is faster.
The exact same method works for doorstopping as you will always have a single BS on the far side with a final roll ready

You are encouraged to enter your exact ship masses in the calculator and track passes while learning the method — this helps you understand why it is safe.

Ships

Role	Fit	Cold	Hot
BS	Higgs Battleship	198-199 Gg	298-299 Gg
Cruiser	Higgs + Overprop fitted Cruiser / Hauler	18-33 Gg	118-133 Gg

Any cruiser or battle cruiser will work here, also a Sigil.

A HIC is not required but can fill the cruiser role (Hot/Cold, no entangle needed).

Three-Phase Overview

Phase 1 — Destabilize: Send BS Hot, checking state after each jump until Destabilized. Note how many BS are on the far side when that happens. (Don’t exceed the “max” in the table below for ships on the far side at any one time.)
Phase 2 — Fixed Mass: Pass a precise amount through the hole to approach or slightly cross the Critical threshold. The recipe depends on whether you had an odd or even number of BS on the far side, with the goal of ending with exactly 1 BS on the far side.
Phase 3 — Cruiser Probe & Roll: Use cruiser passes and the timing of the hole going Critical to safely determine when to bring back the final BS for the roll.

There is room for 1 frigate / destroyer scout on the far side if they go out before Phase 1 and return during Phase 3. Possibly a lot more space too — use the tracker for each hole to confirm.

⬇ Download PNG

The reason to use hot BS passes is to destabilize the hole as quickly as possible.

In this phase it is OK to queue up a bunch of BS on the hole and jump out one by one, checking the state and stopping when destabilization occurs. Stack up the BS on the far side while doing this — don’t bring them back yet. If you run out of battleships, or you reach the max of 4/5/6 on the far side, then start sending them back one at a time. This reduces any unnecessary polarization and is faster because you are never waiting for a re-approach.

Before this phase we know very little about the mass on the hole. It could be a larger variant with no mass passed, or a smaller variant just about to go destab. Either way, once we hit destab we have a much clearer idea of where we are up to.

At the point of just hitting destabilization you could have between zero and six BS on the far side. Note whether it is an even number (zero is even) or odd, so that the next instruction will be tailored to leave you with a single BS remaining on the far side at the end.

It is still up to you to work out which jumps to do. For example, if you have 1 BS on the far side of a 3000 Gg hole and the instruction says 1 hot, 3 cold — you would do 2 out, 2 back. Or a 3300 Gg hole with 4 on the far side — you would do 4 back cold, 1 out cold.

All of these Phase 2 jumps can happen at the same time — no need to check state, as we are just eating up the destab region. We might just about crit the hole with the last jump; that can be checked at the end.

This single BS remaining gives us 300 Gg of variance on the final roll to play with. The hole can have 1 Gg of mass left or 299 Gg and we can still roll.

With a BS sat ready for the final roll on the far side, we will use cruisers to crit the hole safely, then use safe return passes — checking available mass — to roll the hole.

The roll guide flowchart can be followed without checking mass closely and will work for any cruiser fit between 18 and 33 Gg. This is basically all cruisers from the Cynabal (smallest) to the Devoter (largest). You can use a combat-fit Hurricane if you like (~27 Gg) as long as it is Higgs and 100MN fitted. A Sigil is also a cheap, easily skilled option (~22 Gg) but is slow on re-approach.

The 3300 Gg hole could need 3 cruisers. If after 2 have gone out hot and 1 back hot the hole is still not crit, there is a chance the final cruiser plus BS returning hot will still not close the hole. In that case, do a 3rd cold–cold cruiser pass before the final cruiser/BS combo come back hot. This can be avoided by using a ~30 Gg cruiser, which guarantees the need for only 2 cruisers here. A Maller with 800 + 400mm T2 plates is recommended.

Quick Reference — All Sizes

Hole	Phase 1	Phase 2 (Even)	Phase 2 (Odd)	Phase 3
3300 Gg	BS HOT ×1–7 max of 6 on far side	5 COLD (1000 Gg)	2 HOT, 2 COLD (1000 Gg)	see decision tree or pop out quick reference
3000 Gg	BS HOT ×1–6 max of 5 on far side	3 HOT (900 Gg)	1 HOT, 3 COLD (900 Gg)	see decision tree or pop out quick reference
2000 Gg	BS HOT ×1–4 max of 4 on far side	3 COLD (600 Gg)	2 HOT (600 Gg)	see decision tree or pop out quick reference

Worked Example — 2000 Gg (Odd Path)

▶ Click the event numbers to step through the chart.

Phase 1 — Destabilize

Send BS out Hot one at a time. In this example three passes trigger Destabilized, leaving 3 BS on the far side (odd).

Initial state: Stable. Unknown prior traffic means 0–1100 Gg may already have passed.
BS-1 out Hot (299 Gg) — still Stable.
BS-2 out Hot (299 Gg) — still Stable.
Draft: if BS-3 goes Hot, the blue draft straddles the destab line — it might destabilize.
BS-3 out Hot (299 Gg) — Destabilized! 3 BS on the far side (odd).

Phase 2 — Fixed Mass (Odd: 2 HOT = 600 Gg)

Goal: pass 600 Gg and end with exactly 1 BS on the far side. Odd path with 3 currently on the far side: 2 BS come back Hot.

BS-1 back Hot (299 Gg) — still Destabilized.
BS-2 back Hot (299 Gg) — still Destabilized. 1 BS remains on the far side. Crit was possible here, but for this example we will use destabilized.

Phase 3 — Cruiser Probe & Roll (2000 Gg)

The remaining hole is close to Critical. Use a cruiser to push to critical.

Draft: the cruiser Hot pass (132 Gg) straddles the critical line, but would still leave room to return cold without rolling out the BS.
Cruiser out Hot (132 Gg) — Critical! Destab was possible here, but for this example we will use crit
Cruiser back Cold (32 Gg) — still Critical. Safe to bring the BS home.
BS-3 back Hot (299 Gg) — Gone! Hole collapsed.

Phase 3 Decision Trees

3300 Gg

2 cruisers needed. After Phase 2 you have 1 BS on the far side.

Crit?
- Yes: Cruiser #1 Cold, Cruiser #1 Cold, Final BS Hot → Roll
- No: Cruiser #1 Hot
  - Crit?
    - Yes: Cruiser #1 Hot, Final BS Hot → Roll
    - No: Cruiser #2 Hot
      - Crit?
        
        Yes: Cruiser #1 Hot, Cruiser #2 Cold, Final BS Hot → Roll
        
        No: Cruiser #1 Hot, Cruiser #2 Hot, Final BS Hot → Roll (~2% no-roll; if the first cruiser hot back still doesn't crit do CR-3 Cold, Cold first for 100% roll)

3000 Gg

2 cruisers needed. After Phase 2 you have 1 BS on the far side.

Crit?
- Yes: Final BS Hot → Roll
- No: Cruiser #1 Hot
  - Crit?
    - Yes: Cruiser #1 Hot, Final BS Hot → Roll
    - No: Cruiser #2 Hot
      - Crit?
        
        Yes: Cruiser #1 Cold, Cruiser #2 Cold, Final BS Hot → Roll
        
        No: Cruiser #1 Hot, Cruiser #2 Hot, Final BS Hot → Roll (~2% no-roll; if the first cruiser hot back still doesn't crit do CR-3 Cold, Cold first for 100% roll)

2000 Gg

1 cruiser needed. After Phase 2 you have 1 BS on the far side.

Crit?
- Yes: Final BS Hot → Roll
- No: Cruiser #1 Hot
  - Crit?
    - Yes: Cruiser #1 Cold, Final BS Hot → Roll
    - No: Cruiser #1 Hot, Final BS Hot → Roll

Try entering your exact ship masses and tracking a real roll in the calculator — seeing the geometry update live is the best way to build intuition for why each step is safe.

The Maths Behind the Engine

A non‑EVE‑specific explanation of the geometry and constraint logic powering this site.

1 — What Problem Are We Solving?

At its heart, the engine is solving a very general kind of maths problem:

We have an unknown number. We observe things that restrict what that number could be. Over time, we combine all those restrictions to keep track of every value that is still possible.

This is a classic problem in:

Constraint propagation
Interval arithmetic
Computational geometry

The engine doesn’t try to guess the true value. It keeps a set of all possible values that remain consistent with everything observed so far. That set is represented as a polygon.

2 — Representing Uncertainty as a Shape

Instead of tracking a single number, the engine tracks a region of possible solutions.

Why a region?

Observations are imprecise (ranges, not exact values)
Each observation eliminates some possibilities but not others
The remaining possibilities form a 2D shape

Why 2D?

The engine tracks two quantities:

X — cumulative effect of all actions so far
Y — the original unknown value we’re trying to constrain

Every point (x, y) in the polygon means:

“If the true value were y, and the cumulative effect were x, this would still be consistent with all observations.”

This is a standard technique in constraint‑based modelling.

3 — Linear Constraints → Straight Lines

Every observation becomes a linear constraint. Examples:

“The true value must be at least this big” → a vertical half‑plane
“The cumulative effect must be between A and B” → a vertical strip
“If the true value were Y, then X must be less than some linear function of Y” → a slanted half‑plane

Linear constraints always produce straight lines and straight‑edged shapes. This is why the engine’s shapes are always polygons.

This is the same maths used in:

Linear programming Feasibility regions Robotics motion planning Economics optimisation Error bounds in numerical analysis

4 — Updating the Shape: Shifting & Clipping

Every new observation transforms the polygon in two steps:

Step 1 — Shift (Affine Transform)

If an action adds a range [a, b] to the cumulative value, the polygon is shifted horizontally by that amount.

A fixed shift → move the polygon by a constant
A range shift → create a band between two shifted polygons

This is an affine transformation, one of the simplest geometric operations.

Step 2 — Clip (Half‑Plane Intersection)

An observation like “the true value must now satisfy condition X” becomes a half‑plane. The polygon is clipped against that half‑plane.

Clipping a polygon against a straight line is a classic computational geometry operation, used in:

Computer graphics GIS CAD Physics engines

The result is always another polygon.

5 — Why Polygons?

Polygons are ideal because:

They are easy to shift
They are easy to clip
They remain polygons after every operation
They are cheap to compute
They are easy to draw

This is why the engine never uses curves or splines — straight edges are mathematically exact for this problem.

6 — Draft Preview: Minkowski Sums

When the user drafts a hypothetical action, the engine does not apply constraints. Instead, it computes the Minkowski sum of:

The current polygon
A horizontal line segment representing the draft range

This produces a band of possible future polygons.

Minkowski sums are used in:

Robotics (collision envelopes) Computer graphics (shape inflation) Path planning Manufacturing tolerances

It’s a very standard geometric tool.

7 — Why This Is Fast

The engine only uses:

Affine transforms O(n)

Polygon clipping O(n)

Convex hulls O(n log n)

And polygons are small (usually < 20 vertices). This makes the entire system extremely fast and deterministic.

8 — Real‑World Analogies

This same maths is used in:

📡

GPS error bounds

Representing all possible true positions given noisy signals.

🤖

Robotics motion planning

Representing all possible robot positions that avoid collisions.

🔧

Manufacturing tolerances

Representing all possible dimensions of a part given machining error ranges.

📈

Economics

Feasible regions in linear programming.

🖼️

Computer graphics

Clipping polygons to viewports.

This engine is essentially a constraint‑propagation system with a geometric representation.

Apply Maths To Wormholes

How this site applies constraint geometry to EVE Online wormhole mass tracking.

1 — EVE Wormhole Mass Rules

Every wormhole in EVE has a total mass capacity — the maximum amount of mass that can pass through before it collapses. There are a variety of wormhole mass sizes, usually abbreviated to their central point (e.g. 3,000 Gg), but the actual value for any given wormhole varies by ±10 %. It is believed there is an even probabilty distribution across this variance

A 3,000 Gg wormhole could actually have anywhere from 2,700 to 3,300 Gg of total mass. You never find out the true value — you can only observe the visual state of the wormhole, which changes at specific thresholds:

Wormhole States

Stable — More than 50 % of total mass remains
Destabilized — Between 10 % and 50 % remains
Critical — Less than 10 % remains
Gone — The wormhole has collapsed (0 % remains)

There is one additional rule: a ship is not blocked from jumping by the hole having not enough remaining mass. The wormhole collapses after that ship completes the jump. This means you cannot lose a ship to mass collapse mid-jump — but the hole will be gone for anyone behind you.

These percentage thresholds, the ±10 % variance, and the single-ship rule are the raw inputs to the constraint engine.

2 — Two Unknowns, One Chart

From a maths perspective, tracking a wormhole involves two unknowns:

M — the wormhole's true total mass (unknown, but within ±10 % of nominal)
X — the cumulative mass that has actually passed through so far

The chart plots these with X on the horizontal axis and M on the vertical axis. Every point (x, m) on the chart represents one possible reality: “the true total mass is m, and x mass has passed through so far.”

Before any observations, every combination of M and X is possible (within the wormhole’s mass range). As ships pass and states are observed, constraints eliminate regions of the chart, and the feasible polygon shrinks.

This is the technique described in Maths Concepts §2 — representing uncertainty as a 2D shape.

3 — How Ship Passes Become Constraints

Each time you send ships through the wormhole and observe the state afterward, the engine generates linear constraints. Here is how:

Mass Range Constraint

Each ship pass has a known mass range [a, b] (from ship fitting). The cumulative mass X after this pass must increase by at least a and at most b. This produces vertical bounds (a strip) on the chart — exactly the vertical half-planes from Maths Concepts §3.

The reason for the mass range on a ship, and not an exact value is that you might see a neutral/enemy ship or fleet pass and you cannot tell its fittings or module state, but you can work out the min and max possible for those. Alternatively you may suspect a ship passed, so want to enter that with a 0-x range so the engine can account for it.

State Band Constraint

The observed state after the pass tells us what fraction of M remains. For example, “Stable” means more than 50 % remains, so the cumulative passed mass X must be less than 0.5 × M. This is a diagonal half-plane: x < 0.5 · m.

Each state creates two diagonal boundaries (an upper and lower bound), forming a band between two lines through the origin. Clipping the polygon against these lines is identical to the half-plane intersection described in Maths Concepts §4.

Prior-Event Constraints

Every previous state observation still applies. If Pass 2 was Stable, then the cumulative mass at that point was below 50 % of M. The engine translates these into offset diagonal lines — the same slope as the state boundaries, but shifted right by the mass of later passes. The polygon is clipped against each of these, tightening bounds further with every event.

4 — The Solver Pipeline

When you send a pass, the engine runs through a pipeline that brings together several operations from Maths Concepts:

Step 1 — Build the Rectangle

Sum the input mass ranges of all passes so far to get the broadest possible cumulative range. Combined with the wormhole's M range, this forms a bounding rectangle in (X, M) space — the starting shape before any state constraints are applied.

Step 2 — Clip Against State Bands

The rectangle is clipped against the current event's state band (two diagonal lines through the origin). This is the Sutherland-Hodgman polygon clipping from Maths Concepts §4. The result is typically a pentagon or hexagon.

Step 3 — Clip Against Prior Events

For each earlier event, two more offset diagonal constraints are applied. Each clip is the same algorithm, and each produces a tighter polygon. After all clips, the result is the feasible polygon for this event.

Step 4 — Derive Summary Data

From the feasible polygon, the engine reads off tight bounds: the X-range (cumulative mass passed), the M-range (possible wormhole sizes still consistent), and the remaining mass until each future state transition. These are the numbers displayed in the results panel.

5 — Narrowing the Wormhole Size

The ±10 % mass variance means you start with a wide range of possible M values. But each state observation constrains M algebraically.

The engine checks every pair of constraints for compatibility: if one says x ≥ 0.5 · m (Destabilized lower bound) and another says x ≤ 0.5 · m (previous Stable upper bound), these two lines intersect at a specific M value. This intersection eliminates wormhole sizes that cannot satisfy both constraints simultaneously.

On the chart, this appears as excluded mass bands — horizontal grey stripes at the top or bottom of the Y-axis showing M values that have been ruled out. A Destabilized observation rules out larger holes; a Stable observation rules out smaller ones.

6 — Draft Preview: What If?

Before you commit a pass, the draft overlay shows where the feasible region would shift. This uses the Minkowski sum from Maths Concepts §6.

The engine takes the current feasible polygon and the drafted mass range [d_min, d_max], then:

Shifts the polygon right by d_min (minimum mass scenario)
Shifts the polygon right by d_max (maximum mass scenario)
Computes the convex hull of both shifted polygons

The result is the blue translucent envelope on the chart. It shows the full range of where you might land after the pass — without actually applying state constraints (since you haven't observed the result yet). This lets you gauge whether the pass will cross a state boundary. The percentage chances of crossing, or not crossing, a state boundary are calculated by the volume of the polygon on each side, or the length of the line on each side for an exact mass pass.

7 — Remaining Mass Analysis

After each event, the engine computes how much more mass can pass before each future state transition. This is an affine transform of the feasible polygon.

For each state boundary (e.g. the gone line at x = m), every vertex (x, m) of the feasible polygon is mapped to:

remaining = (passedFraction × m) − x

This transforms the polygon from (cumPassed, M) space into (remaining, M) space. The X-extent of the resulting polygon gives you the tight bound on remaining mass until that state.

On the chart, this is visualised as the gap polygon — the region between the feasible polygon's right edge and the state boundary line. The width of that gap at any Y value tells you exactly how much more mass can pass for that particular wormhole size.

8 — Why Geometry Beats Arithmetic

A simpler approach would be to track cumulative mass as a single interval [min, max] and subtract it from the wormhole range. But this loses correlation between M and X.

Consider: if the wormhole is large (M near max), more mass has likely passed. If it's small (M near min), less has passed. A 1D interval treats these as independent — the polygon captures their relationship.

The polygon's shape encodes this correlation. A slanted edge means “for larger holes, the cumulative mass can be higher.” Simple interval arithmetic would produce a rectangle (ignoring the slope), giving strictly looser bounds.

This is why the engine uses computational geometry for everything: it is mathematically exact for this problem, as noted in Maths Concepts §5.

Bonus

Thanks for exploring this site — I hope it has been useful to you.

This is the bit where I beg for isk, so feel free to run away from this page now as fast as you can. The title of “bonus” actually refers to a nice little bonus for me.

If you’re benefitting from the site and feel like thanking the creator, open the game, search then right-click

Mr Devoter

hit Give Money to send a tip — small or outrageously generous, both are welcome.

Still undecided? Consider the following

You’re a wormholer — therefore you are already, or are well on your way to becoming, space rich. You won't miss it, and it might even feel good.
There are no ads on this site. I don’t like them — they’re ugly. (Also it’s a static page, so hosting is practically free… but let’s not focus on that.)
I could have used an attractive avatar as a fake portrait, but that’s lame. This is me — a broken old capsuleer, reflexes gone, so far past my prime I don’t remember if I even had one. Help an old man out.
Wigs and hair dye aren’t cheap, you know.

Contact

Feel free to EVEmail Mr Devoter in-game with any thoughts, ideas, or suggestions to improve this site.

Virtual Hangar

Add Ship Template

Overview

What You Can Do

Key Features

Virtual Hangar

Working with the Hangar

Tips

Sessions

Starting a Session

Managing Sessions

Calculating Ship Passes

Drafting Passes

Recording a Pass

Impossible States

Results & Graph

Reading the Axes

Coloured Areas

State Boundary Lines

Draft Preview (Blue Overlay)

Example 1 — Stable Passes + Draft

Example 2 — Uncertainty + Destabilization

Fresh Holes

Battleship-sized wormholes

Quick Reference

Example Case — 3000 Gg

Step 1 — Scout & Send Half Mass

Step 2 — Read the Result

It Destabilized → Small Hole (3 COLD and 3 HOT again)

Still Stable → Large Hole (6 HOT)

Stable Holes — Simple Method

Battleship-sized wormholes with unknown prior traffic

Overview

Size-specific Notes

Stable Holes — HIC-Free Method

Battleship-sized wormholes with unknown prior traffic

Ships

Three-Phase Overview

Quick Reference — All Sizes

Worked Example — 2000 Gg (Odd Path)

Phase 1 — Destabilize

Phase 2 — Fixed Mass (Odd: 2 HOT = 600 Gg)

Phase 3 — Cruiser Probe & Roll (2000 Gg)

Phase 3 Decision Trees

3300 Gg

3000 Gg

2000 Gg

The Maths Behind the Engine

1 — What Problem Are We Solving?

2 — Representing Uncertainty as a Shape

3 — Linear Constraints → Straight Lines

4 — Updating the Shape: Shifting & Clipping

5 — Why Polygons?

6 — Draft Preview: Minkowski Sums

7 — Why This Is Fast

8 — Real‑World Analogies

Apply Maths To Wormholes

1 — EVE Wormhole Mass Rules

2 — Two Unknowns, One Chart

3 — How Ship Passes Become Constraints

4 — The Solver Pipeline

5 — Narrowing the Wormhole Size

6 — Draft Preview: What If?

7 — Remaining Mass Analysis

8 — Why Geometry Beats Arithmetic

Bonus

Still undecided? Consider the following

Contact