Channel
Magazines World
@Magzineworld
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,071subscribers
+28 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 | -1001220598597 |
|---|---|
| Type | Channel |
| Username | @Magzineworld |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 2 times, most recently 6 November 2026 |
| On Telegram | t.me/Magzineworld |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 3 Nov 2026, 00:29 | 2,071 | +5 |
| 30 Oct 2026, 21:49 | 2,066 | -1 |
| 27 Oct 2026, 20:49 | 2,067 | +1 |
| 24 Oct 2026, 11:40 | 2,066 | +2 |
| 21 Oct 2026, 20:17 | 2,064 | +5 |
| 18 Oct 2026, 09:28 | 2,059 | +4 |
| 14 Oct 2026, 23:37 | 2,055 | -1 |
| 11 Oct 2026, 13:37 | 2,056 | -1 |
| 4 Oct 2026, 19:59 | 2,057 | +4 |
| 20 Sept 2026, 02:46 | 2,053 | no change |
| 16 Sept 2026, 12:38 | 2,053 | +5 |
| 13 Sept 2026, 01:37 | 2,048 | -2 |
| 8 Sept 2026, 16:41 | 2,050 | -2 |
| 24 Aug 2026, 16:13 | 2,052 | +2 |
| 21 Aug 2026, 08:38 | 2,050 | +4 |
| 18 Aug 2026, 00:42 | 2,046 | +6 |
| 11 Aug 2026, 08:32 | 2,040 | -3 |
| 7 Aug 2026, 19:45 | 2,043 | 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.
@makkarieltsvideo · 20,774
Telegram ranks this channel #45 of 63 here — alongside 62 others — read 24 September 2026
@UPSC_Quiz_MCQ_PYQ_CSAT_Test_PDF · 73,049
Telegram ranks this channel #47 of 64 here — alongside 63 others — read 19 August 2026
@GtopGJ · 62,732
Telegram ranks this channel #51 of 56 here — alongside 55 others — read 22 August 2026
@multibaggers_valuepicks · 37,294
Telegram ranks this channel #81 of 84 here — alongside 83 others — read 29 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Magazines World” (@Magzineworld), 2,071 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Magzineworld.
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.