Telegram RegisterThe public register of Telegram
Telegram profile photo for @feuturespda_bot

Channel

@feuturespda_bot

@futurespda498

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

2subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001654316313
TypeChannel
Username@futurespda498
Description@feuturespda_bot
CreatedBetween 1 December 2021 and 25 July 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/futurespda498

Growth

27 August 2026 — 2 subscribers13 August 2026 — 2 subscribers7 August 202613 August 2026
2 measurements spanning 7 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 21:032no change
7 Aug 2026, 07:232first reading

Engagement

20 posts held, back to 25 July 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 26 July 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
69
Links
162

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

26 Jul 2022, 12:53 UTC21 viewsread 13 August 2026

👨‍🚀 Автор готов обсудить свой сигнал по #AAVEUSDT.

26 Jul 2022, 12:01 UTC21 viewsread 13 August 2026

26.07 в 17:00 (МСК) на YouTube-канале CScalp TV выходит обучающее видео: "+20% Пробой наклонного уровня. Разбор скальперских сделок" В видео трейдер разберет несколько сделок. Ситуации: пробой наклонных и горизонтальных уровней. Основания: раскорреляция с BTC, активность в стакане, объемы, уровни. Идеи для сделок трейдер брал в канале Trader signals. Хотите научиться отрабатывать сигналы? Смотрите обучающее видео зд

26 Jul 2022, 10:50 UTC20 viewsread 13 August 2026
Photo

SHORT #AUDIOUSDT from $0.3065 stop loss $0.31 30m TF. На монете появился участник на что указывают повышенные объёмы + в прошлом монета очень импульсно шла вниз. Образовались 2 чётких минимума на пробой которых и стоит входить с целью на импульс Автор: BREIDO Trade #ПробойУровня

26 Jul 2022, 10:50 UTC21 viewsread 13 August 2026

👨‍🚀 Автор готов обсудить свой сигнал по #AUDIOUSDT.

26 Jul 2022, 10:24 UTC15 viewsread 13 August 2026

👨‍🚀 Автор готов обсудить свой сигнал по #BATUSDT.

26 Jul 2022, 09:14 UTC14 viewsread 13 August 2026
Photo

SHORT #BTSUSDT from $0.0105 stop loss $0.0107 15m TF. Монета впервые будет ретестить свой недавно пробитый уровень, на отметке 0.01063 стоит плотность, от которой ожидаю реакцию в шорт Сигналы МосБиржи здесь. #ОтскокОтУровня

26 Jul 2022, 09:14 UTC15 viewsread 13 August 2026

👨‍🚀 Автор готов обсудить свой сигнал по #BTSUSDT.

26 Jul 2022, 08:04 UTC14 viewsread 13 August 2026
Photo

SHORT #BTCUSDT from $20 750 stop loss $21 500 4h TF. Ситуация на обновление минимума + слом трендовой линии. В связи с ростом доминации BTC и явным упадком объемов, стоит ожидать плавное закругление цены вниз. Автор: Market Situations #ПробойУровня

26 Jul 2022, 08:04 UTC14 viewsread 13 August 2026

👨‍🚀 Автор готов обсудить свой сигнал по #BTCUSDT.

26 Jul 2022, 08:02 UTC12 viewsread 13 August 2026

👨‍🚀 Автор готов обсудить свой сигнал по #BTCUSDT.

26 Jul 2022, 07:39 UTC11 viewsread 13 August 2026

👨‍🚀 Автор готов обсудить свой сигнал по #LEVERBUSD.

26 Jul 2022, 07:39 UTC11 viewsread 13 August 2026
Photo

SHORT #LEVERBUSD from $0.00267 stop loss $0.268 5m TF. Сформировался локальный уровень , рассматриваю на пробой в шорт. На графике инструмента видна явная сила продавца , ожидаю импульсный пробой с основной целью 0.002600$ Автор: Запильный Скальпинг #ПробойУровня

Showing the 12 most recent of 20 posts we hold for @futurespda498. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.

“@feuturespda_bot” (@futurespda498), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/futurespda498.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.