
Channel
π£π Mines RUSH - Signals π£π
@rushmineschannel
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
3,089subscribers
-199 since we began measuring on 12 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1002205893148 |
|---|---|
| Type | Channel |
| Username | @rushmineschannel |
| Created | Between 1 June 2024 and 30 September 2024 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/rushmineschannel |
Topic
Gambling & betting β 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 09:40 | 3,089 | -10 |
| 1 Nov 2026, 01:59 | 3,099 | -10 |
| 29 Oct 2026, 10:01 | 3,109 | -9 |
| 26 Oct 2026, 02:17 | 3,118 | -4 |
| 23 Oct 2026, 00:56 | 3,122 | -10 |
| 20 Oct 2026, 03:19 | 3,132 | -7 |
| 17 Oct 2026, 02:39 | 3,139 | -14 |
| 14 Oct 2026, 08:45 | 3,153 | -8 |
| 10 Oct 2026, 20:55 | 3,161 | -4 |
| 5 Oct 2026, 00:57 | 3,165 | -22 |
| 25 Sept 2026, 22:18 | 3,187 | -21 |
| 17 Sept 2026, 02:57 | 3,208 | -12 |
| 13 Sept 2026, 01:18 | 3,220 | -5 |
| 9 Sept 2026, 23:44 | 3,225 | no change |
| 9 Sept 2026, 00:19 | 3,225 | -24 |
| 3 Sept 2026, 12:58 | 3,249 | +1 |
| 31 Aug 2026, 15:23 | 3,248 | +1 |
| 28 Aug 2026, 08:17 | 3,247 | -11 |
| 25 Aug 2026, 14:04 | 3,258 | -18 |
| 22 Aug 2026, 16:53 | 3,276 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured β we do not publish a rate before we have the readings behind it.
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.
@notoriousmines Β· 32,636
Telegram ranks this channel #3 of 31 here β alongside 30 others β read 2 September 2026
@mines1winoriginal Β· 235,304
Telegram ranks this channel #8 of 54 here β alongside 53 others β read 12 August 2026
@aviator1winoriginal Β· 100,543
Telegram ranks this channel #23 of 56 here β alongside 55 others β read 19 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists 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 4 November 2026 β this entry's latest reading, not the date you are reading this.
βπ£π Mines RUSH - Signals π£πβ (@rushmineschannel), 3,089 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/rushmineschannel.
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.