Channel
TAPESH
@Tapeshir
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,890subscribers
-80 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 | -1001066593538 |
|---|---|
| Type | Channel |
| Username | @Tapeshir |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/Tapeshir |
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 26 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 |
|---|---|---|
| 5 Nov 2026, 13:17 | 1,890 | -5 |
| 30 Oct 2026, 12:35 | 1,895 | -2 |
| 27 Oct 2026, 20:49 | 1,897 | -4 |
| 24 Oct 2026, 09:38 | 1,901 | -4 |
| 21 Oct 2026, 10:17 | 1,905 | -6 |
| 18 Oct 2026, 00:46 | 1,911 | -2 |
| 14 Oct 2026, 22:45 | 1,913 | -1 |
| 11 Oct 2026, 12:22 | 1,914 | -6 |
| 5 Oct 2026, 01:37 | 1,920 | -10 |
| 26 Sept 2026, 12:56 | 1,930 | -33 |
| 21 Sept 2026, 02:46 | 1,963 | no change |
| 15 Sept 2026, 03:00 | 1,963 | -5 |
| 11 Sept 2026, 03:39 | 1,968 | -2 |
| 8 Sept 2026, 09:17 | 1,970 | 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.
@ashpazzzzzi · 25,761
Telegram ranks this channel #32 of 67 here — alongside 66 others — read 13 September 2026
@andisheh_naab12 · 19,346
Telegram ranks this channel #34 of 64 here — alongside 63 others — read 1 October 2026
@mehbano2 · 29,854
Telegram ranks this channel #40 of 65 here — alongside 64 others — read 8 September 2026
This channel appears in 3 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“TAPESH” (@Tapeshir), 1,890 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Tapeshir.
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.