Telegram RegisterThe public register of Telegram
Telegram profile photo for EPusdt

Channel

EPusdt

@epusdt

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

2,117subscribers

+35 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001722706052
TypeChannel
Username@epusdt
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/epusdt

Growth

2,0822,1172,099.57 August 2026 — 2,082 subscribers7 August 2026 — 2,082 subscribers8 August 2026 — 2,089 subscribers11 August 2026 — 2,102 subscribers14 August 2026 — 2,109 subscribers17 August 2026 — 2,117 subscribers7 August 202617 August 2026
6 measurements spanning 10 days, net +35. 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,077–2,122 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 20:062,117+8
14 Aug 2026, 14:552,109+7
11 Aug 2026, 12:582,102+13
8 Aug 2026, 09:102,089+7
7 Aug 2026, 09:462,082no change
7 Aug 2026, 09:362,082first reading

Engagement

20 posts held, back to 5 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
40.6%
avg views ÷ 2,117 subscribers
Avg views / post
860
13 posts measured
Reaction rate
0.294%
reactions ÷ views · ER floor
Posts in window
13
of 20 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. It is computed over the 7 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held20 (5 July 20264 August 2026)
Views total11,178
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:59 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.

Reaction mix

26 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1038.5%
👍519.2%
🥰415.4%
❤‍🔥311.5%
🤡311.5%
🔥13.85%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 11 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 26reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 5 July 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Aug 2026, 21:36 UTC567 views5 reactionsread 7 August 2026
Photo

全新设计的收银台,更现代,更好用,更丝滑

2🥰2🔥1

4 Aug 2026, 20:31 UTC538 viewsread 7 August 2026
Poll

您的生意模式

  1. 在发卡站中完成67%
  2. 在telegram群组或者机器人中完成28%
  3. 在tg中与客户沟通并在私聊中完成或者需要私聊提供后续服务26%

The shares total 121%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

1 Aug 2026, 06:22 UTC822 viewsread 7 August 2026

epusdt目前,由于自托管的扫链,公共节点不一定稳定,可以尝试购买付费节点,相关解决方案,下个月提供,需要准备时间

31 Jul 2026, 10:22 UTC814 viewsread 7 August 2026
Photo

tg小程序自动登录,再也不丢订单记录,方便客户自己查订单,减少客服量

30 Jul 2026, 11:58 UTC830 viewsread 7 August 2026

gm pay的设计希望提供归集功能,大家有什么建议吗,我们计划将base 币安币链来实现(基于大多数u商的实际采用情况)

29 Jul 2026, 16:16 UTC778 viewsread 7 August 2026

为激励生态发展,群内前十名部署完成GM Shop并实际上架商品的商家(真实商品并且可以购买),将获得10 TRX空投或者20TRX GM能量余额

29 Jul 2026, 15:59 UTC735 views4 reactionsread 7 August 2026

0学习成本 0资金成本 一键启动你的生意 可以对接群内各大发卡大佬货源,无论他是dujiao还是异次元 都可以对接!!! 开店就用GM Shop 项目开源地址 一键部署

4

29 Jul 2026, 15:46 UTC582 viewsread 7 August 2026

🚀 GMShop Edge 全新开源,邀您抢先体验 基于 Cloudflare Workers 构建的新一代自托管数字商品商城,一个 Worker 即可提供公开商城、客户中心、在线结算、自动交付与专业管理后台。 ✨ 一站式数字商品运营 全面覆盖商品管理、库存管理、订单处理、客户与权益、优惠券、退款售后、邮件通知、权限管理、任务队列、计划任务及审计日志等核心场景。 📦 支持多种数字商品 目前支持: - Stock:自动发放卡密、账号、激活码等预置库存 - Download:通过私有 R2 安全交付文件 - Automation:执行部署、脚本、资源开通与自动构建流程 🔄 支持上游商品与自动采购 已支持对接: - 异次元发卡 - 独角数卡 Next 可自动同步上游商品,并通过多账号池完成自动选号、采购、核验与统一交付。 💳 灵活的支付与计价体系 - 支持 Stripe、GMpay、EPay 等类型化支付适配器

27 Jul 2026, 14:05 UTC872 views3 reactionsread 7 August 2026

影响不大,不必过度恐慌,只是MD5加密方式不符合安全标准,仍然可以用,在目前的场景下利用的概率很低

🤡3

27 Jul 2026, 11:57 UTC≈1,020 views1 reactionsread 7 August 2026

由于epay接口存在潜在安全隐患,建议各生态合作伙伴,以最新gm pay对接 这个漏洞利用的可能性非常低,只是建议切换

👍1

24 Jul 2026, 21:24 UTC≈1,040 views3 reactionsread 7 August 2026

因为项目逐渐变多,本频道和本群将于近期更名为 GM开源技术交流群

❤‍🔥3

22 Jul 2026, 04:49 UTC≈1,310 views2 reactionsread 7 August 2026

https://x.com/GMWallet/status/2079782001125839030 抽奖2000TRX

👍2

Showing the 12 most recent of 20 posts we hold for @epusdt. 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.

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Aug 2026, 20:31 UTCAnonymous Poll46 voters

您的生意模式

  1. 在发卡站中完成67%
  2. 在telegram群组或者机器人中完成28%
  3. 在tg中与客户沟通并在私聊中完成或者需要私聊提供后续服务26%

The shares total 121%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

5 Jul 2026, 16:06 UTCAnonymous Poll91 voters

您是否觉得管理多链并支持多种资产比较麻烦

  1. 很麻烦,希望归集54%
  2. 其实多个链也很不错46%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 5 July 2026 to 4 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 687,079 of 1,481,306entries 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 4 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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“EPusdt” (@epusdt), 2,117 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/epusdt.

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.