Short answer: Across 1,523 MetaTrader 5 positions that AlgoVesta opened from Telegram signals for 40 customers between 18 August and 15 November 2026, the median time from the message reaching AlgoVesta to the position being open was 1.33 seconds. 81.0% took less than 2 seconds and 99.4% less than 5 seconds. On live broker servers the median was 1.44 seconds (708 positions, 25 customers).
To copy signals from a Telegram channel to MetaTrader 5 automatically, start with the Telegram to MT5 bridge.
Data window: 2026-08-18 to 2026-11-15 (90 days, measured on 2026-11-16). Source: AlgoVesta's own production database, queried read-only. Not measured: profit and loss. Data: download the CSV (CC BY 4.0).
Method and other studies: Research
What exactly did we time?
The clock starts when AlgoVesta's Telegram reader receives the channel message on behalf of the customer. It stops when AlgoVesta records the position as open after the MetaTrader 5 terminal confirms the order. In between, the message is read, matched to the customer's bot and settings, checked against their risk rules, sized, and sent to the MT5 terminal that AlgoVesta runs for that account.
- Included: every Telegram signal in the window that AlgoVesta executed on an MT5 account and that we could link to its position record.
- One position per signal. When a signal has several take-profit targets, AlgoVesta opens one position per target. We count the first one, so a signal with five targets is not counted five times.
- Not included: the time between the channel posting the message and Telegram delivering it to AlgoVesta. That part depends on Telegram and is not in these figures.
- Not included: signals that were not executed, for example because the customer's own rules filtered them. Those are covered in our 90-day signal study.
How long does it take?
| Group | Positions | Customers | Median | 90th percentile | 99th percentile | Under 2 s |
|---|---|---|---|---|---|---|
| All MT5 servers | 1,523 | 40 | 1.33 s | 2.58 s | 4.52 s | 81.0% |
| Live broker servers | 708 | 25 | 1.44 s | 2.39 s | 4.64 s | 78.7% |
| Demo servers | 815 | 20 | 1.01 s | 2.79 s | 4.39 s | 83.1% |
Half of all positions were open between 0.94 and 1.74 seconds after the message arrived (the 25th and 75th percentiles). Some customers trade on both live and demo servers, so the two customer counts add up to more than 40.
Live and demo servers are not a controlled comparison. They are different broker servers holding different customers' accounts, so we do not read the gap between the two medians as a property of live trading.
How are the times distributed?
| Time from message to open position | Positions | Share |
|---|---|---|
| Less than 1 second | 480 | 31.5% |
| 1 to 2 seconds | 754 | 49.5% |
| 2 to 3 seconds | 181 | 11.9% |
| 3 to 5 seconds | 99 | 6.5% |
| 5 seconds or more | 9 | 0.6% |
Each band includes its lower bound and excludes its upper bound. The full table, including the live and demo split, is in the CSV file.
How much of that is the MT5 order itself?
We also record the round-trip of the order command alone: from sending it to the MT5 terminal until the terminal confirms. Over 1,994 orders on live broker servers in the same window, that round-trip had a median of 1.26 seconds and a 90th percentile of 2.79 seconds. This figure covers orders from every signal source, not only Telegram, so it cannot be subtracted directly from the times above.
What about crypto exchanges?
For Telegram signals executed on Binance futures with live (mainnet) API keys, the median time from the message reaching AlgoVesta to the exchange's order confirmation was 8.07 seconds, with a 90th percentile of 15.87 seconds. This is a small sample: 79 orders from 8 customers, and none of them took less than 5 seconds. We have not yet broken down where those seconds are spent, and we publish the figure as measured rather than leaving it out. A further group of crypto orders whose API keys were later deleted came from fewer than five customers and is hidden.
Crypto orders run on a different path from MT5: they go through our order servers to the exchange's own API. How that path works is described in How AlgoVesta works.
How did we measure it?
- Source. AlgoVesta's production database: the Telegram decision log, which stores every message with the decision taken and the order it produced, joined to the MT5 and crypto trade records. Queries ran in a read-only database session that was rolled back at the end; nothing was written.
- Window. 2026-08-18 to 2026-11-15. The 90 days before had fewer than five customers in this measurement, so we do not publish a comparison with it.
- Exclusions. Our own hourly monitoring account, residue from test runs, banned accounts and deleted accounts are removed before anything is counted.
- Privacy. We publish aggregates only. Any group with fewer than five customers is hidden, and so is any band with one to four positions. No channel names, message contents or customer identifiers appear here.
- Percentiles. Percentiles use the nearest-rank method. No position had a negative time, so none was excluded for clock errors.
What are the limitations?
- The clock does not start at the channel. Time spent before Telegram delivers the message to AlgoVesta is not measured here.
- Server classification is by name. An MT5 server whose name contains "demo" is counted as demo; all others as live.
- Our customers, not the market. These are the brokers, instruments and channels our customers chose. Another set of customers could give different times.
- No performance data. A position that opens quickly is not a profitable position. We did not measure profit and loss.
Frequently asked questions
The bottom line
Over 90 days, a Telegram signal that AlgoVesta executed on MT5 was an open position a median 1.33 seconds after the message arrived, and 99.4% of positions were open within 5 seconds. The longer crypto times are published as measured. We will repeat this measurement so the series can be compared.
Disclaimer. AlgoVesta is signal-routing automation infrastructure (Bring Your Own Signal). It runs execution infrastructure on your behalf using trade-only credentials; it does not generate signals, hold, receive, or move client funds, and does not provide investment advice or trading recommendations. Times in this article are medians and percentiles for the stated window and may vary. Crypto and forex trading carry substantial risk of loss; leveraged positions may be fully liquidated. Past performance does not guarantee future results.
The authoritative version of this article is the English original; translations are provided for convenience.
Ready to automate your trading workflow?
Connect your exchange with secure, trade-only API keys.
Start Free — 7 DaysRelated comparisons: Cornix · TSCopier · TelegramFXCopier · Copygram · PineConnector