Channel
Интеллект+
@intellectpl
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,129subscribers
-117 since we began measuring on 8 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001713922500 |
|---|---|
| Type | Channel |
| Username | @intellectpl |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/intellectpl |
Topic
Other / unclassifiable — 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 30 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 |
|---|---|---|
| 3 Nov 2026, 03:51 | 2,129 | -1 |
| 31 Oct 2026, 04:10 | 2,130 | -4 |
| 27 Oct 2026, 23:06 | 2,134 | -5 |
| 25 Oct 2026, 04:57 | 2,139 | -4 |
| 22 Oct 2026, 06:59 | 2,143 | -4 |
| 19 Oct 2026, 08:56 | 2,147 | -4 |
| 16 Oct 2026, 08:16 | 2,151 | -4 |
| 13 Oct 2026, 12:35 | 2,155 | -6 |
| 7 Oct 2026, 05:58 | 2,161 | -19 |
| 30 Sept 2026, 00:16 | 2,180 | -27 |
| 19 Sept 2026, 10:58 | 2,207 | -17 |
| 18 Sept 2026, 14:52 | 2,224 | no change |
| 14 Sept 2026, 13:57 | 2,224 | -18 |
| 11 Sept 2026, 02:17 | 2,242 | -4 |
| 8 Sept 2026, 16:17 | 2,246 | 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.
@engvisuals · 20,313
Telegram ranks this channel #9 of 71 here — alongside 70 others — read 29 September 2026
@english_pdf_basic_books · 31,367
Telegram ranks this channel #31 of 81 here — alongside 80 others — read 8 September 2026
@DailyEnglishGrammar · 20,223
Telegram ranks this channel #53 of 83 here — alongside 82 others — read 30 September 2026
@DABLE_FILMS · 49,645
Telegram ranks this channel #57 of 61 here — alongside 60 others — read 29 September 2026
@Englishcoursebookss · 30,558
Telegram ranks this channel #68 of 81 here — alongside 80 others — read 9 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Интеллект+” (@intellectpl), 2,129 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/intellectpl.
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.