
Channel
T H R
@THRvibes
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,811subscribers
-177 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002179074480 |
|---|---|
| Type | Channel |
| Username | @THRvibes |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/THRvibes |
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 15 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 |
|---|---|---|
| 4 Nov 2026, 03:26 | 2,811 | -6 |
| 1 Nov 2026, 02:31 | 2,817 | -5 |
| 29 Oct 2026, 06:38 | 2,822 | -6 |
| 26 Oct 2026, 01:51 | 2,828 | -6 |
| 23 Oct 2026, 08:27 | 2,834 | -6 |
| 20 Oct 2026, 01:19 | 2,840 | -8 |
| 17 Oct 2026, 01:09 | 2,848 | -5 |
| 13 Oct 2026, 22:06 | 2,853 | -11 |
| 8 Oct 2026, 17:00 | 2,864 | -18 |
| 1 Oct 2026, 21:37 | 2,882 | -35 |
| 16 Sept 2026, 01:58 | 2,917 | -12 |
| 12 Sept 2026, 12:17 | 2,929 | -8 |
| 12 Sept 2026, 00:12 | 2,937 | no change |
| 8 Sept 2026, 09:15 | 2,937 | -16 |
| 2 Sept 2026, 21:45 | 2,953 | -2 |
| 30 Aug 2026, 21:48 | 2,955 | -6 |
| 27 Aug 2026, 15:06 | 2,961 | -3 |
| 24 Aug 2026, 16:09 | 2,964 | -3 |
| 21 Aug 2026, 04:43 | 2,967 | -11 |
| 17 Aug 2026, 21:04 | 2,978 | 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.
@CinemaDL_ir · 54,474
Telegram ranks this channel #52 of 77 here — alongside 76 others — read 24 August 2026
@gifkoshr · 76,823
Telegram ranks this channel #52 of 77 here — alongside 76 others — read 19 August 2026
@MEMEZ0NE · 111,815
Telegram ranks this channel #61 of 80 here — alongside 79 others — read 13 August 2026
@MarizNews · 60,712
Telegram ranks this channel #68 of 73 here — alongside 72 others — read 27 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“T H R” (@THRvibes), 2,811 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/THRvibes.
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.