Telegram RegisterThe public register of Telegram
Telegram profile photo for بوت تحميل من اليوتيوب سناب

Bot

بوت تحميل من اليوتيوب سناب

@YNXBOT

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

23,293monthly users

-2,477 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 ID720967619
TypeBot
Username@YNXBOT
First recorded14 August 2026
Last confirmed live24 October 2026
Measurements held43
Confirmed unchanged1 time, most recently 24 October 2026
On Telegramt.me/YNXBOT

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 77% 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

23,11626,18524,650.56 August 2026 — 25,770 monthly users7 August 2026 — 25,866 monthly users9 August 2026 — 25,913 monthly users10 August 2026 — 25,891 monthly users11 August 2026 — 25,957 monthly users13 August 2026 — 26,007 monthly users14 August 2026 — 26,016 monthly users14 August 2026 — 26,016 monthly users16 August 2026 — 25,741 monthly users17 August 2026 — 26,054 monthly users18 August 2026 — 26,085 monthly users19 August 2026 — 26,124 monthly users20 August 2026 — 26,144 monthly users21 August 2026 — 26,139 monthly users22 August 2026 — 26,183 monthly users24 August 2026 — 26,165 monthly users25 August 2026 — 26,185 monthly users27 August 2026 — 26,177 monthly users28 August 2026 — 26,132 monthly users29 August 2026 — 25,220 monthly users30 August 2026 — 25,425 monthly users31 August 2026 — 25,337 monthly users1 September 2026 — 25,210 monthly users3 September 2026 — 25,076 monthly users6 September 2026 — 24,920 monthly users9 September 2026 — 24,574 monthly users11 September 2026 — 24,312 monthly users13 September 2026 — 24,133 monthly users15 September 2026 — 24,034 monthly users17 September 2026 — 23,955 monthly users19 September 2026 — 23,765 monthly users26 September 2026 — 23,653 monthly users4 October 2026 — 23,116 monthly users9 October 2026 — 23,318 monthly users13 October 2026 — 23,376 monthly users14 October 2026 — 23,368 monthly users15 October 2026 — 23,318 monthly users17 October 2026 — 23,473 monthly users18 October 2026 — 23,562 monthly users19 October 2026 — 23,555 monthly users22 October 2026 — 23,549 monthly users23 October 2026 — 23,565 monthly users24 October 2026 — 23,293 monthly users23,2936 August 202624 October 2026
43 measurements spanning 79 days, net -2,477. 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 22,656–26,645 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 43
Measured (UTC)Monthly usersChange
24 Oct 2026, 10:1623,293-272
23 Oct 2026, 07:5123,565+16
22 Oct 2026, 05:4923,549-6
19 Oct 2026, 22:1823,555-7
18 Oct 2026, 19:3023,562+89
17 Oct 2026, 20:3923,473+155
15 Oct 2026, 23:2623,318-50
14 Oct 2026, 20:3123,368-8
13 Oct 2026, 11:3723,376+58
9 Oct 2026, 06:3723,318+202
4 Oct 2026, 17:3723,116-537
26 Sept 2026, 21:3923,653-112
19 Sept 2026, 17:3923,765-190
17 Sept 2026, 03:5923,955-79
15 Sept 2026, 07:3824,034-99
13 Sept 2026, 17:1624,133-179
11 Sept 2026, 19:0124,312-262
9 Sept 2026, 05:1824,574-346
6 Sept 2026, 00:5524,920-156
3 Sept 2026, 19:1825,076first 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.

Forward network

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.

Mentions

Named by 18 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.

“بوت تحميل من اليوتيوب سناب” (@YNXBOT), 23,293 monthly users as measured 24 October 2026. Telegram Register, tgregister.com/channel/YNXBOT.

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.