TRAVIAN PANEL
Discovered coordinates, available troops and confirmed dispatches mean different things. Learn to read the counts, identify the current stage and decide what to check.
Updated: 4 October 2026 · Android 248 / extension 310 behavior
01
Illustrative example · Not live game data
Distinct oasis positions within the search area, including those without animals.
Positions checked for animals and losses. This is not a count of attacks sent.
Unknown until current animals, troops and loss limits have been verified.
Increasing the radius from 20 to 30 makes the geometric search area about 2.25 times larger. Oasis counts and duration need not grow at the same rate: distribution, occupied oases and response times vary. Check the radius for the specific village and troop type.
Coordinates from a complete, error-free discovery are stored on the device for 6 hours. The next search after expiry discovers the map again; newly unoccupied oases may then be found. Records are scoped to village, center, account, world and radius. Phone and computer have separate storage. Animals, ready troops and pre-dispatch checks are always verified again.
02
Use valid stored positions or discover the map. A growing count may mean discovery is still running.
Check current animals and simulations for the selected troop type. Finding one eligible target does not immediately send an attack.
Split dispatch separately evaluates smaller forces. Preparation may continue after the scan finishes.
Troops, target and outgoing movements are checked again. Success is shown only for a verified dispatch result.
03
Try the upper bound based on troop numbers only. Examples use one troop type; this calculator does not connect to your game or send orders.
Enter a whole number from 0 to 1,000,000 in every field.
The minimum is not met, or no unreserved troops remain.
A minimum of 0 removes the count threshold. A group still needs at least 1 troop.
Example: 110 ready − 0 kept − 0 reserved = 110 available. With a minimum of 50, the numeric upper bound is 2 groups of 55 + 55. JavaScript is needed to change the fields.
This result is not a dispatch plan. Enough distinct eligible oases must exist. Loss, animal permission and reward checks may lead to fewer groups or no dispatch. Lowering the minimum does not create safe targets.
04
Read the available count for the selected troop type, not the village total. For example, 55 troops − 10 kept = 45; that is below a minimum of 50. Another village or unit can have a different minimum.
Read the latest action time and stage. Group calculation progress is separate from map scanning. Loss calculations may be needed for several group sizes. A target verified empty during group preparation is skipped while other candidates continue.
First check which device is executing the task. The extension may show the phone's status when the phone is running it. On that device, use Open Game to check that the village and resources load, and check the connection and login.
This does not prove that the order was not received. Before clicking again, check the action time, log result and outgoing troops in the game. Repeated clicks do not resolve the uncertainty.
Preparation or simulation progress is not proof of dispatch. Read the time and confirmed troop/group count in the result for that village and troop type; compare with outgoing game movements if needed.
Disabling or stopping cancels preparation; it does not recall troops already travelling. Another device taking priority can also stop the task. Read the village, time and explanation together.