Channel
@utubebot_3
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
190,236subscribers
-191 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001336923142 |
|---|---|
| Type | Channel |
| Username | @utubebot_3 |
| Created | 25 April 2018 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/utubebot_3 |
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 47% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:56 | 190,236 | -28 |
| 11 Aug 2026, 21:46 | 190,264 | -84 |
| 11 Aug 2026, 00:13 | 190,348 | -42 |
| 10 Aug 2026, 02:21 | 190,390 | +5 |
| 9 Aug 2026, 03:53 | 190,385 | -12 |
| 8 Aug 2026, 06:14 | 190,397 | -37 |
| 7 Aug 2026, 04:21 | 190,434 | +7 |
| 7 Aug 2026, 00:00 | 190,427 | no change |
| 6 Aug 2026, 23:54 | 190,427 | first reading |
3 posts held, back to 25 April 2018 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 17 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 5 December 2023. An engagement rate over an empty window would be a number about nothing.
🔸 لیست ربات ها ▶️ ربات دانلود از یوتیوب دانلود به صورت فایل ➡️ @utubestbot دانلود به صورت لینک دانلود ➡️ @youtibot ➖➖➖➖➖➖➖➖➖➖➖➖ 🌐 ربات دانلود از اینستاگرام 👇 @instapico_bot ➖➖➖➖➖➖➖➖➖➖➖➖ 🐦 ربات دانلود از ایکس (توییتر) و پینترست 👇 @taksavebot ➖➖➖➖➖➖➖➖➖➖➖➖ 📺 ربات دانلود از تیک تاک 👇 @TikTokio_Bot ➖➖➖➖➖➖➖➖➖➖➖➖
Signed arash
.
Channel created
Showing the 3 most recent of 3 posts we hold for @utubebot_3. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“ربات دانلود از یوتیوب” (@utubebot_3), 190,236 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/utubebot_3.
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.