Telegram RegisterThe public register of Telegram
Telegram profile photo for برنامه ناشناس

Bot

برنامه ناشناس

@App_nashenasBot

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

122,251monthly users

+77,482 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID8928351867
TypeBot
Username@App_nashenasBot
First recorded11 August 2026
Last confirmed live24 October 2026
Measurements held46
Confirmed unchanged1 time, most recently 24 October 2026
On Telegramt.me/App_nashenasBot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 16 August 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 why it has no browse page of its own yet.

Growth

44,769146,30695,537.56 August 2026 — 44,769 monthly users7 August 2026 — 56,368 monthly users8 August 2026 — 64,521 monthly users9 August 2026 — 71,532 monthly users10 August 2026 — 79,180 monthly users11 August 2026 — 79,180 monthly users12 August 2026 — 86,566 monthly users14 August 2026 — 94,135 monthly users16 August 2026 — 102,047 monthly users17 August 2026 — 107,886 monthly users18 August 2026 — 112,956 monthly users19 August 2026 — 115,422 monthly users20 August 2026 — 118,732 monthly users22 August 2026 — 125,536 monthly users24 August 2026 — 133,172 monthly users25 August 2026 — 135,679 monthly users26 August 2026 — 139,349 monthly users28 August 2026 — 143,440 monthly users29 August 2026 — 144,310 monthly users30 August 2026 — 146,306 monthly users31 August 2026 — 144,454 monthly users1 September 2026 — 140,537 monthly users2 September 2026 — 142,563 monthly users3 September 2026 — 141,656 monthly users5 September 2026 — 138,982 monthly users8 September 2026 — 134,745 monthly users11 September 2026 — 125,259 monthly users13 September 2026 — 118,973 monthly users14 September 2026 — 117,162 monthly users16 September 2026 — 118,698 monthly users18 September 2026 — 119,910 monthly users24 September 2026 — 121,638 monthly users3 October 2026 — 117,185 monthly users8 October 2026 — 120,537 monthly users12 October 2026 — 122,691 monthly users14 October 2026 — 124,091 monthly users15 October 2026 — 125,515 monthly users16 October 2026 — 125,045 monthly users17 October 2026 — 122,714 monthly users18 October 2026 — 129,452 monthly users19 October 2026 — 130,223 monthly users20 October 2026 — 126,362 monthly users21 October 2026 — 124,326 monthly users22 October 2026 — 118,389 monthly users23 October 2026 — 119,113 monthly users24 October 2026 — 122,251 monthly users122,2516 August 202624 October 2026
46 measurements spanning 79 days, net +77,482. 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 29,538–161,537 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 46
Measured (UTC)Monthly usersChange
24 Oct 2026, 23:10122,251+3,138
23 Oct 2026, 20:58119,113+724
22 Oct 2026, 18:47118,389-5,937
21 Oct 2026, 16:47124,326-2,036
20 Oct 2026, 09:48126,362-3,861
19 Oct 2026, 12:49130,223+771
18 Oct 2026, 09:20129,452+6,738
17 Oct 2026, 06:28122,714-2,331
16 Oct 2026, 04:50125,045-470
15 Oct 2026, 07:50125,515+1,424
14 Oct 2026, 09:47124,091+1,400
12 Oct 2026, 20:00122,691+2,154
8 Oct 2026, 04:22120,537+3,352
3 Oct 2026, 14:22117,185-4,453
24 Sept 2026, 20:35121,638+1,728
18 Sept 2026, 17:01119,910+1,212
16 Sept 2026, 08:59118,698+1,536
14 Sept 2026, 17:56117,162-1,811
13 Sept 2026, 02:16118,973-6,286
11 Sept 2026, 04:59125,259first 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 4 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.

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

“برنامه ناشناس” (@App_nashenasBot), 122,251 monthly users as measured 24 October 2026. Telegram Register, tgregister.com/channel/App_nashenasBot.

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.