Telegram RegisterThe public register of Telegram
Telegram profile photo for Report MAL s

Channel

Report MAL s

@reportMALss

On this record: Topic · Growth · Engagement · Cite this entry

3,048subscribers

-141 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-1001313276972
TypeChannel
Username@reportMALss
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live12 October 2026
Measurements held18
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/reportMALss

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

3,0483,1893,118.57 August 2026 — 3,189 subscribers8 August 2026 — 3,186 subscribers11 August 2026 — 3,176 subscribers14 August 2026 — 3,168 subscribers17 August 2026 — 3,162 subscribers20 August 2026 — 3,158 subscribers24 August 2026 — 3,151 subscribers26 August 2026 — 3,146 subscribers30 August 2026 — 3,140 subscribers1 September 2026 — 3,134 subscribers5 September 2026 — 3,127 subscribers10 September 2026 — 3,113 subscribers10 September 2026 — 3,113 subscribers14 September 2026 — 3,104 subscribers19 September 2026 — 3,093 subscribers28 September 2026 — 3,074 subscribers5 October 2026 — 3,057 subscribers12 October 2026 — 3,048 subscribers7 August 202612 October 2026
18 measurements spanning 66 days, net -141. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,027–3,210 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 16:413,048-9
5 Oct 2026, 18:163,057-17
28 Sept 2026, 16:003,074-19
19 Sept 2026, 02:573,093-11
14 Sept 2026, 08:013,104-9
10 Sept 2026, 21:343,113no change
10 Sept 2026, 07:413,113-14
5 Sept 2026, 02:413,127-7
1 Sept 2026, 17:563,134-6
30 Aug 2026, 00:373,140-6
26 Aug 2026, 23:183,146-5
24 Aug 2026, 08:053,151-7
20 Aug 2026, 18:073,158-4
17 Aug 2026, 16:043,162-6
14 Aug 2026, 09:583,168-8
11 Aug 2026, 05:073,176-10
8 Aug 2026, 05:133,186-3
7 Aug 2026, 06:473,189first 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.

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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“Report MAL s” (@reportMALss), 3,048 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/reportMALss.

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.