Telegram RegisterThe public register of Telegram
Telegram profile photo for EnvoyMeds

Channel

EnvoyMeds

@envoymeds1

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

3subscribers

+0 since we began measuring on 20 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004239442734
TypeChannel
Username@envoymeds1
Created14 August 2026measured — dated from the channel’s first post
First recorded20 August 2026
Last confirmed live27 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 27 August 2026
On Telegramt.me/envoymeds1

Growth

320 Aug 2026, 09:00 — 3 subscribers20 Aug 2026, 17:35 — 3 subscribers20 Aug 2026, 09:0020 Aug 2026, 17:35
2 measurements taken within a single day. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 17:353no change
20 Aug 2026, 09:003first reading

Engagement

8 posts held, back to 14 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
66.7%
avg views ÷ 3 subscribers
Avg views / post
2.0
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 8 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 August 2026
Posts held8 (14 August 202620 August 2026)
Views total14
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 09:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

20 Aug 2026, 05:01 UTC2 viewsread 20 August 2026

📌 猴痘 HIV:猴痘高度“盯上”HIV感染人群 猴痘 HIV:猴痘高度“盯上”HIV感染人群:全球约40%猴痘患者合并HIV感染,共感染住院风险+50%、死亡风险4.54倍。解读共感染风险、两大核心原因及HIV感染者专属防控提醒… 🔗 https://envoymeds.com/archives/6298

19 Aug 2026, 12:12 UTC2 viewsread 20 August 2026

📌 耐药 – 一种全新机制的 HIV 药,成了耐药患者的救命稻草 NHS 英格兰正式为对现有药物都耐药、几乎无药可用的 HIV 患者引入全新机制的 lenacapavir(来那卡帕韦)。它直接攻击病毒衣壳,为多重耐药患者带来救命稻草… 🔗 https://envoymeds.com/archives/6317

18 Aug 2026, 09:07 UTC2 viewsread 20 August 2026

📌 HIV 治疗性疫苗:全球首个HIV治疗性疫苗ICVAX,签约无锡了 HIV 治疗性疫苗:全球首个进入临床试验的艾滋病治疗性核酸疫苗ICVAX签约无锡,入选国家十五五重大科技专项。本文深扒其PD-1增强型DNA疫苗原理、港大血统、产业化历程与距离现实的距离… 🔗 https://envoymeds.com/archives/6314

17 Aug 2026, 05:39 UTC2 viewsread 20 August 2026

📌 HIV毒株 – 你我毒株不一样丨135人11种HIV毒株!耐药突变总检出率32.59% HIV毒株:青岛MSM新发HIV感染者病毒测序发现11种毒株,耐药突变总检出率32.59%,新型重组毒株与耐药聚集传播值得警惕… 🔗 https://envoymeds.com/archives/6288

16 Aug 2026, 06:04 UTC2 viewsread 20 August 2026

📌 终结艾滋病:盖茨发文称,终于相信艾滋病能被终结了 比尔·盖茨发文称终于相信艾滋病能被终结:长效预防针剂来那卡帕韦、基因编辑功能性治愈,加上基层医疗网络,让终结艾滋病从口号变成可触及的未来… 🔗 https://envoymeds.com/archives/6287

14 Aug 2026, 20:23 UTC2 viewsread 20 August 2026

📌 治疗即预防 – 应当告知所有医生和感染者:什么是治疗即预防与U=U 治疗即预防(TasP)与U=U:HIV感染者接受抗病毒治疗,将病毒载量维持在<200拷贝/mL并持续抑制,可预防HIV性行为传播。本文整理自美国DHHS指南,详解7条核心推荐、TasP与U=U的科学边界、病毒学闪现,以及安全套+PrEP+PEP的完整预防链… 🔗 https://envoymeds.com/archives/6273

14 Aug 2026, 20:17 UTC2 viewsread 20 August 2026

📌 HIV 感染者外表:能从外表看出来一个人感染了艾滋吗 HIV 感染者外表:能否从外表判断一个人是否感染HIV?答案是:不能。大多数HIV感染者没有任何症状,外表与普通人毫无差别。确诊只能依靠实验室检测。本文详解HIV感染三阶段、检测窗口期,以及高危暴露后的72小时黄金阻断与正确预防方式… 🔗 https://envoymeds.com/archives/6242

Showing the 8 most recent of 8 posts we hold for @envoymeds1. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 300,603 of 1,623,166entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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 20 August 2026 — this entry's latest reading, not the date you are reading this.

“EnvoyMeds” (@envoymeds1), 3 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/envoymeds1.

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.