Telegram RegisterThe public register of Telegram
Telegram profile photo for 【淫河舰甄选】入会系统

Bot

【淫河舰甄选】入会系统

@yinhejianbot

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

13,697monthly users

-7,628 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID8688673110
TypeBot
Username@yinhejianbot
First recorded16 August 2026
Last confirmed live3 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/yinhejianbot

Previous handles

@yinhejianbot was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@yinhejianbot
held 16 August 202616 August 2026

Growth

13,69721,32517,5116 August 2026 — 21,325 monthly users7 August 2026 — 20,356 monthly users10 August 2026 — 20,019 monthly users13 August 2026 — 19,868 monthly users16 August 2026 — 19,303 monthly users16 August 2026 — 19,303 monthly users18 August 2026 — 19,024 monthly users21 August 2026 — 17,797 monthly users25 August 2026 — 16,371 monthly users26 August 2026 — 15,690 monthly users30 August 2026 — 14,289 monthly users3 September 2026 — 13,697 monthly users6 August 20263 September 2026
12 measurements spanning 28 days, net -7,628. 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 12,553–22,469 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
3 Sept 2026, 22:3613,697-592
30 Aug 2026, 17:1314,289-1,401
26 Aug 2026, 13:3515,690-681
25 Aug 2026, 16:0316,371-1,426
21 Aug 2026, 09:3817,797-1,227
18 Aug 2026, 16:1719,024-279
16 Aug 2026, 20:2519,303no change
16 Aug 2026, 15:5619,303-565
13 Aug 2026, 13:5719,868-151
10 Aug 2026, 15:2720,019-337
7 Aug 2026, 15:1220,356-969
6 Aug 2026, 22:4521,325first 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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“【淫河舰甄选】入会系统” (@yinhejianbot), 13,697 monthly users as measured 3 September 2026. Telegram Register, tgregister.com/channel/yinhejianbot.

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.