
Bot
ForwardsCoverBot
@ForwardsCoverBot
On this record: Topic · Growth · Engagement · Citations · Cite this entry
54,219monthly users
-1,130 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 432668551 |
|---|---|
| Type | Bot |
| Username | @ForwardsCoverBot |
| First recorded | 12 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ForwardsCoverBot |
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 21 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 18 Sept 2026, 05:16 | 54,219 | +5 |
| 15 Sept 2026, 21:22 | 54,214 | +1,344 |
| 14 Sept 2026, 04:17 | 52,870 | -1,147 |
| 12 Sept 2026, 13:02 | 54,017 | -104 |
| 10 Sept 2026, 11:15 | 54,121 | +1,382 |
| 7 Sept 2026, 07:15 | 52,739 | -531 |
| 4 Sept 2026, 14:19 | 53,270 | -1,850 |
| 2 Sept 2026, 21:36 | 55,120 | -21 |
| 31 Aug 2026, 16:15 | 55,141 | +22 |
| 30 Aug 2026, 12:47 | 55,119 | -146 |
| 29 Aug 2026, 09:53 | 55,265 | -114 |
| 28 Aug 2026, 09:43 | 55,379 | -119 |
| 27 Aug 2026, 11:17 | 55,498 | +1,071 |
| 26 Aug 2026, 13:33 | 54,427 | -1,334 |
| 25 Aug 2026, 10:47 | 55,761 | +63 |
| 24 Aug 2026, 09:06 | 55,698 | -125 |
| 22 Aug 2026, 19:54 | 55,823 | -21 |
| 21 Aug 2026, 09:56 | 55,844 | +134 |
| 20 Aug 2026, 07:35 | 55,710 | +112 |
| 18 Aug 2026, 13:18 | 55,598 | 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 84 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
@acreditasequeser · 23819 postschero vouches
@chvtrans · 418 postsCat
@catlove20 · 116 posts텔레그램 대신 전해드립니다
@TG_FW_IT · 1514 posts𝗿𝗲𝗰𝗲𝗶𝗽𝘁𝘀
@elielivouches · 3914 postssahar_dance_naz
@dance_vip_nab · 10313 posts𝚃𝙶 "𝚂𝙿𝙴𝙰𝙺 𝙽𝙾𝚆"
@tgspeaknow · 8713 postsGamiee’s Uber & DoorDash Orders
@GamieeVouches · 41812 postsTG MENTION
@TGmention27 · 28711 postsproofs
@katunayan · 111 postsPounds Money Secrets
@poundsmoneysecrets · 2111 postsbaechu vouch
@baechu_vouch · 9910 posts두두둠강채널
@doomgang · 8518 postsPixars Cloud Vouches
@pixarscloudvouches · 3017 postsAerikai's proofs🧾 (formerly martymarion)
@aerikaiproofs · 206 postsViral videos
@yourviralvid · 16 postsmama
@hjdohjdrhjd · 15 postsXX & DEAR
@ffhvgdvdtgccccc · 24 postsmami
@hrdtawsT · 344 postsLink link
@LinkLinkNew · 2693 posts𝐃𝐔𝐃𝐀𝐘 𝐒𝐄𝐑𝐕𝐈𝐂𝐄𝐒 𝐯.𝟐
@dudayservices · 2353 postsMegamind Number
@megamind_number1 · 73 posts🍃Zaza Vouches 2.0🍃
@zazavouch · 373 postsJD's Projects [ADVERTS]
@AIOCAdverts · 3112 postsBOOM AND CRASH SCALPER SOFTWARE
@BOOMANDCRASHSCALPERSOFTWARE · 252 postsSCAMMERS SA TELE (LF ACTIVE ADMINS)
@IWASSCAM00 · 502 posts❤️18禁❤️總頻道
@beauty18_channel_hkgirl_nonstar · 1,8472 posts𝒄𝒉𝒆𝒗𝒂𝒃𝒊’𝒔 𝒗𝒐𝒖𝒄𝒉𝒆𝒔
@chevreceipts · 702 posts써킷
@circuit2025 · 182 postsLordpress
@lordpress_event · 742 posts🔞𝙈𝙊𝘼𝙉𝙄𝙉𝙂 𝘽𝙀𝘼𝙏𝙎💦
@moaningbeats · 5,2282 postsCREATIVE✒️ HUB💯💯
@naughtytee · 3442 posts𝖛𝖔𝖚𝖈𝖍 𝖟𝖔𝖓𝖊 II
@ndvouchpxayz · 32 postsTaxta savdo
@taxta5savdo · 142 postsDoping hafıza videoları doping hfz tyt PDF ayt PDF soru bankası PDF 9 10 11 12 sınıf videolar
@tytaytykspdfdoping · 5,2192 postsWhisper's Vouches
@whispersvouches · 12 posts𝐀𝐍𝐃𝐀𝐋𝐔𝐒
@ANDALUS_TEAM · 91 postНатяжные потолки
@Angren_remont · 931 postATOMY.uz
@Atomyuzbekistana · 401 postBooking Info / Requirements HUB
@B4U_Hotels · 1021 postChess Friends
@Chess_play · 1631 postALIENCAT VOUCHES NEW 👽
@aliencatttvouches · 3021 postانجمن علمی دانشکده داروسازی اردبیل
@anjomanpharums · 821 postA Shop Vouches🤩
@athingsvouches · 2111 postpasukan bucin
@bucinsemangatku12 · 61 post💎 Card Haven
@cardhaven · 2871 postDispatch & Menfess
@disfessneoaezone · 141 postD ;)
@dunyoy1msen2 · 21 post
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 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.
Named by
Channels on the register whose posts name this channel's handle.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ForwardsCoverBot” (@ForwardsCoverBot), 54,219 monthly users as measured 18 September 2026. Telegram Register, tgregister.com/channel/ForwardsCoverBot.
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.