Telegram RegisterThe public register of Telegram

Bot

Sci-Hub

@scihubot

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

47,200monthly users

-228 since we began measuring on 5 August 2026

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

Register entry

Telegram ID162917195
TypeBot
Username@scihubot
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held6
On Telegramt.me/scihubot

Growth

47,20047,98347,591.55 August 2026 — 47,428 monthly users7 August 2026 — 47,849 monthly users8 August 2026 — 47,983 monthly users10 August 2026 — 47,613 monthly users12 August 2026 — 47,200 monthly users12 August 2026 — 47,200 monthly users5 August 202612 August 2026
6 measurements spanning 7 days, net -228. 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 47,083–48,100 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
12 Aug 2026, 17:0947,200no change
12 Aug 2026, 10:4847,200-413
10 Aug 2026, 09:4047,613-370
8 Aug 2026, 09:3647,983+134
7 Aug 2026, 08:4647,849+421
5 Aug 2026, 22:1147,428first 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

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 10 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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Hacker News

This handle was named 4 times in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Sci-Hub” (@scihubot), 47,200 monthly users as measured 12 August 2026. Telegram Register, tgregister.com/channel/scihubot.

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.