Telegram RegisterThe public register of Telegram
Telegram profile photo for Catch Your Waifu

Bot

Catch Your Waifu

@Catch_Your_Waifu_Bot

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

19,242monthly users

+2,146 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 ID6883098627
TypeBot
Username@Catch_Your_Waifu_Bot
First recorded17 August 2026
Last confirmed live5 September 2026
Measurements held17
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/Catch_Your_Waifu_Bot

Growth

17,09619,28418,1907 August 2026 — 17,096 monthly users8 August 2026 — 17,187 monthly users11 August 2026 — 17,438 monthly users13 August 2026 — 17,648 monthly users14 August 2026 — 17,722 monthly users16 August 2026 — 17,761 monthly users17 August 2026 — 17,578 monthly users17 August 2026 — 17,578 monthly users18 August 2026 — 18,373 monthly users20 August 2026 — 18,046 monthly users21 August 2026 — 18,518 monthly users24 August 2026 — 18,874 monthly users25 August 2026 — 19,083 monthly users27 August 2026 — 18,790 monthly users29 August 2026 — 19,284 monthly users1 September 2026 — 19,276 monthly users5 September 2026 — 19,242 monthly users19,2427 August 20265 September 2026
17 measurements spanning 29 days, net +2,146. 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 16,768–19,612 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
5 Sept 2026, 04:3619,242-34
1 Sept 2026, 02:3619,276-8
29 Aug 2026, 22:2419,284+494
27 Aug 2026, 18:4418,790-293
25 Aug 2026, 14:2319,083+209
24 Aug 2026, 11:3518,874+356
21 Aug 2026, 15:0618,518+472
20 Aug 2026, 14:0218,046-327
18 Aug 2026, 14:5318,373+795
17 Aug 2026, 17:4617,578no change
17 Aug 2026, 12:4917,578-183
16 Aug 2026, 04:2317,761+39
14 Aug 2026, 16:0517,722+74
13 Aug 2026, 04:5817,648+210
11 Aug 2026, 01:0717,438+251
8 Aug 2026, 20:5217,187+91
7 Aug 2026, 14:4217,096first 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 3 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Catch Your Waifu” (@Catch_Your_Waifu_Bot), 19,242 monthly users as measured 5 September 2026. Telegram Register, tgregister.com/channel/Catch_Your_Waifu_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.