Travian Calculators

What it does

Tools provides Distance / Travel Time, Counter-Attack Timing, Troop Power / Upgrades, and Elephant Finder. The first three are browser calculations. Elephant Finder scans oases near coordinates through a running account session and reports elephant garrisons it finds.

How it works

Distance takes coordinates, map half-width 200, 250, or 400, tribe and troop or hero speed, server variant and speed, Tournament Square 0–20, and items. Slowest unit sets speed. Counter timing accepts attacker, defender, arrival second, optional solo-hero Map, counter village and troop, and margin, then shows SEND AT. Troop Power uses levels 0–20 for stats and T4.6 cost comparisons. Elephant Finder needs running account and radius 1–12, so it is slower than browser calculations.

The bot works in cycles, not finish-time alarms. A normal cycle sleeps for a random 60 to 180 seconds after all villages; the baseline uses 240 to 600 seconds. Between villages it waits 2 to 8 seconds, or 5 to 15 seconds in the baseline. Account settings reach a running bot immediately. Village settings have a five-minute cache, cleared when the Village Settings card is saved. Task edits are loaded after a complete village pass, so a change made while sleeping can take about two cycles to take effect. Refresh starts the next cycle sooner but does not itself reload tasks.

Each village pass reads current state first. Its economy order is Auto NPC, Auto Add Cropland, Auto Celebration, trade routes, settler training and sending, then build tasks. Earlier work can therefore delay later work. Displayed resources and queues are the last state read, not a promise of the next game state. Game automation carries risk; no setting guarantees a game result or eliminates account risk.

When reading results, separate a completed game action from a configured intention. A success log means the bot reached the relevant page and the action entered the expected game flow; it does not make later state permanent or exempt from game rules. A wait message usually preserves configuration for a later cycle. A temporary skip lets other eligible work be considered where queue logic allows it. A failed click can stop lower-priority building work for that pass because strict priority protects resources intended for earlier work. Review the game page as well as logs after important actions.

The bot does not wake exactly when construction finishes. It discovers a finished action during the next cycle, so a gap can be roughly a cycle plus per-village delay. The village list refreshes on periodic re-login, normally every 60 to 120 minutes and 120 to 240 minutes in the baseline, or after restart. A village founded while the bot runs is therefore not immediately processed. Configure clear priorities, avoid conflicting automation, and give one change time to appear before adding another.

Settings

Setup in 5 steps

1. Open Tools.

2. Choose calculator.

3. Enter coordinates, version, troop, and item data.

4. Compare result with game state.

5. For Elephant Finder, select a running account and modest radius.

Requirements

Limits and what it does not do

Common problems

A passed-window warning means recalculate a future arrival or margin. Different game timing usually means recheck server speed, map size, Square, troop, and items. Elephant Finder cannot scan without a running account; a slow scan is expected because it reads session data.

Related features

Second village and settlers · Auto building queue · Task types reference

Last updated: October 26, 2026