Bot
AmazonGC
@iAmazonGCbot
On this record: Growth · Engagement · Citations · Cite this entry
20,221monthly users
-7,494 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8743887119 |
|---|---|
| Type | Bot |
| Username | @iAmazonGCbot |
| First recorded | 13 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 3 times, most recently 1 September 2026 |
| On Telegram | t.me/iAmazonGCbot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 30 Aug 2026, 20:25 | 20,221 | -4,849 |
| 26 Aug 2026, 19:24 | 25,070 | -2,296 |
| 23 Aug 2026, 06:46 | 27,366 | -1,382 |
| 20 Aug 2026, 17:19 | 28,748 | -3,145 |
| 17 Aug 2026, 16:26 | 31,893 | -268 |
| 14 Aug 2026, 18:13 | 32,161 | +446 |
| 13 Aug 2026, 20:50 | 31,715 | no change |
| 12 Aug 2026, 08:23 | 31,715 | +1,572 |
| 9 Aug 2026, 05:21 | 30,143 | +2,428 |
| 7 Aug 2026, 17:16 | 27,715 | 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 23 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 22 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.
@ItsGiveawayTimes · 14,9994 postsMONSTERS
@MONSTERS047 · 144 postsStock X Updates
@AstralxUpdates · 4,4893 postsNamaste DSA
@FreeNamasteDSACourse · 1,4042 postsRupee point
@onlinemoneyearningOf · 2752 postsPannel hub
@pannelhub009 · 32 postsTaskLinker [ Official ]
@tasklinker · 2,4232 postsZN ERA NETWORK
@zn_era001 · 1,1502 postsA2Z MODZ
@A2ZMODZ_free · 1,0371 postTapcoins Daily Combos
@Airdropalexa1 · 1,6481 postEarn Wise
@earn_wise_official · 2491 postEarnRoy
@earnove · 1711 post𝑮𝑯𝑶𝑺𝑻 𝑮𝑰𝑽𝑬𝑨𝑾𝑨𝒀𝑺 !!
@KGFSTOREZ · 5691 postGL LOOTERS
@looterboy0 · 1751 postNAITIK X NETWORK
@naitikxnetwork · 1,1421 postPrime Looters ( Official )
@Prime_Loot · 7361 postTASK HUB 💵
@referandearn660 · 1,2681 postApp review 🤑💰
@reviwandearn7 · 5361 post🎤𓄂꯭꯭🐲⃝⃪꯭꯭꯭꯭🇷 𝐄 𝐗 𝐗𓁋𓄂꯭꯭ᬼ꯭꯭𓄻꯭𝆺𝅥⃝꯭⎯꯭͓ꨄ
@REXXXXXX_OP · 251 post𝙎𝙏𝙍𝙀𝘼𝙈 𝙓 𝙎𝙏𝙊𝙍𝙀
@walltalkescrow · 471 postFIRST STEP OF EARNING
@whatsappagents676 · 8811 postPROZXL TEAM ✨✨
@wsfile2010 · 891 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“AmazonGC” (@iAmazonGCbot), 20,221 monthly users as measured 30 August 2026. Telegram Register, tgregister.com/channel/iAmazonGCbot.
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.