Channel
ππππππ
@voguhe
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
1,144subscribers
+12 since we began measuring on 6 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1001100412262 |
|---|---|
| Type | Channel |
| Username | @voguhe |
| Created | Between 1 January 2017 and 31 January 2018 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/voguhe |
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 6 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 07:55 | 1,144 | -3 |
| 14 Oct 2026, 11:10 | 1,147 | +1 |
| 10 Oct 2026, 16:59 | 1,146 | +2 |
| 6 Oct 2026, 00:38 | 1,144 | no change |
| 4 Oct 2026, 17:21 | 1,144 | +1 |
| 24 Sept 2026, 23:18 | 1,143 | +4 |
| 15 Sept 2026, 04:19 | 1,139 | -3 |
| 11 Sept 2026, 14:38 | 1,142 | +1 |
| 2 Sept 2026, 09:05 | 1,141 | +2 |
| 29 Aug 2026, 23:25 | 1,139 | +3 |
| 27 Aug 2026, 03:24 | 1,136 | +3 |
| 20 Aug 2026, 12:23 | 1,133 | +2 |
| 17 Aug 2026, 09:58 | 1,131 | -1 |
| 13 Aug 2026, 23:38 | 1,132 | -1 |
| 6 Aug 2026, 22:40 | 1,133 | +1 |
| 6 Aug 2026, 00:34 | 1,132 | 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.
@Nostalzhi Β· 22,567
Telegram ranks this channel #15 of 62 here β alongside 61 others β read 20 September 2026
@irfalodeh Β· 115,632
Telegram ranks this channel #16 of 72 here β alongside 71 others β read 18 August 2026
@shinYoga Β· 41,829
Telegram ranks this channel #20 of 71 here β alongside 70 others β read 29 August 2026
@Rap3daOriginal Β· 158,636
Telegram ranks this channel #25 of 39 here β alongside 38 others β read 26 September 2026
@ketabdeh Β· 25,132
Telegram ranks this channel #32 of 71 here β alongside 70 others β read 14 September 2026
@book_pdff Β· 23,379
Telegram ranks this channel #36 of 71 here β alongside 70 others β read 18 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 23 October 2026 β this entry's latest reading, not the date you are reading this.
βππππππβ (@voguhe), 1,144 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/voguhe.
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.