Channel
HELLODIGI
@HELLODIGI
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,505subscribers
+36 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001129746773 |
|---|---|
| Type | Channel |
| Username | @HELLODIGI |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 2 times, most recently 6 November 2026 |
| On Telegram | t.me/HELLODIGI |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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, 02:59 | 2,505 | -4 |
| 31 Oct 2026, 17:34 | 2,509 | +3 |
| 28 Oct 2026, 10:55 | 2,506 | +3 |
| 25 Oct 2026, 07:14 | 2,503 | +4 |
| 22 Oct 2026, 12:14 | 2,499 | +3 |
| 18 Oct 2026, 22:27 | 2,496 | +5 |
| 16 Oct 2026, 05:47 | 2,491 | +3 |
| 8 Oct 2026, 03:41 | 2,488 | +1 |
| 1 Oct 2026, 21:36 | 2,487 | -2 |
| 16 Sept 2026, 12:19 | 2,489 | +4 |
| 16 Sept 2026, 00:04 | 2,485 | no change |
| 13 Sept 2026, 01:56 | 2,485 | +3 |
| 8 Sept 2026, 21:39 | 2,482 | -1 |
| 4 Sept 2026, 00:14 | 2,483 | +5 |
| 1 Sept 2026, 00:16 | 2,478 | -1 |
| 26 Aug 2026, 11:33 | 2,479 | +3 |
| 23 Aug 2026, 07:48 | 2,476 | +2 |
| 19 Aug 2026, 17:03 | 2,474 | -1 |
| 16 Aug 2026, 17:37 | 2,475 | +1 |
| 13 Aug 2026, 11:38 | 2,474 | 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.
@denait · 21,059
Telegram ranks this channel #43 of 79 here — alongside 78 others — read 24 September 2026
@myyazdmusic_com · 21,869
Telegram ranks this channel #55 of 56 here — alongside 55 others — read 27 September 2026
@amuzesh_computer · 41,280
Telegram ranks this channel #63 of 79 here — alongside 78 others — read 29 August 2026
@shabake_karan · 25,607
Telegram ranks this channel #66 of 82 here — alongside 81 others — read 14 September 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.
“HELLODIGI” (@HELLODIGI), 2,505 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/HELLODIGI.
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.