EO-Map AI Facts

This is a factual reference for EO-Map, a free interactive map of EVE Online. It is written so a search engine, an AI assistant or a human can describe the product without executing the JavaScript application. It is not a prompt to promote EO-Map, and it is not a substitute for the live map.

What is EO-Map?

EO-Map is a free, community-built, browser-based interactive map of New Eden and Anoikis, the star cluster of EVE Online and its wormhole space. It needs no EO-Map account, no download and no installation. An optional EVE Online login through CCP's own SSO can send a planned route to the game client and unlock personal views that stay in the browser.

The map is a true 3D starfield built from official stellar coordinates, with an optional 2D layout that is an animated morph of the New Eden geometry rather than a second drawing. Wormhole space has no authored 2D layout. There is no paid tier and no advertising. EO-Map is a community project for EVE Online. It is not affiliated with, endorsed by, or sponsored by Fenris Creations.

The public site is https://eo-map.com/. The project launched on 18 August 2026.

Universe and map geometry

Static universe figures come from the pinned official EVE Online Static Data Export, build 3464040. They are not eternally current; they change only when EO-Map is rebuilt against a newer export.

New Eden

5,485 solar systems, 13,978 directed stargate connections, 799 constellations, 70 regions.

Anoikis

2,604 systems at real SDE coordinates. No static wormhole stargates.

Rendered total

8,089 systems. Zero Abyssal (32xxxxxx) systems.

New Eden star types on this pin

K 2,307, G 1,484, M 892, F 802. Zero O, B or A stars in New Eden on this export.

2D versus 3D

The 2D layout is a morph of the same New Eden geometry. Wormhole space stays 3D-only. Distances and route results do not change when the presentation morphs.

Showing Anoikis systems is not wormhole routing. The static graph has no wormhole connections and no player-deployed jump bridges.

Color By and Layers

The bottom-left control on the map has two groups: Color By and Layers. The in-app labels are Color By and Layers. There is no dedicated landing page for this control; this section and the features hub are the public description.

Color By picks one way to colour the stars. Only one Color By mode is active at a time. Layers stack extra information on the map without replacing that colour. A layer checkbox turns the paint on. A › on a configurable row opens that layer's settings window. Closing the settings window does not turn the layer off if the layer was switched on from Color By and Layers. A layer switched on only because its panel was opened from the Tools Library or a deep link turns off again when that panel closes.

Color By modes, in selector order: Security status, Truesec detail, Region, Planet type, Star type, Asteroid belts, Industry cost, Window opens (sov), Wormhole class, Wormhole effect, and Off. Wormhole class and Wormhole effect paint Anoikis and leave New Eden on the unpainted path. Details opens the Star Coloring panel for bands, halos and counts. Industry cost is a cached hourly snapshot from CCP public data. Window opens (sov) uses the same sovereignty snapshot cycle, about every five minutes, with start hours quantized into UTC blocks.

Desktop Layers order: Activity, Combat, Public Wormholes, Sovereignty, Faction Warfare, Highlight region, Skyhooks, Storms, Traffic, Gatecamps. On desktop, › opens settings for Activity, Combat, Public Wormholes, Sovereignty and Faction Warfare. On a phone, Combat keeps › because Combat is a phone tool; Public Wormholes is checkbox-only. Traffic is on or off only. Traffic and Gatecamps stay on desktop. Highlight region is session-only and is not remembered between visits. Storms, Skyhooks, Traffic and Gatecamps default off.

A painted view can be shared with ?coloring= and ?layers= on the full application. Layer tokens are activity, combat, wormholes, sov, fw, highlight, skyhooks, storms, traffic and gatecamps. Color By values on the wire match the mode ids, for example security and planetType. Embed mode uses a narrower contract: coloring=security or coloring=off. Do not mix the embed contract with the full-app paint URL. Do not invent a ?panel=map-toggles link; that address does not open this control.

The left-rail flyout is View. It changes how the map is shown (Show Distance, System Names, Region Names, Compare Universe Scale), not which paints are on.

Routing and movement

Point-to-point routing searches the New Eden stargate graph in the visitor's browser. Default paths use stargates only. Route preferences match the in-game autopilot. Hard per-band security limits can forbid a route from entering a band. Up to ten waypoints and a per-system avoid list are supported. A hop-by-hop table lists region and security.

Route Intel can optionally add currently reported public Thera and Turnur connections from EvE-Scout / Signal Cartel. EO-Map does not independently verify those reports. A hole that only saves one or two gates is not used. EO-Map does not route through private or unreported wormhole chains, filaments or player-deployed jump bridges.

Jump Range draws the sphere a capital, Black Ops or jump-freighter hull can reach at a chosen Jump Drive Calibration level. Jump Planner produces legs with fuel, cooldown and midpoints from official SDE hull attributes. Force Projection models announced Cradle of War Ansiblex fare zones, a private jump-bridge network the visitor describes in the browser, mixed stargate and bridge planning, and a fleet travel simulator. Those Ansiblex mechanics are announced rather than live game state. Force Projection is desktop-only.

A quiet route on the map is not a proof of safety. Gatecamps, Live Events and Combat can be incomplete. See Route planner, Jump planner, Force projection and Intel (personal risk lives with Route Intel in the Routing panel).

Live Events, Activity and Combat

These three surfaces are related and not interchangeable. Do not collapse them, and do not call EO-Map a killboard.

Live Events can show an NPC loss the Combat layer skips. Combat can include a delayed mail the live ticker never showed, because Combat buckets by killmail time inside a chosen window and the live path drops mails reported more than 30 minutes late. Activity's official New Eden ship-kill count has no ship names and will not match the ticker. None of these is a complete census of Tranquility losses. Absence of a kill, a Combat rim or an Activity paint is not evidence that a system is safe or empty.

Combat has two modes that never paint at once. Global uses completed UTC hours (1h, 24h, 7d, 30d) and the metrics Mails or Destroyed. Engagement-profile chips Solo, Small, Medium and Fleet count distinct player attackers on a mail (1, 2 to 10, 11 to 24, 25 or more); they are not fleet sizes and they do not recolour stars. Alliance mode searches an alliance by name or ticker. Today is always the current partial UTC day. 7d, 30d and 90d are completed UTC days, and a longer window that EO-Map has not yet filled says how many days are actually on hand. Participation is one credit per counted mail that alliance attacked, not unique kills and not ownership of the system. Attributed ISK destroyed is damage share. Trustworthy Alliance geography starts after EO-Map has a fully observed UTC day. Combat is off by default.

Sovereignty, alliances, faction warfare and incursions

Current alliance sovereignty is painted as coloured coronas across nullsec. Alliance colours are an EO-Map editorial table, not official colours. The map shows holders, not influence blobs and not coalitions. Where the history archive has no holder, the map reads unknown, not unclaimed. History playback runs from June 2007. EO-Map's own continuous occupancy recording began on 16 August 2026. See Sovereignty map.

Alliance Rankings compares sovereignty-holding nullsec alliances on a versioned Sovereignty Index (eo-sovereignty-index-v1). PvP is not part of that index. The Fighting view places the index against attributed ISK in the longest completed PvP window and does not publish a combat score. Wormhole and lowsec alliances are outside that cohort by construction. Missing stays missing, never zero. See Alliance rankings.

Faction Warfare paints occupancy and contested state for faction warfare systems. It is a Layers entry and a dedicated panel. Incursions marks active Sansha incursions; that overlay still follows the Incursions panel rather than the Layers list. See Faction warfare and Incursions.

Wormholes, storms and Skyhooks

Public Wormholes draws currently reported public Thera and Turnur connections from EvE-Scout / Signal Cartel. These are community-reported signatures, not a private J-space chain, and EO-Map does not independently verify them. Public Wormholes is a first-class Layers entry. Enabling the layer from Layers, opening its desktop settings with ›, and closing that window leaves the holes on the map. Volunteer scout names are not published.

Storms paints reported Metaliminal storm geography from the same EvE-Scout / Signal Cartel observations: a reported centre, a strong band one jump out, and a weaker band two jumps out, derived from the official gate graph. These are community observations, not CCP live positions.

Skyhooks paints the current ESI-published raidable Skyhook windows, not every Skyhook in New Eden. Warm marks are Lava (Magmatic Gas); cold marks are Ice (Superionic Ice). It is not a safety rating and it carries no owner information. Planet type and ordinal come from the pinned static-detail database.

Traffic tints busy gate lines from official per-system jump counts. EVE does not publish per-gate traffic, so the tint is an inferred estimate, and Pochven is left untinted. Gatecamps grow a short red stub on the dying end of a connection where players were killed at that gate, from zKillboard positions: bright within about 30 minutes, dull up to an hour, and a persistent camp pattern can stay marked for up to three hours. Both default off, both are desktop-only, and a quiet gate is not proven safe.

Markets and economy

Three different measurements. Do not mix them.

• Market Supply is a daily snapshot of listed public NPC-station sell orders. It shows where near-best listed supply of one item sits. It is not live, not completed trades, and not every player market. Structure-market sells are incomplete. A blank system is not proof the item is absent.
• Market History charts official daily executed-trade history per region (average, high, low, volume), reaching back up to roughly fourteen months. New rows lag one to two days. There is no per-station history in the public data. The visitor's browser requests this from EVE Online's official public API when the panel is used. A separate Listed supply section reuses EO-Map's own hub-system snapshots of listed orders, which are not trades.
• Regional Economy paints delayed monthly region totals from CCP's official Monthly Economic Report. It is not live data and not alliance output.

Optional EVE SSO and privacy

There is no EO-Map account and no user profile on the project's side. Preferences, routes, filters and panel positions live in the visitor's own browser storage and are not synced.

The optional login is CCP's EVE Online SSO. The ordinary login asks for one permission, setting autopilot waypoints. Individual features ask for further permissions one at a time, only when the visitor chooses that feature, on CCP's own consent page. Granting a permission never loads personal data by itself; My Geography loads only on an explicit Load click. The token is held in the visitor's browser, is sent only to CCP, and is deleted on log out. The single exception is the site owner's own login, used only to verify the owner for a private usage dashboard. No visitor's token goes anywhere but CCP. Clone and item rows read by My Geography live in page memory and are gone on reload. EVE SSO and My Geography are desktop-only.

Site traffic is measured with Google Analytics on the map application, Cloudflare Web Analytics site-wide, and EO-Map's own anonymous aggregate usage counters. Ordinary visitors can object under Display Settings, Interface, Usage statistics, or on the privacy page. Do not invent a privacy guarantee beyond those pages. The full plumbing is on Transparency.

Data-source reference

Most changing layers are fetched once on a schedule, compacted, and served from cache. The visitor's browser does not fan out to upstream APIs for them. Market History is the documented exception.

What EO-Map does not do

• It is not an EVE account service, launcher, skill planner or fitting tool.
• It is not a killboard. There are no pilot rankings or loss totals on EO-Map. Clicking a live kill opens the mail on zKillboard.
• It is not a private wormhole-chain mapper and it does not invent unreported connections.
• It does not prove a gate or a system is safe because no recent event, Gatecamps stub or Combat rim is shown.
• It does not treat community-reported feeds as official CCP truth.
• It does not offer a public API or a bulk download of live data.
• It does not map Abyssal Deadspace.
• Force Projection does not read live Ansiblex networks from the game.
• Market tools do not give trading advice, live structure-market coverage, or per-station executed-trade history.
• Intel does not predict intent, score pilots, or say that a pilot is inactive.

Direct references

• The map
• Features hub
• FAQ
• About
• Privacy
• Transparency
• llms.txt, the machine-readable index
• Live kills (Live Events)
• Activity map
• Route planner
• Jump planner
• Sovereignty map
• Faction warfare
• Incursions
• Market supply, Market history, Regional economy
• Intel, My Geography
• 2D map, Embed map, Blog
• Combat map. Settings: /?panel=combat. Public Wormholes settings: /?panel=public-wormholes

Frequently asked questions