Telegram RegisterThe public register of Telegram
Telegram profile photo for TornadoCashAlerts

Channel

TornadoCashAlerts

@TornadoAlerts

On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

829subscribers

+185 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-1001876735722
TypeChannel
Username@TornadoAlerts
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/TornadoAlerts

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 86% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

6438297367 August 2026 — 644 subscribers8 August 2026 — 644 subscribers8 August 2026 — 643 subscribers15 August 2026 — 656 subscribers24 August 2026 — 661 subscribers31 August 2026 — 676 subscribers9 September 2026 — 692 subscribers18 September 2026 — 829 subscribers7 August 202618 September 2026
8 measurements spanning 42 days, net +185. 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 615–857 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 13:40829+137
9 Sept 2026, 17:01692+16
31 Aug 2026, 14:32676+15
24 Aug 2026, 07:33661+5
15 Aug 2026, 16:45656+13
8 Aug 2026, 08:17643-1
8 Aug 2026, 02:47644no change
7 Aug 2026, 11:41644first reading

Engagement

20 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 01:53 UTC6 viewsread 8 August 2026

amount: 0.1 ETH relayer: #torntool.eth locked: 8545.3686 TORN fee: 0.0021 ETH toStakers: 0 TORN time: 2026-08-08 09:52:59 UTC+8 etherscan: tx hash

8 Aug 2026, 01:46 UTC6 viewsread 8 August 2026

amount: 1.0 ETH relayer: #torntool.eth locked: 8545.3686 TORN fee: 0.0057 ETH toStakers: 0.9960 TORN time: 2026-08-08 09:46:35 UTC+8 etherscan: tx hash

8 Aug 2026, 01:23 UTC8 viewsread 8 August 2026

amount: 1.0 ETH relayer: #sky-relayer.eth locked: 12224.9072 TORN fee: 0.0060 ETH toStakers: 0.9960 TORN time: 2026-08-08 09:23:35 UTC+8 etherscan: tx hash

8 Aug 2026, 00:32 UTC13 viewsread 8 August 2026

amount: 0.1 ETH relayer: #00relayer.eth locked: 10389.7143 TORN fee: 0.0017 ETH toStakers: 0 TORN time: 2026-08-08 08:32:35 UTC+8 etherscan: tx hash

8 Aug 2026, 00:32 UTC9 viewsread 8 August 2026

amount: 1.0 ETH relayer: #solid-relayer.eth locked: 4442.0414 TORN fee: 0.0055 ETH toStakers: 0.9960 TORN time: 2026-08-08 08:31:59 UTC+8 etherscan: tx hash

8 Aug 2026, 00:31 UTC7 viewsread 8 August 2026

amount: 1.0 ETH relayer: #solid-relayer.eth locked: 4443.0374 TORN fee: 0.0055 ETH toStakers: 0.9960 TORN time: 2026-08-08 08:30:59 UTC+8 etherscan: tx hash

8 Aug 2026, 00:30 UTC8 viewsread 8 August 2026

amount: 1.0 ETH relayer: #solid-relayer.eth locked: 4444.0334 TORN fee: 0.0055 ETH toStakers: 0.9960 TORN time: 2026-08-08 08:29:59 UTC+8 etherscan: tx hash

8 Aug 2026, 00:25 UTC9 viewsread 8 August 2026

amount: 1.0 ETH relayer: #reltor.eth locked: 32353.1514 TORN fee: 0.0060 ETH toStakers: 0.9960 TORN time: 2026-08-08 08:24:47 UTC+8 etherscan: tx hash

8 Aug 2026, 00:18 UTC10 viewsread 8 August 2026

amount: 10.0 ETH relayer: #00relayer.eth locked: 10389.7143 TORN fee: 0.0377 ETH toStakers: 9.9647 TORN time: 2026-08-08 08:18:35 UTC+8 etherscan: tx hash

8 Aug 2026, 00:12 UTC10 viewsread 8 August 2026

amount: 10.0 ETH relayer: #s-relayer.eth locked: 5403.9669 TORN fee: 0.0437 ETH toStakers: 9.9647 TORN time: 2026-08-08 08:12:11 UTC+8 etherscan: tx hash

8 Aug 2026, 00:02 UTC10 viewsread 8 August 2026

amount: 10.0 ETH relayer: #00relayer.eth locked: 10399.6790 TORN fee: 0.0377 ETH toStakers: 9.9647 TORN time: 2026-08-08 08:01:47 UTC+8 etherscan: tx hash

7 Aug 2026, 23:50 UTC9 viewsread 8 August 2026

amount: 10.0 ETH relayer: #torntool.eth locked: 8546.3645 TORN fee: 0.0417 ETH toStakers: 9.9647 TORN time: 2026-08-08 07:50:35 UTC+8 etherscan: tx hash

Showing the 12 most recent of 20 posts we hold for @TornadoAlerts. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

币安公告
@binance_cn · 34,060
Telegram ranks this channel #80 of 84 here — alongside 83 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“TornadoCashAlerts” (@TornadoAlerts), 829 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/TornadoAlerts.

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.