Channel
Max help channel
@maxhelp
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,760subscribers
+41 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001001620534 |
|---|---|
| Type | Channel |
| Username | @maxhelp |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/maxhelp |
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 12 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Oct 2026, 23:05 | 6,760 | -1 |
| 16 Oct 2026, 07:40 | 6,761 | +11 |
| 8 Oct 2026, 01:01 | 6,750 | +8 |
| 1 Oct 2026, 21:37 | 6,742 | -11 |
| 16 Sept 2026, 05:16 | 6,753 | -2 |
| 12 Sept 2026, 05:39 | 6,755 | +2 |
| 2 Sept 2026, 22:38 | 6,753 | +6 |
| 31 Aug 2026, 04:58 | 6,747 | +1 |
| 28 Aug 2026, 05:13 | 6,746 | +6 |
| 27 Aug 2026, 21:46 | 6,740 | no change |
| 25 Aug 2026, 01:27 | 6,740 | +1 |
| 21 Aug 2026, 05:34 | 6,739 | +9 |
| 15 Aug 2026, 03:26 | 6,730 | +5 |
| 11 Aug 2026, 22:43 | 6,725 | +3 |
| 9 Aug 2026, 06:11 | 6,722 | +3 |
| 5 Aug 2026, 22:23 | 6,719 | 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.
@MAXOBJECT · 39,947
Telegram ranks this channel #4 of 57 here — alongside 56 others — read 30 August 2026
@VoxelLearn · 29,997
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 8 September 2026
@architects_tech · 20,776
Telegram ranks this channel #14 of 67 here — alongside 66 others — read 26 September 2026
@Voxelproduction · 46,428
Telegram ranks this channel #18 of 75 here — alongside 74 others — read 27 August 2026
@cad_3d · 22,348
Telegram ranks this channel #35 of 79 here — alongside 78 others — read 20 September 2026
@memari180 · 55,797
Telegram ranks this channel #41 of 77 here — alongside 76 others — read 2 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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“Max help channel” (@maxhelp), 6,760 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/maxhelp.
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.