Channel
MeloWoodZzZ 🔉
@melowoodz
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,228subscribers
-85 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 | -1001120063764 |
|---|---|
| Type | Channel |
| Username | @melowoodz |
| Created | Between 1 May 2017 and 29 February 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/melowoodz |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 5 Nov 2026, 19:47 | 2,228 | -3 |
| 2 Nov 2026, 16:46 | 2,231 | -1 |
| 30 Oct 2026, 20:07 | 2,232 | -5 |
| 27 Oct 2026, 20:45 | 2,237 | -2 |
| 24 Oct 2026, 23:25 | 2,239 | -3 |
| 22 Oct 2026, 04:09 | 2,242 | -1 |
| 18 Oct 2026, 11:40 | 2,243 | -5 |
| 15 Oct 2026, 06:50 | 2,248 | -3 |
| 11 Oct 2026, 23:57 | 2,251 | -6 |
| 5 Oct 2026, 05:19 | 2,257 | -7 |
| 26 Sept 2026, 22:35 | 2,264 | -7 |
| 18 Sept 2026, 00:36 | 2,271 | no change |
| 17 Sept 2026, 16:38 | 2,271 | -5 |
| 13 Sept 2026, 17:59 | 2,276 | -4 |
| 10 Sept 2026, 00:41 | 2,280 | -5 |
| 4 Sept 2026, 22:20 | 2,285 | -6 |
| 29 Aug 2026, 21:52 | 2,291 | -1 |
| 27 Aug 2026, 04:28 | 2,292 | -1 |
| 24 Aug 2026, 01:58 | 2,293 | -8 |
| 20 Aug 2026, 01:12 | 2,301 | 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.
@soheyl_english · 58,797
Telegram ranks this channel #29 of 87 here — alongside 86 others — read 23 August 2026
@amiralichannel · 68,112
Telegram ranks this channel #36 of 93 here — alongside 92 others — read 20 August 2026
@hollywooddaily · 27,218
Telegram ranks this channel #52 of 72 here — alongside 71 others — read 19 September 2026
@spanishtimee · 19,793
Telegram ranks this channel #57 of 74 here — alongside 73 others — read 1 October 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“MeloWoodZzZ 🔉” (@melowoodz), 2,228 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/melowoodz.
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.