
Bot
TaskUpBot
@TaskUpesy_bot
On this record: Growth · Engagement · Citations · Cite this entry
31,764monthly users
-3,928 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 8463998552 |
|---|---|
| Type | Bot |
| Username | @TaskUpesy_bot |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| On Telegram | t.me/TaskUpesy_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 13 Aug 2026, 20:47 | 31,764 | no change |
| 13 Aug 2026, 12:37 | 31,764 | -506 |
| 12 Aug 2026, 09:32 | 32,270 | -886 |
| 11 Aug 2026, 08:53 | 33,156 | -957 |
| 10 Aug 2026, 09:01 | 34,113 | -907 |
| 9 Aug 2026, 05:55 | 35,020 | -672 |
| 7 Aug 2026, 17:47 | 35,692 | first 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 27 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.
Named by
Channels on the register whose posts name this channel's handle.
@TaskUpBotNews · 24,21967 posts@Murtiguto1st
@Murtiguto1st · 1644 posts𝗧𝗘𝗖𝗛𝗡𝗜𝗖𝗔𝗟 𝗧𝗔𝗠𝗜𝗠
@technical_tamim · 19,1423 posts💎 E A R N X T A S K S ( O F F I C I A L )
@admideasyInstagram12 · 462 posts𝘽𝙀𝙆𝙄 𝙏𝙀𝘾𝙃
@BEKI_TECH7 · 4,9532 postsIncome HZ
@IncomeHZ18 · 9,3312 posts𝗜𝗻𝘀𝘁𝗴𝗿𝗮𝗺 𝗰𝗿𝗲𝗮𝘁𝗲 𝘁𝗲𝗮𝗺
@instgram_account_create · 642 postsOnline Real site Income
@Realincomesite11 · 82 posts𝐓𝐄𝐂𝐇 𝐁𝐘 𝐘𝐎𝐍𝐀𝐒 ️
@tech_yonas · 8972 posts⚜️ 𝗩𝗜𝗣𝗖𝗥𝗬𝗣𝗧𝗢 𝗧𝗥𝗜𝗖𝗞𝗦 𝗕𝗗 ⚜️
@viptricksbd · 1352 posts🤎• 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗔𝗦𝗔𝗗•🤎
@asadul87 · 551 postBe young and free
@channel1hi · 21 postEARN _WITH_CRYPTO
@Cryptowalat · 4,5571 postEarning site🤑💰
@earningsite13 · 711 postEASY INSTA CREATOR
@easyinstagramcreator · 501 postETHIOPIAN BONES BINGO BOTS
@ethbonusbingo · 4431 postFeature_ Earning😱
@Feature_Earning_Btc · 751 postልቼ ደላላ (Liche Delala)
@goldsuurddhhs · 1971 postIncome bd 241
@incomebd2410 · 101 postInstagram Creator Studio 🔥
@Instagram_Creator_Studio_0 · 7101 post😱ইনস্টাগ্রাম সকল সমস্যা সমাধান 😰😏
@instagramunlimited56 · 171 postPatron Tech et📲🇪🇹
@patron_tech · 1,8201 postRimon setup channel
@rimonsetup · 571 postSOJIB TRICKS
@sojibtricks1 · 8441 post
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“TaskUpBot” (@TaskUpesy_bot), 31,764 monthly users as measured 13 August 2026. Telegram Register, tgregister.com/channel/TaskUpesy_bot.
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.