Channel
Электросталь | Новости | Слухи
@electrostal_sluh
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
16,248subscribers
-24 since we began measuring on 12 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001769282270 |
|---|---|
| Type | Channel |
| Username | @electrostal_sluh |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 5 times, most recently 31 October 2026 |
| On Telegram | t.me/electrostal_sluh |
Topic
Local community — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 27 Oct 2026, 01:55 | 16,248 | -1 |
| 24 Oct 2026, 07:16 | 16,249 | -1 |
| 23 Oct 2026, 04:16 | 16,250 | -2 |
| 22 Oct 2026, 02:49 | 16,252 | -1 |
| 20 Oct 2026, 21:55 | 16,253 | -1 |
| 18 Oct 2026, 20:08 | 16,254 | -1 |
| 16 Oct 2026, 18:20 | 16,255 | -1 |
| 15 Oct 2026, 17:46 | 16,256 | +1 |
| 13 Oct 2026, 07:01 | 16,255 | +2 |
| 9 Oct 2026, 02:38 | 16,253 | -3 |
| 4 Oct 2026, 14:20 | 16,256 | -2 |
| 26 Sept 2026, 08:57 | 16,258 | -6 |
| 19 Sept 2026, 11:01 | 16,264 | -1 |
| 17 Sept 2026, 02:38 | 16,265 | -5 |
| 15 Sept 2026, 05:41 | 16,270 | -1 |
| 13 Sept 2026, 16:41 | 16,271 | -1 |
| 12 Sept 2026, 13:50 | 16,272 | 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.
@Nizhnekamsk_crazy · 26,432
Telegram ranks this channel #12 of 67 here — alongside 66 others — read 12 September 2026
@Ivanovo_crazy · 26,398
Telegram ranks this channel #14 of 52 here — alongside 51 others — read 12 September 2026
@Kazan_crazy · 26,136
Telegram ranks this channel #15 of 79 here — alongside 78 others — read 13 September 2026
@Samara_crazy · 26,297
Telegram ranks this channel #17 of 72 here — alongside 71 others — read 12 September 2026
This channel appears in 4 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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“Электросталь | Новости | Слухи” (@electrostal_sluh), 16,248 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/electrostal_sluh.
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.