Channel
DINOPLAY
@dino_1122
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,188subscribers
-399 since we began measuring on 10 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001835071251 |
|---|---|
| Type | Channel |
| Username | @dino_1122 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/dino_1122 |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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, 03:29 | 4,188 | -14 |
| 1 Nov 2026, 07:10 | 4,202 | -25 |
| 29 Oct 2026, 13:36 | 4,227 | -15 |
| 26 Oct 2026, 20:16 | 4,242 | -22 |
| 24 Oct 2026, 02:10 | 4,264 | -32 |
| 21 Oct 2026, 06:01 | 4,296 | -20 |
| 18 Oct 2026, 13:09 | 4,316 | -12 |
| 15 Oct 2026, 23:31 | 4,328 | -20 |
| 12 Oct 2026, 17:34 | 4,348 | -50 |
| 6 Oct 2026, 11:58 | 4,398 | -49 |
| 29 Sept 2026, 18:17 | 4,447 | -107 |
| 15 Sept 2026, 14:39 | 4,554 | -23 |
| 12 Sept 2026, 03:40 | 4,577 | -10 |
| 10 Sept 2026, 00:20 | 4,587 | 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.
@pymx1th1 · 22,059
Telegram ranks this channel #18 of 64 here — alongside 63 others — read 19 September 2026
@SFbet88_V · 20,469
Telegram ranks this channel #23 of 56 here — alongside 55 others — read 21 September 2026
@slotpgwallet · 28,979
Telegram ranks this channel #38 of 68 here — alongside 67 others — read 10 September 2026
@zeus7899 · 21,789
Telegram ranks this channel #47 of 58 here — alongside 57 others — read 19 September 2026
@dbet_3 · 28,730
Telegram ranks this channel #47 of 61 here — alongside 60 others — read 10 September 2026
@ulb88 · 22,223
Telegram ranks this channel #64 of 72 here — alongside 71 others — read 19 September 2026
This channel appears in 6 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.
“DINOPLAY” (@dino_1122), 4,188 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/dino_1122.
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.