Telegram RegisterThe public register of Telegram

Channel

JY 進源实物盘

@yeye

2 usernames

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

6,887subscribers

-18 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1001277077657
TypeChannel
Usernames@wanzhoudb8 @yeye
CreatedBetween 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/yeye

Growth

6,8876,9056,89611 Aug 2026, 18:17 — 6,905 subscribers11 Aug 2026, 18:30 — 6,905 subscribers12 Aug 2026, 07:31 — 6,898 subscribers12 Aug 2026, 16:04 — 6,887 subscribers11 Aug 2026, 18:1712 Aug 2026, 16:04
4 measurements taken within a single day, net -18. 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 6,884–6,908 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:046,887-11
12 Aug 2026, 07:316,898-7
11 Aug 2026, 18:306,905no change
11 Aug 2026, 18:176,905first reading

Engagement

20 posts held, back to 18 March 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
5.04%
avg views ÷ 6,887 subscribers
Avg views / post
347
3 posts measured
Reaction rate
0.856%
reactions ÷ views · ER floor
Posts in window
4
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 2 of 3 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 (18 March 20264 August 2026)
Views total1,041
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 06:33 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

6 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
350.0%
👍350.0%

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 5 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 6reactions 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 18 March 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, 10:40 UTC155 views3 reactionsread 12 August 2026

纯菠菜微信im 风口项目微信加好友不用通过 一个号干一个月不死号 单价2起 团队来谈 @JY186

👍3

19 Jul 2026, 04:34 UTC429 views2 reactionsread 12 August 2026

纯菠菜V推单价30团队来谈 全网最简单微信加好友推名片 通过之后简单聊两句添加了就算一单无需改资料 @JY186

2

18 Jul 2026, 05:39 UTCviews —

進源公告栏 pinned «纯绿色菠菜不死耗,不封号 1.业务类型:拉手 2.业务说明:推微信名片跟拉群 3.详细规则:本公群规则 一,具体业务:微信加好友 二,做单标准:找业务员预约数据,通过之后发话术拿名片二维码。 粉加上就算一单。秒删不算 扣单标准:违规处罚 1:炸群 炸鱼 群里拉其他不想干的人员进群待着(1扣10或者扣除该拉手做的单子) 2:骚扰:私下骚扰客户(1扣5) 3:刷子:做单人拿数据去刷话术二维码后台不结算全扣 4:假单:任何假单不结算 5:如果客服不能进群 需要配合加客服微信从新拉群 6,以上要求必须严格遵守…»

18 Jul 2026, 05:38 UTC457 viewsread 12 August 2026

纯绿色菠菜不死耗,不封号 1.业务类型:拉手 2.业务说明:推微信名片跟拉群 3.详细规则:本公群规则 一,具体业务:微信加好友 二,做单标准:找业务员预约数据,通过之后发话术拿名片二维码。 粉加上就算一单。秒删不算 扣单标准:违规处罚 1:炸群 炸鱼 群里拉其他不想干的人员进群待着(1扣10或者扣除该拉手做的单子) 2:骚扰:私下骚扰客户(1扣5) 3:刷子:做单人拿数据去刷话术二维码后台不结算全扣 4:假单:任何假单不结算 5:如果客服不能进群 需要配合加客服微信从新拉群 6,以上要求必须严格遵守,不符合直接不结算,自己的小弟看好教程规则。不接受任何扯皮。 7、撤回消息之前要截图报备不然则算无效单 四,交单标准:按照实时话务更新的来即可,未按照要求来算无效单。 格式:拉完群@客服,我让退群才退出群聊 联系客服报备做单: @JY186

29 Jun 2026, 08:13 UTC649 viewsread 12 August 2026

空降色 1-3存单1200招 小额99群转账车 不罚站 0风险 善后客户删账单 招实力稳定车队 不需要引导领钱就行 @JY186

26 Jun 2026, 10:29 UTC654 viewsread 12 August 2026

资金盘前中期保月司法 点位置顶 来丝滑微信支付宝码车 支持双压 @JY186

25 Jun 2026, 04:54 UTC663 viewsread 12 August 2026

招纯美团代收崩老头项目安全无司法,量大有店铺可以联系 @JY183

16 Jun 2026, 03:37 UTC927 viewsread 12 August 2026

空降色 1-3存单1200招 小额99群转账车 不罚站 0风险 善后客户删账单 招实力稳定车队 不需要引导 @JY186

28 May 2026, 09:30 UTC≈1,370 views0 reactionsread 12 August 2026

来支付宝经营收款单大车,保卸货,出现司法等问题不需要你承担,我方保你把钱卸出去后加分

19 May 2026, 05:16 UTC≈1,560 views1 reactionsread 12 August 2026

空降色 1-3存单1200招 小额99群转账车 不罚站 0风险 善后客户删账单 招实力稳定车队 不需要引导 @JY186

1

11 May 2026, 05:20 UTC≈1,700 viewsread 12 August 2026

空降色1-3存 招微信群转车 单笔3000内 车队来谈 量大不罚站 @JY186

22 Apr 2026, 06:52 UTC≈2,220 viewsread 12 August 2026

常规色直盘 招微信支付宝码专车笔笔维护删单 万内汇率11起实力车队来谈 量大不罚站 @JY186

Showing the 12 most recent of 20 posts we hold for @yeye. 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 — 516,432 of 1,160,990entries 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 2 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.

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

“JY 進源实物盘” (@yeye), 6,887 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/yeye.

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.