Skip to content

Radius Scan Guide

IK edited this page Mar 4, 2026 · 1 revision

Radius Scan Guide

This page is a practical "how to use it" guide for the Radius Scan tab.

For implementation details, formulas, and API behavior, see:


What Radius Scan Is For

Radius Scan is the fast flip scanner:

  1. Buy from sell orders in your buy radius.
  2. Haul.
  3. Sell into buy orders in your sell radius.

Best for:

  • active hauling,
  • quick liquidity checks,
  • route-level batch planning.

If you want same-station maker trading, use Station Trading. If you want destination marketplace day-trader flow, use Regional Trade.


Before Your First Scan

Checklist:

  1. Set anchor system_name.
  2. Set realistic cargo_capacity.
  3. Start with high-sec route security (min_route_security = 0.45).
  4. Keep filters broad first.
  5. Run one scan, then tighten.

2-Minute First Setup

Use this baseline:

  1. Open Flipper (Radius) tab.
  2. Set:
    • system_name = Jita
    • cargo_capacity = 5000
    • buy_radius = 5
    • sell_radius = 10
    • min_margin = 5
    • min_route_security = 0.45
    • min_daily_volume = 0
    • max_investment = 0
  3. Keep structures off for first run (include_structures = false).
  4. Click Scan.
  5. Sort by RealProfit or ProfitPerJump.

Core Controls Explained

Buy vs Sell radius

  • buy_radius:
    • where tool searches source sell orders (where you buy)
  • sell_radius:
    • where tool searches destination buy orders (where you sell)

Practical pattern:

  • smaller buy radius + larger sell radius often gives cleaner results.

Route security

  • min_route_security = 0: all space
  • 0.45: high-sec routes only (recommended baseline)
  • 0.5, 0.7: stricter safety

Profit and liquidity filters

  • min_margin
  • min_daily_volume
  • max_investment
  • min_s2b_per_day
  • min_bfs_per_day
  • min_s2b_bfs_ratio
  • max_s2b_bfs_ratio

How To Read Rows Correctly

Use these fields in order:

  1. RealProfit: depth-aware expected ISK for executable qty.
  2. FilledQty and CanFill: how much can actually execute now.
  3. RealMarginPercent: execution-aware margin.
  4. ProfitPerJump: route efficiency.
  5. S2BPerDay, BfSPerDay, DailyProfit: throughput realism.
  6. SlippageBuyPct, SlippageSellPct: depth risk.

Important:

  • TotalProfit can be optimistic.
  • prefer RealProfit + FilledQty for real execution decisions.

Example Configs

Example A: Safe high-sec flipper

Goal: stable and safer hauling.

Settings:

  • buy_radius = 5
  • sell_radius = 10
  • min_margin = 8
  • min_route_security = 0.45
  • min_daily_volume = 5

Example B: Capital-controlled scan

Goal: avoid oversized expensive rows.

Settings:

  • max_investment = 1_000_000_000
  • keep cargo realistic to your ship/freighter
  • increase min_margin to cut weak rows

Example C: Aggressive discovery

Goal: maximum idea generation.

Settings:

  • min_route_security = 0
  • buy_radius = 15
  • sell_radius = 20
  • min_margin = 2
  • then manually vet RealMarginPercent, slippage, and jumps

Batch Builder (Route Fill)

Right-click a row -> Build batch.

What it does:

  • takes same route (same buy/sell path),
  • picks additional rows,
  • fills cargo using best ISK/m3 density first,
  • outputs total volume, profit, capital, and copyable manifest.

Use it when one good row does not fill your cargo.


Structures in Radius Scan

Enable Include Structures when:

  • logged in via ESI,
  • you want structure orders included.

Notes:

  • private structure visibility depends on access/token.
  • unresolved structure names can be skipped from results.
  • if testing parity, compare NPC-only first, then add structures.

Common Issues and Fixes

"Only few rows, looks empty"

Check:

  1. min_margin too high?
  2. route security too strict?
  3. buy/sell radii too small?
  4. max_investment and cargo caps too low?

"Looks profitable but actual qty is tiny"

This is usually depth/slippage reality.

Action:

  • review FilledQty, CanFill, RealProfit, slippage columns.
  • ignore rows with weak executable quantity.

"Cache stale warning"

Normal around ESI cache boundaries.

Use:

  • auto-refresh, or
  • reboot cache + rescan.

"I get same stations repeatedly"

Expected in hub-centric environments.

Action:

  • widen buy/sell radii,
  • adjust route security,
  • use blacklist for systems you never want.

Recommended Workflow

  1. Run safe baseline scan.
  2. Sort by RealProfit.
  3. Open top rows in execution planner.
  4. Build batch for best route.
  5. Save preset once settings stabilize.
  6. Enable auto-refresh while actively trading.

Related Pages

🚀 Start Here

📈 Trading Modules

🏭 Industry

🧭 Guides

👤 Character & Corp

🧠 Advanced

🛠️ Development

🔗 Links

Clone this wiki locally