Channel
Свободный канал Общежития #14 «Спектр» #15 «Парус» #16,17,18 "Чешиха"(около УЛК), Измайловских общежитий(#4,5,6,8,9)
@zisbmstu
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,517subscribers
+172 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002023798110 |
|---|---|
| Type | Channel |
| Username | @zisbmstu |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/zisbmstu |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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, 22:29 | 1,517 | -5 |
| 1 Nov 2026, 12:56 | 1,522 | -1 |
| 29 Oct 2026, 04:38 | 1,523 | -2 |
| 26 Oct 2026, 06:17 | 1,525 | -1 |
| 23 Oct 2026, 08:36 | 1,526 | +7 |
| 17 Oct 2026, 16:10 | 1,519 | +1 |
| 14 Oct 2026, 23:46 | 1,518 | +1 |
| 11 Oct 2026, 13:59 | 1,517 | +2 |
| 5 Oct 2026, 05:16 | 1,515 | +15 |
| 28 Sept 2026, 02:36 | 1,500 | no change |
| 26 Sept 2026, 21:18 | 1,500 | +27 |
| 17 Sept 2026, 18:18 | 1,473 | +2 |
| 13 Sept 2026, 13:00 | 1,471 | +1 |
| 9 Sept 2026, 11:58 | 1,470 | +3 |
| 3 Sept 2026, 21:16 | 1,467 | +2 |
| 31 Aug 2026, 08:12 | 1,465 | +9 |
| 28 Aug 2026, 01:34 | 1,456 | +6 |
| 24 Aug 2026, 15:55 | 1,450 | +57 |
| 20 Aug 2026, 17:42 | 1,393 | +35 |
| 17 Aug 2026, 11:33 | 1,358 | 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.
@bmstu1830 · 29,397
Telegram ranks this channel #42 of 82 here — alongside 81 others — read 8 September 2026
@pk_bmstu · 23,300
Telegram ranks this channel #70 of 83 here — alongside 82 others — read 16 September 2026
This channel appears in 2 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.
“Свободный канал Общежития #14 «Спектр» #15 «Парус» #16,17,18 "Чешиха"(около УЛК), Измайловских общежитий(#4,5,6,8,9)” (@zisbmstu), 1,517 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/zisbmstu.
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.