Telegram RegisterThe public register of Telegram
Telegram profile photo for no link | 链接拦截 🚫

Bot

no link | 链接拦截 🚫

@no_linking_bot

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

91,791monthly users

+17,922 since we began measuring on 7 August 2026

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

Register entry

Telegram ID7894808842
TypeBot
Username@no_linking_bot
First recorded11 August 2026
Last confirmed live5 September 2026
Measurements held16
Confirmed unchanged2 times, most recently 5 September 2026
On Telegramt.me/no_linking_bot

Growth

73,39892,48482,9417 August 2026 — 73,869 monthly users8 August 2026 — 74,360 monthly users9 August 2026 — 73,398 monthly users11 August 2026 — 73,398 monthly users11 August 2026 — 76,421 monthly users13 August 2026 — 79,125 monthly users16 August 2026 — 81,128 monthly users17 August 2026 — 83,575 monthly users19 August 2026 — 86,434 monthly users20 August 2026 — 87,534 monthly users23 August 2026 — 84,853 monthly users24 August 2026 — 88,021 monthly users27 August 2026 — 90,625 monthly users30 August 2026 — 92,146 monthly users1 September 2026 — 92,484 monthly users3 September 2026 — 91,791 monthly users91,7917 August 20263 September 2026
16 measurements spanning 28 days, net +17,922. 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 70,535–95,347 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
3 Sept 2026, 18:3891,791-693
1 Sept 2026, 13:0292,484+338
30 Aug 2026, 14:1592,146+1,521
27 Aug 2026, 14:1890,625+2,604
24 Aug 2026, 15:1688,021+3,168
23 Aug 2026, 00:3984,853-2,681
20 Aug 2026, 09:4687,534+1,100
19 Aug 2026, 11:4786,434+2,859
17 Aug 2026, 13:3883,575+2,447
16 Aug 2026, 07:4781,128+2,003
13 Aug 2026, 09:2479,125+2,704
11 Aug 2026, 07:1776,421+3,023
11 Aug 2026, 03:1273,398no change
9 Aug 2026, 08:2173,398-962
8 Aug 2026, 11:0474,360+491
7 Aug 2026, 02:1673,869first 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 6 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.

“no link | 链接拦截 🚫” (@no_linking_bot), 91,791 monthly users as measured 3 September 2026. Telegram Register, tgregister.com/channel/no_linking_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.