Telegram RegisterThe public register of Telegram
Telegram profile photo for نام نام کردن نهایی

Bot

نام نام کردن نهایی

@mamemidibot

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

29,916monthly users

+4,554 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID6737307394
TypeBot
Username@mamemidibot
First recorded17 August 2026
Last confirmed live7 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/mamemidibot

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

Growth

12,59831,75022,1746 August 2026 — 25,362 monthly users8 August 2026 — 22,505 monthly users10 August 2026 — 20,652 monthly users11 August 2026 — 20,083 monthly users12 August 2026 — 19,593 monthly users13 August 2026 — 19,225 monthly users14 August 2026 — 18,477 monthly users17 August 2026 — 18,477 monthly users18 August 2026 — 17,345 monthly users19 August 2026 — 17,067 monthly users20 August 2026 — 16,175 monthly users22 August 2026 — 15,738 monthly users24 August 2026 — 12,910 monthly users26 August 2026 — 12,696 monthly users27 August 2026 — 12,598 monthly users28 August 2026 — 12,950 monthly users29 August 2026 — 13,286 monthly users31 August 2026 — 14,220 monthly users1 September 2026 — 14,564 monthly users4 September 2026 — 15,082 monthly users6 September 2026 — 15,770 monthly users9 September 2026 — 16,712 monthly users12 September 2026 — 16,925 monthly users13 September 2026 — 17,125 monthly users15 September 2026 — 17,647 monthly users17 September 2026 — 17,734 monthly users25 September 2026 — 18,754 monthly users4 October 2026 — 22,566 monthly users8 October 2026 — 24,551 monthly users13 October 2026 — 26,243 monthly users14 October 2026 — 26,864 monthly users16 October 2026 — 27,044 monthly users17 October 2026 — 27,390 monthly users18 October 2026 — 27,766 monthly users19 October 2026 — 28,173 monthly users20 October 2026 — 28,135 monthly users21 October 2026 — 29,436 monthly users22 October 2026 — 29,611 monthly users24 October 2026 — 29,604 monthly users25 October 2026 — 31,041 monthly users26 October 2026 — 31,519 monthly users29 October 2026 — 31,718 monthly users30 October 2026 — 31,545 monthly users31 October 2026 — 31,750 monthly users2 November 2026 — 31,593 monthly users6 November 2026 — 30,763 monthly users7 November 2026 — 29,916 monthly users29,9166 August 20267 November 2026
47 measurements spanning 93 days, net +4,554. 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 9,725–34,623 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 47
Measured (UTC)Monthly usersChange
7 Nov 2026, 23:0729,916-847
6 Nov 2026, 19:4530,763-830
2 Nov 2026, 20:2531,593-157
31 Oct 2026, 20:2831,750+205
30 Oct 2026, 20:2731,545-173
29 Oct 2026, 17:1431,718+199
26 Oct 2026, 17:2931,519+478
25 Oct 2026, 20:5631,041+1,437
24 Oct 2026, 22:1929,604-7
22 Oct 2026, 21:1829,611+175
21 Oct 2026, 17:3629,436+1,301
20 Oct 2026, 14:5928,135-38
19 Oct 2026, 16:2628,173+407
18 Oct 2026, 13:4527,766+376
17 Oct 2026, 11:5627,390+346
16 Oct 2026, 14:2727,044+180
14 Oct 2026, 15:0026,864+621
13 Oct 2026, 03:0826,243+1,692
8 Oct 2026, 17:2124,551+1,985
4 Oct 2026, 08:0022,566first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 29 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“نام نام کردن نهایی” (@mamemidibot), 29,916 monthly users as measured 7 November 2026. Telegram Register, tgregister.com/channel/mamemidibot.

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.