
Channel
بحوث مشاريع تخرج حل واجبات
@TUplans
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,323subscribers
+85 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002083036759 |
|---|---|
| Type | Channel |
| Username | @TUplans |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 October 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/TUplans |
Topic
Education — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 13 Nov 2026, 14:16 | 1,323 | -10 |
| 8 Nov 2026, 23:40 | 1,333 | -10 |
| 5 Nov 2026, 21:17 | 1,343 | -17 |
| 2 Nov 2026, 10:25 | 1,360 | -30 |
| 30 Oct 2026, 00:08 | 1,390 | +1 |
| 27 Oct 2026, 04:50 | 1,389 | +3 |
| 24 Oct 2026, 04:06 | 1,386 | +1 |
| 21 Oct 2026, 09:06 | 1,385 | +11 |
| 18 Oct 2026, 01:10 | 1,374 | +19 |
| 15 Oct 2026, 04:40 | 1,355 | +37 |
| 11 Oct 2026, 15:37 | 1,318 | +21 |
| 5 Oct 2026, 05:18 | 1,297 | +12 |
| 2 Oct 2026, 04:26 | 1,285 | no change |
| 26 Sept 2026, 23:00 | 1,285 | +9 |
| 17 Sept 2026, 12:19 | 1,276 | +2 |
| 13 Sept 2026, 19:19 | 1,274 | +3 |
| 10 Sept 2026, 07:59 | 1,271 | +13 |
| 5 Sept 2026, 05:17 | 1,258 | +2 |
| 1 Sept 2026, 12:57 | 1,256 | +10 |
| 29 Aug 2026, 23:04 | 1,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.
@G_TaibahU · 27,675
Telegram ranks this channel #19 of 87 here — alongside 86 others — read 9 September 2026
@kkubooks · 19,231
Telegram ranks this channel #20 of 74 here — alongside 73 others — read 2 October 2026
@kkueduTG · 27,327
Telegram ranks this channel #25 of 75 here — alongside 74 others — read 10 September 2026
@universitykku · 50,932
Telegram ranks this channel #29 of 74 here — alongside 73 others — read 25 August 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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“بحوث مشاريع تخرج حل واجبات” (@TUplans), 1,323 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/TUplans.
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.