Telegram RegisterThe public register of Telegram
Telegram profile photo for An-Sherwood Forest🧙🏻

Channel

An-Sherwood Forest🧙🏻

@chenpingan2030

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

524subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003952126062
TypeChannel
Username@chenpingan2030
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/chenpingan2030

Growth

5225265247 August 2026 — 522 subscribers8 August 2026 — 522 subscribers8 August 2026 — 526 subscribers16 August 2026 — 524 subscribers7 August 202616 August 2026
4 measurements spanning 9 days, net +2. 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 521–527 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 16:04524-2
8 Aug 2026, 14:48526+4
8 Aug 2026, 04:02522no change
7 Aug 2026, 22:18522first reading

Engagement

20 posts held, back to 6 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
42.9%
avg views ÷ 524 subscribers
Avg views / post
225
20 posts measured
Reaction rate
2.54%
reactions ÷ views · ER floor
Posts in window
20
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 8 of 20 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 7 August 2026
Posts held20 (6 August 20267 August 2026)
Views total4,495
Reactions total46
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 04:02 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

46 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 43.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2043.5%
😭919.6%
😱715.2%
48.70%
👀48.70%
👏12.17%
🔥12.17%

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 8 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 46reactions 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 6 August 2026 to 7 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

7 Aug 2026, 18:39 UTC156 viewsread 8 August 2026
Photo

第一个叙事应该都知道了,第二个我附上一个图片,第三个的叙事我推特有发过 开链了我这三个也不一定是新的龙头(仅供参考)

Signed An

7 Aug 2026, 18:38 UTC160 viewsread 8 August 2026

重新更新一遍 ARC 这是目前的龙头 0x8bcb94279fc2c984ec34e0c1f2192df8c69ea4f0 下面这两个都是在关链之后阴谋做起来的 这个是创始人之前发的一张图片,还有经常说的词 0xacd3c4ae00ddac5cd857d83424cf4eb85f32ad8f 这个是类似现金猫 0x1570489708c328aa51ba8004c95a60e6f9f757e3 https://radardex.app/ 这个网站看线,用 大师可以交易 或者用OKX搜这个网站可以交易 ,这时候其实最大的黑马就是ARC了 在9.15开链之前都有可能有阴谋更换龙头,这是我目前唯一持仓的三个币了,平时也可以用这个网站多看看有没有新的阴谋涨起来

Signed An

7 Aug 2026, 15:54 UTC190 views1 reactionsread 8 August 2026

每次一有蹭币安的动物meme 果然NALA就会被鞭尸一下😂

😭1

Signed An

7 Aug 2026, 12:46 UTC202 views2 reactionsread 8 August 2026

补一条 币圈换仓补仓 币圈大忌 拆东补西

2

Signed An

7 Aug 2026, 11:52 UTC210 viewsread 8 August 2026

就今天休息了 每日一鳄 明天重新战斗

Signed An

7 Aug 2026, 09:25 UTC229 views26 reactionsread 8 August 2026

被现金猫套傻了,所以今天没上机趁机休息写了个复盘 告诫自己也希望对大家有所帮助 为什么写这个复盘? 现金猫回撤,让我rb—bsc这一轮的利润全部进去了 利润回撤永远是最令人难以接受的,目前被套状态,只能hold等待拉升然后跑 (我还是卖了火星币去补的仓,如果火星币突然上合约或者现货,心理冲击肯定一下会让我难以接受,提前复盘能做好心理防护盾) 我也不例外,既然在这个圈子,停下交易也是不可能的,我也是小卡拉咪,只能通过复盘去告诉自己为什么亏损,然后不断的告诉自己下次不犯,不断的强化自己的交易逻辑 1.fomo情绪影响,从rb—bsc这一轮身边太多赚钱的人了,然后自己也在赚(虽然没有别人能赚),不断叠加的fomo buff 在现金猫上现货的时候爆发,所以没有控制好,直接allin,想着翻倍一波大盈利 其实可以等今天再买 (达到预期,理所当然认为会继续上涨带动新一轮行情) 币圈本质上是以小资金去博弈,去撬动更大的资金池,然后吃掉其他比

👍15😭72👏1🔥1

Signed An

6 Aug 2026, 20:25 UTC248 views5 reactionsread 8 August 2026

草泥马现金猫😃 晕过去了

👀4😭1

Signed An

6 Aug 2026, 16:06 UTC259 viewsread 8 August 2026

BSC也玩不懂了 开始那几个大标如果没有上车的 剩下的基本都是PVP 分流 太恶心了 与叙事已经无关了 在BSC玩不能带脑子

Signed An

Showing the 12 most recent of 20 posts we hold for @chenpingan2030. 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 — 1,218,242 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 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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“An-Sherwood Forest🧙🏻” (@chenpingan2030), 524 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/chenpingan2030.

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.