Strategy guide

Catching fleets on return in OGame: how to time the hit with the phalanx

A fleet returning to its planet sits still for a few seconds, and anyone with a phalanx knows exactly when. Here is the full method: what you can see, how to work out the flight, how much margin to leave and what the defender will do to make you miss.

Updated

The idea in one sentence

A fleet in flight cannot be attacked, but once it lands it is a target again. If you know the exact second it lands and your fleet arrives just after, the defender has no time to send it away again.

This guide is the other side of the fleetsave guide in this same section: that one explains how to hide a fleet; this one, how to find the fleet that is not well hidden. Reading both helps on both sides: the gaps you look for are the ones others will look for in you.

Before you start: rules and cost

  • Attack limit: under the official rules you may not attack the same planet or moon of an active player more than 6 times in 24 hours, except during an announced alliance war. Attacks with fleets that are wiped out also count. Some universes change this limit: check yours.
  • No scripts: since July 2025 the rules ban any program acting as an interface between you and the game. Working out times with a calculator is fine; a program that scans or sends fleets for you is not.
  • The cost: every phalanx scan uses 5,000 deuterium from the moon you scan from. Following a fleet with several scans is expensive, so it pays off against big fleets, not a couple of cargo ships.
  • The risk: while your fleet flies to the target, your own home is empty. A hunter can be hunted too.

How to see a returning fleet

The sensor phalanx is a moon building. It scans a planet (never a moon) and shows the fleets heading to it or leaving it, with their arrival time. The scanned player gets no warning.

Phalanx range

Range is level² − 1 systems on each side, in your galaxy only. According to the community wiki, the Discoverer class gets 20% more.

LevelSystems on each side
23
415
524
635
748
863

What it sees and what it misses

  • Scanning the origin planet shows the fleets returning to it from any mission (attack, transport, harvest, expedition), with their return time.
  • Scanning the destination planet shows the fleets heading to it: attacks, transports, deployments and alliance defence.
  • It misses anything leaving a moon or going to a moon, and a cancelled deployment: it disappears as soon as it is cancelled.
  • Composition: community sources disagree on whether you can see which ships a returning fleet carries. Do not rely on it: spy the planet to know what you will meet.

The quick rule: you only catch what returns to a planet. A player who fleetsaves moon to moon cannot be seen with the phalanx; for them you need other clues (spying the moon, debris fields that vanish, activity times).

Working out the impact time

Distance

  • Another galaxy: 20,000 × galaxy difference.
  • Another system in the same galaxy: 2,700 + 95 × system difference.
  • Same system: 1,000 + 5 × position difference.
  • Planet to its own moon or debris: 5.

Flight duration

The formula used by the wiki and the simulators is:

duration (s) = (35,000 ÷ speed × √(10 × distance ÷ slowest ship) + 10) ÷ universe fleet speed

Here "speed" is the send setting in tenths: 10 for 100%, 9 for 90%… down to 1 for 10%. "Slowest ship" is the real speed of your slowest ship, with drives, class and lifeforms included. The result is rounded to the second. Use the formula to plan, but the arrival time the game shows you when sending is the one that counts.

Return time

  • A fleet that attacked, transported or harvested comes back in the same time it took to go: return = departure + 2 × outbound.
  • A recalled fleet comes back in the time it had already flown: return = recall time + (recall − departure). Whether rounding adds one second is not confirmed: allow ±1 s.

Hitting the landing

How many seconds of margin

Your fleet must arrive after the landing, never before: if you arrive first you hit an empty planet and the fleet lands behind you. Gameforge does not explain what happens when both events fall on the same second, so nobody serious bets on that second. Hunter guides recommend 1 to 5 seconds after; start with 3.

The later you arrive, the more time the defender has to send the fleet out again. Arrive 30 or 60 seconds late and you will usually find an empty planet.

Blind phalanx

Sometimes the fleet has no return time because it is deployed and the defender recalls it. Since a cancelled deployment disappears from the phalanx, the hunter scans often and notes when it vanished. With the departure and recall times the return follows from the rule above.

It is the most expensive technique (every scan costs 5,000 deuterium) and the least precise: the error is the time between two scans. It only pays off against huge fleets.

What the defender will do

A good defender knows all of the above and plays against you:

  • Send again as soon as it lands. If they are online, one click is enough. That is why seconds matter.
  • Recall at the last minute to change the return time after you have launched.
  • Land on the moon, where the phalanx sees nothing, and jump through the jump gate to another moon: a jump is not a flight and, according to the community, does not show on the phalanx.
  • Flood the phalanx with fleets. The official rules let them send many fleets to their own planet, also from two friends or allies (up to 80 fleets in total, telling support), so you cannot tell which one matters.
  • Ninja: they see your attack in their event list, gather fleet or allies and destroy you on arrival. Always spy first and simulate the battle with margin.

Delaying your own fleet

Often your flight is shorter than the time left and you just leave later. But if you need to tune the exact second:

  • Lower the send speed in 10% steps (the General, in 5% steps).
  • Bring a slower ship: the slowest ship sets the pace for the whole fleet.
  • Alliance attack (ACS): a fleet joining can delay the group by up to 30% of its flight time; sources do not say whether of the remaining or the total time. It is used to fine-tune a few seconds.

Worked example

Made-up data: universe with fleet speed ×2. Your planet is at 2:140:5 and the target at 2:150:8. Your slowest ship flies at 15,000. The phalanx shows an enemy fleet that lands at 03:14:22.

Step 1: distance

Different systems in the same galaxy: 2,700 + 95 × 10 = 3,650.

Step 2: duration

√(10 × 3,650 ÷ 15,000) = √2.433 ≈ 1.560.

SpeedCalculationDuration
100%(3,500 × 1.560 + 10) ÷ 245:35
90%(3,889 × 1.560 + 10) ÷ 250:38
50%(7,000 × 1.560 + 10) ÷ 21:31:05
30%(11,667 × 1.560 + 10) ÷ 22:31:45

Step 3: departure time

You want to arrive at 03:14:22 + 3 s = 03:14:25. At 100%: 03:14:25 − 45:35 = 02:28:50. Scan again just before launching to confirm the time has not changed, and check on the send screen that the arrival the game shows is 03:14:25.

Variant: the fleet is recalled

Another fleet left at 20:00:00 and vanishes from the phalanx at 23:10:05. It had flown 3:10:05, so it comes back at 23:10:05 + 3:10:05 = 02:20:10. Aim for 02:20:13 and, since you only know the recall time within the gap between scans, expect to miss sometimes.

Common mistakes

  1. Arriving before the fleet. You hit an empty planet. Always a few seconds after.
  2. Trusting an old scan. The defender may have recalled or changed plans: scan before launching.
  3. Chasing a moon-to-moon fleetsave. The phalanx cannot see it; you burn deuterium for nothing.
  4. Not spying. Without a spy report you do not know whether a bigger fleet or a crushing defence is waiting.
  5. Forgetting the ninja. If the defender sees you coming, they can wait for you with allies.
  6. Calculating by hand and not checking the game. The game's arrival time accounts for everything your calculation may miss.
  7. Going over the attack limit. The seventh attack in 24 hours on the same planet or moon is a breach, except in war.
  8. Leaving your home empty and visible. While you hunt, others can hunt you.

Depends on your universe

  • Fleet speed: every universe has its own, sometimes different for peaceful, war and holding missions. It changes every time.
  • Alliance attacks: may be disabled.
  • Attack limit: 6 by default, but some universes change it or have none.
  • Circular galaxies: if the universe has them, the distance between the edges is shorter.
  • Project Orion: the new missions are only active in universes opened since 6 November 2026. There is no official information on how they show on the phalanx.

How Orbit helps

  • The flight simulator works out the duration with your drives, your class and your universe speeds, and backwards: give it the impact time and it tells you when to leave. See the calculators manual.
  • In the chat, Catch on return works out when an observed fleet returns at every possible speed and when to leave to arrive just after.
  • The player scanner shows observed activity by time slot, useful to know when your target is usually offline. See the intelligence manual.

Sources