Fleet saving — sending your ships on a timed mission so they are never home when a predator lands — is the single highest-leverage skill in OGame. Build the wrong ships and you lose resources; ignore fleet save for one night and you lose everything you spent the last month building. This guide covers every mission type available, how to calculate your return window, how to keep deuterium costs sane, and the recurring mistakes that turn veteran players into crash statistics.
Why Fleets Die at Home
In OGame every fleet on a planet or moon is a static target. The moment your ships sit idle, any player with a spy probe and an active phalanx can see exactly how long they stay there. Crash windows are not random — they are calculated. An attacker will scan your planet, note your fleet return time, and time their battle ships to arrive in the same second your mission lands. You never see it coming because you are asleep, at work, or simply not watching the galaxy screen.
The math is brutally simple. A large fleet represents millions or even billions of units of resources. Those resources translate into deuterium, time, and ranking points for the attacker. Your fleet is the most valuable thing on the server, and dedicated raiders check active planets multiple times per hour precisely because the payoff is so high.
Speed universes make the problem worse and better at the same time. Worse because ships build fast, so competition is fierce and attack fleets form quickly. Better because — as we will cover — short fleet save missions become viable when travel times collapse to minutes. On OGames' Proxima universe running at 200x fleet speed, a round-trip that would take twelve hours on a 1x server can complete in minutes, giving you windows you can actually monitor.
The core principle: your fleet must never be home when you cannot actively defend it. Internalize that rule before you read anything else.
Fleet Save Mission Options
Not every mission is created equal for fleet saving purposes. Each has different fuel costs, timing characteristics, and risk profiles. Here is how experienced players evaluate them.
Deploy
Deploying to another planet or moon you own is the most fuel-efficient save because the ships stop there. The downside: they are now a static target on a different coordinate. Only use deploy saves when the destination is a moon — moons cannot be phalanxed, meaning an attacker cannot confirm your fleet is there without guessing. Never deploy to a planet if you are worried about being scanned.
Transport
Sending a transport mission to an ally's moon is a classic save method. Your fleet is in flight, unhittable, returning at a precise time you control. The risk is trusting your ally completely — if they are offline or their account is compromised, your fleet lands and sits exposed. Only run this with players you have known for a long time, and make sure they are online when your fleet returns.
Colonize (Dummy Colony)
Sending a Colony Ship to an empty slot performs a round trip of the longest possible duration automatically if the slot is already colonized and the mission bounces. Some players exploit this for extended saves. In practice, true colonize saves require an actual empty slot, which you burn when you use it. Treat this as a situational tool, not a routine save method.
Expedition
Expedition missions travel to position 16 of a chosen solar system and return after a fixed delay with random rewards — resources, dark matter, ships, or nothing. Because position 16 cannot be phalanxed, your fleet is completely invisible during the trip. Expedition saves are ideal for medium-duration windows. The fuel cost scales with the distance to system 16, so choose nearby systems to save deuterium. The bonus is that you might actually gain resources or ships while saving. See the expedition speed servers guide for optimizing what you send.
Recycle (Debris Field)
Sending recyclers to harvest a debris field keeps them in flight. If you aim at a debris field that will regenerate or at a non-existent field, the recyclers return empty. It is a clean save for recyclers specifically. Do not use it for your combat fleet — recyclers alone are not worth protecting with this level of attention.
Holding (ACS Defend)
The ACS Defend / Hold mission lets you park a fleet at a friendly player's moon for up to 99 hours. This is the gold standard long save. Your fleet is invisible to phalanx on a moon you do not own, and it returns at a precise future time. It costs deuterium for the initial flight but nothing during the hold period. Build relationships with trusted alliance members specifically for this purpose.
Timing Your Return
Timing is everything. A fleet that returns at 03:00 local time while you are asleep might as well not be saved at all — you gain nothing if you cannot be at your screen the moment it lands.
The golden rule is return to an active window: a period of at least 30–60 minutes where you will be watching the game. If you eat lunch at 12:30 every day, return at 12:35. If you play intensively from 20:00 to 22:00, return at 20:05. Never return in the middle of an 8-hour sleep window.
Calculating Return Time
OGame displays the exact timestamp of your fleet's return in the fleet movement screen. Work backwards from when you want to be online and choose a mission duration that hits that window. On high-speed universes the granularity is seconds — you can typically return within a two-minute window of your target time by adjusting the destination distance.
A practical technique: set your fleet save so the return lands at least 15 minutes after you normally log in, not at exactly the moment. If your session starts at 20:00 and your return is at 20:02, a brief delay getting to your keyboard could mean your fleet sits unattended for several minutes — enough for a pre-staged attacker to land.
The Ninja Window Problem
Sophisticated attackers watch fleet return times and stage their attack fleet to arrive in the same second. This is called a ninja attack from the defender's perspective. Your best counter: keep your return time secret. Do not announce it in alliance chat, do not let it appear in a predictable pattern, and consider using a moon (which is phalanx-immune) as your save destination so the attacker cannot confirm your fleet's location to begin with. For the offensive ninja technique, the ninja defense guide covers the mechanics from both sides.
Speed Universe Timing on OGames
On Andromeda (50x fleet speed), a flight to a galaxy-8 target that would take six hours on a 1x server takes roughly seven minutes. On Proxima (200x), that same trip collapses to under two minutes. This means you can run what are effectively micro-saves — deploying your fleet on a short expedition or transport and returning before the next human can react and launch. It also means mistakes propagate at the same speed: if you miscalculate your return, an attacker who notices can launch and land before you have time to correct course. Speed rewards prepared players who already have save routines built; it punishes reactive ones who try to improvise.
Deuterium Cost of Safety
Fleet saving burns deuterium. On a 1x server with a large fleet, daily save costs can exceed a planet's entire deuterium production, making it the single largest resource sink in an active account. On speed servers the absolute fuel amounts are lower per trip — shorter times mean shorter distances — but you may save more frequently, which adds up.
The core formula: deuterium cost = ship fuel consumption × distance × (2 for round trip) × speed factor. Every ship class has a base fuel consumption stat. Large Cargos, Battle Cruisers, and Destroyers are the most expensive ships per unit to fly. Light fighters and Cruisers are more economical per unit of combat power saved.
Optimizing Fuel Costs
- Fly at minimum speed (10%). Halving speed roughly cuts fuel consumption by 75%. The trade-off is longer flight time — often desirable anyway because a longer save window gives you more flexibility.
- Use nearby destinations. Fuel cost scales with distance. A system 30 galaxies away costs dramatically more than one 3 galaxies away. Keep a list of trusted ally moons in nearby systems specifically for holds and transports.
- Expedition to system 1. If you are in galaxy 1, expedition to system 16 in your own galaxy costs almost nothing compared to cross-galaxy trips.
- Consolidate your fleet. Splitting saves across multiple destinations multiplies fuel costs. Fly everything together whenever possible unless you need separate timing windows for different ship groups.
On OGames, deuterium production scales with universe speed. In Nebula (99x economy) your synthesizers run at nearly 100x a standard server's output, which means absolute save costs — while higher in raw numbers — represent a smaller fraction of your income. In Proxima (200x), passive deuterium income is so high that fuel cost is almost never the constraint on saving frequency. This is one of the hidden advantages of high-speed universes that new players often underestimate when comparing them to slower environments. See the server comparison page for exact speed multipliers.
FS Mistakes That Get You Crashed
Every crash story in OGame follows a recognizable pattern. The fleet was big, the save routine was almost right, and then one edge case appeared that the player had not prepared for. Here are the mistakes that veteran players make — once.
The "Just This Once" Overnight Gamble
You are tired. The fleet is on the planet. You tell yourself the server is quiet tonight and you will be fine. This is statistically the most common cause of large crashes. Attackers specifically hunt during low-activity hours precisely because defenders drop their guard. There is no such thing as a safe night to leave your fleet home. Save. Every. Night.
Forgetting to Re-launch After Landing
Your fleet returns at 08:00. You log in, collect the resources, intend to re-launch immediately, and then get pulled away for twenty minutes. In a high-activity universe, twenty minutes is more than enough for a scan-and-launch sequence. Build the habit of re-launching before you do anything else when a fleet lands.
Saving to a Planet Instead of a Moon
A deploy save to a planet is a phalanx-visible target. Any player with a phalanx can see your fleet sitting there and calculate the landing window. Always save to moons. If you do not have a moon at the target coordinate, either build one or use a different save type. The moon shot guide explains how to get moons efficiently.
Predictable Save Patterns
Returning at exactly 22:00 every night for two weeks tells every active watcher on the server that your fleet lands at 22:00. Rotate your return times. Vary destinations. Make your pattern invisible. Dedicated raiders keep notes on target habits — do not give them the data.
Trusting the Wrong Ally
Holds and transports require trust. A falling-out with an ally, an account ban, or a compromised password means your fleet lands somewhere you cannot protect it. Always have a backup save option that does not depend on another player. Expedition saves and self-owned moon deploys should be your primary methods; ally holds are supplements.
Saving With Full Cargo Holds
A fleet carrying 500 million resources in its cargo is not just a ship loss risk — it is a resource loss risk too. Before saving, either spend resources on buildings, research, or defenses, or deploy them to a moon storage. Attackers calculate total loot including cargo; a fully loaded save is a prime target if the attacker somehow intercepts the return.
Ignoring the Phalanx Threat
If you save to coordinates that can be phalanxed and your destination is known, a patient attacker with phalanx can watch your fleet appear in transit and calculate the return time with precision. Phalanx-immune saves (expedition to position 16, holds on another player's moon, or your own moon where your fleet is invisible) eliminate this entire attack vector. Read the phalanx guide to understand exactly what is visible and what is not.
FS on Fast Universes: Minutes Matter
Everything changes at high fleet speed multipliers. On a 1x server, fleet save is a twice-daily ritual with hour-long windows. On Proxima at 200x, a save might last twelve minutes. That compression cuts both ways.
The advantage: you can respond to threats in real time. If you see a hostile fleet in your galaxy screen, you can launch and be safely in flight before they cross two solar systems. You can also correct mistakes — a save that returns at the wrong time can be re-launched before the attacker lands, because the windows are short enough for human reaction.
The disadvantage: the discipline required is higher, not lower. A twelve-minute save window means your fleet lands every twelve minutes, and every landing is an exposure. You need either a near-continuous save loop (possible on very fast universes where you can chain expedition saves while online) or a long hold on a trusted moon.
The Continuous Save Loop
On Proxima-speed universes some players maintain what is effectively a permanent save: they chain expedition missions back-to-back, each one returning just as they launch the next. The fleet is almost never home. Fuel costs are high but manageable given 200x deuterium production. This is the logical endpoint of fleet save discipline in a fast environment — and it explains why the most durable accounts on high-speed servers are not the players with the biggest fleets, but the ones with the tightest routines.
Attack Windows Collapse
On Andromeda (50x fleet speed), a cross-galaxy attack that takes 4+ hours on standard universes takes around five minutes. This means hostile fleets can materialize from across the server with almost no warning time. The practical implication: you cannot rely on watching the galaxy screen and reacting. Your fleet needs to already be safe before the threat appears, not after.
New players on OGames speed universes sometimes feel paranoid about saving every session. Veterans will tell you the paranoia is correct. Speed compresses both your build time and your vulnerability windows. The players who reach the top of the rankings on OGames universes without losing their fleet are not the luckiest ones — they are the ones who built save routines on day one and never broke them.
FAQ
What is the safest fleet save mission type in OGame?
A hold mission (ACS Defend) on a trusted ally's moon is the gold standard for long saves — your fleet is in flight, invisible to phalanx, and returns at a predictable time you control. For medium saves, expedition missions to position 16 of a nearby solar system are nearly as safe because position 16 cannot be phalanxed. Avoid saving to planets at any time, as planets are always phalanx-visible.
How do I calculate the right save duration?
Work backward from when you will be online and alert. Your fleet should return 10–20 minutes after you expect to log in, not before. If you sleep 8 hours, your save must last at least 8.5 hours to cover the full offline window plus reaction time. Use the fleet movement screen's timestamp display to fine-tune the duration by adjusting the destination distance or flight speed.
Does flying slower really save that much deuterium?
Yes, significantly. OGame's fuel formula makes speed reduction extremely efficient. Flying at 50% speed roughly cuts fuel consumption by around 50%; flying at 10% speed cuts it by roughly 75–80% compared to full speed. For a large fleet this is the difference between spending half your daily deuterium production on a single save versus a fraction of it. Slower speeds also extend your save duration, which is often what you want.
Can I be crashed while my fleet is on an expedition?
Not directly — a fleet in flight cannot be attacked. However, your fleet can be crashed when it returns if an attacker has calculated your return time. Expedition missions to position 16 cannot be phalanxed, so the attacker would need to guess your return time rather than observe it. This makes expedition saves significantly safer than saves to phalanx-visible coordinates. Never announce your return time in public channels.
How often should I fleet save on OGames speed universes?
Every time you leave the keyboard for more than a few minutes and cannot watch your fleet movement screen. On Andromeda (50x) and Nebula (99x), this effectively means every gaming session end and every time you step away. On Proxima (200x), active players often maintain near-continuous expedition save chains while online and use long holds on ally moons for offline periods. The correct frequency is: whenever your fleet would otherwise be sitting unattended on a planet or unprotected moon.
Fleet saving is not optional in OGame — it is the skill that separates players who grow steadily from players who restart from scratch every few weeks. If you want to compete in an environment where your fleet is actually protected by high debris rates and generous dark matter rewards, register on OGames and start building your save routine from day one.