Telegram RegisterThe public register of Telegram
Telegram profile photo for MM

Channel

MM

@callmematyas

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

1,110subscribers

+1,073 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002245796731
TypeChannel
Username@callmematyas
CreatedBetween 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live2 November 2026
Measurements held18
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/callmematyas

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 7 October 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 the other topics.

Growth

371,11757710 August 2026 — 37 subscribers10 August 2026 — 41 subscribers17 August 2026 — 47 subscribers24 August 2026 — 64 subscribers1 September 2026 — 56 subscribers11 September 2026 — 60 subscribers18 September 2026 — 64 subscribers2 October 2026 — 1,085 subscribers7 October 2026 — 1,085 subscribers8 October 2026 — 1,096 subscribers13 October 2026 — 1,116 subscribers16 October 2026 — 1,113 subscribers19 October 2026 — 1,112 subscribers22 October 2026 — 1,117 subscribers25 October 2026 — 1,116 subscribers27 October 2026 — 1,115 subscribers30 October 2026 — 1,112 subscribers2 November 2026 — 1,110 subscribers1,11010 August 20262 November 2026
18 measurements spanning 84 days, net +1,073. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 19:071,110-2
30 Oct 2026, 19:281,112-3
27 Oct 2026, 22:361,115-1
25 Oct 2026, 03:301,116-1
22 Oct 2026, 11:591,117+5
19 Oct 2026, 13:351,112-1
16 Oct 2026, 20:181,113-3
13 Oct 2026, 23:561,116+20
8 Oct 2026, 16:221,096+11
7 Oct 2026, 04:191,085no change
2 Oct 2026, 09:201,085+1,021
18 Sept 2026, 13:5964+4
11 Sept 2026, 05:2260+4
1 Sept 2026, 15:4256-8
24 Aug 2026, 18:0264+17
17 Aug 2026, 10:0747+6
10 Aug 2026, 19:3141+4
10 Aug 2026, 10:1537first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“MM” (@callmematyas), 1,110 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/callmematyas.

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.