Channel
Прельские новости🫦
@prelskie_news
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,652subscribers
-89 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001526611512 |
|---|---|
| Type | Channel |
| Username | @prelskie_news |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/prelskie_news |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 09:42 | 4,652 | -32 |
| 15 Sept 2026, 12:17 | 4,684 | -9 |
| 11 Sept 2026, 13:20 | 4,693 | -12 |
| 6 Sept 2026, 13:59 | 4,705 | +13 |
| 2 Sept 2026, 20:25 | 4,692 | no change |
| 2 Sept 2026, 08:28 | 4,692 | -14 |
| 30 Aug 2026, 03:55 | 4,706 | -23 |
| 27 Aug 2026, 08:37 | 4,729 | -22 |
| 24 Aug 2026, 09:34 | 4,751 | +19 |
| 20 Aug 2026, 08:06 | 4,732 | +39 |
| 17 Aug 2026, 16:16 | 4,693 | -6 |
| 14 Aug 2026, 00:07 | 4,699 | -16 |
| 10 Aug 2026, 23:02 | 4,715 | -24 |
| 7 Aug 2026, 19:48 | 4,739 | -2 |
| 7 Aug 2026, 12:12 | 4,741 | 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.
@dom2_news2 · 58,667
Telegram ranks this channel #10 of 36 here — alongside 35 others — read 1 September 2026
@alianaustinenko · 37,363
Telegram ranks this channel #34 of 46 here — alongside 45 others — read 31 August 2026
@marykohno888 · 67,138
Telegram ranks this channel #40 of 45 here — alongside 44 others — read 21 August 2026
@demiand_grill · 250,601
Telegram ranks this channel #44 of 65 here — alongside 64 others — read 21 August 2026
@DaryaPinzar86 · 68,817
Telegram ranks this channel #45 of 57 here — alongside 56 others — read 12 September 2026
This channel appears in 5 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Прельские новости🫦” (@prelskie_news), 4,652 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/prelskie_news.
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.