Telegram RegisterThe public register of Telegram
Telegram profile photo for Yueya fnf

Channel

Yueya fnf

@yueya_fnf

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

4,376subscribers

+142 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002227950478
TypeChannel
Username@yueya_fnf
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/yueya_fnf

Growth

4,2344,3764,3057 August 2026 — 4,234 subscribers7 August 2026 — 4,234 subscribers10 August 2026 — 4,279 subscribers13 August 2026 — 4,274 subscribers17 August 2026 — 4,376 subscribers7 August 202617 August 2026
5 measurements spanning 10 days, net +142. 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 4,213–4,397 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 12:234,376+102
13 Aug 2026, 17:574,274-5
10 Aug 2026, 21:014,279+45
7 Aug 2026, 23:044,234no change
7 Aug 2026, 22:184,234first reading

Engagement

18 posts held, back to 30 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 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
19.0%
avg views ÷ 4,376 subscribers
Avg views / post
830
18 posts measured
Reaction rate
0.825%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 17 of 18 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 8 August 2026
Posts held18 (30 July 20268 August 2026)
Views total14,941
Reactions total115
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:01 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

115 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 77.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8977.4%
😭108.70%
🤣65.22%
😨32.61%
💋21.74%
💩21.74%
😁21.74%
🥰10.87%

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 17 of the 18 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 115reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 30 July 2026 to 8 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

8 Aug 2026, 02:32 UTC332 views2 reactionsread 8 August 2026

纯交易者视角: 既没有 FOMO 股权,也没有 Pump.fun 股权, 从利益角度,Pump.fun 赢对你更有利。 原因很简单: Pump.fun 有流动性 Token,你能直接参与它成功带来的上涨; FOMO 如果赢了,大部分价值最终只会沉淀到少数股权持有人手里。

2

Signed Yueya| I will never DM u

7 Aug 2026, 06:38 UTC505 views3 reactionsread 8 August 2026

NFT工具 mintgo.fun waypoint.tools/mintscan/

3

Signed Yueya| I will never DM u

6 Aug 2026, 14:42 UTC651 views3 reactionsread 8 August 2026

如果你预期某个重大事件会导致市场流动性大幅下降(比如美联储讲话、CPI、战争消息、监管消息等),通常最好快速降低风险敞口。 尤其是那些: 当天涨了很多的币; 已经被市场炒高的币; 一旦恐慌容易被砸的币。 因为这些币往往在风险事件发生时跌得最狠

3

Signed Yueya| I will never DM u

6 Aug 2026, 14:24 UTC651 views5 reactionsread 8 August 2026

现在币圈最变态的就是纯赌博 ,没有人能根据因为所以 讲出为什么涨,根据分析项目基本面和前景啥的

5

Signed Yueya| I will never DM u

6 Aug 2026, 13:55 UTC678 views6 reactionsread 8 August 2026

最近不操作了,多学多看!老师们带带我吧

🤣6

Signed Yueya| I will never DM u

6 Aug 2026, 13:53 UTC687 views8 reactionsread 8 August 2026

失败了,是我想太多了😢,没有知行合一,还是得跟着大哥的步伐走,走歪了

5😨3

Signed Yueya| I will never DM u

4 Aug 2026, 21:56 UTC873 views7 reactionsread 8 August 2026

币安最近最强的热点之一,就是股票 Meme 交易对 目前 BSC 发射台上,Nvidia 股票配对是热度最高的方向之一;SpaceX 题材里,体量最大的代表则是 MarsCoin。 STARMIND 的优势在于,它同时叠加了两条最强叙事:一边分红 Nvidia 股票,一边分红 SpaceX 股票,同时部署在 BSC,天然承接币安股票 Meme 的资金和流量。 它同时覆盖了 Nvidia、SpaceX、太空 AI、股票 Meme 和 BSC 五层热点。随着 SpaceX 正式公布 Starmind 计划,这个币也成为当前市场里少数能够同时代表 SpaceX 与 Nvidia 合作叙事的 Meme 标的。 后续只要 SpaceX、Elon 或 Nvidia 再次提到 Starmind,市场注意力就可能迅速回流

7

Signed Yueya| I will never DM u

4 Aug 2026, 20:03 UTC819 views3 reactionsread 8 August 2026

https://x.com/cb_doge/status/2084727647465062537?s=46

3

Signed Yueya| I will never DM u

4 Aug 2026, 20:03 UTC753 views2 reactionsread 8 August 2026
Photo

0x98f09871a423d068a456b29bedf3f40368a17777 马斯克+黄仁勋+币安币股 如果不分流 这个叙事蛮好的,目前700k

💩2

Signed Yueya| I will never DM u

4 Aug 2026, 18:58 UTC762 views8 reactionsread 8 August 2026
Photo

yueya的degen之路只剩下100u了,我们能赢吗😭 https://fomo.family/r/yueya_eth

😭62

Signed Yueya| I will never DM u

4 Aug 2026, 13:30 UTC805 views6 reactionsread 8 August 2026

大哥说了才能买

6

Signed Yueya| I will never DM u

3 Aug 2026, 07:10 UTC946 views7 reactionsread 8 August 2026
Photo

Photo, posted without a caption

7

Signed Yueya| I will never DM u

Showing the 12 most recent of 18 posts we hold for @yueya_fnf. 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 — 858,388 of 1,481,502entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

“Yueya fnf” (@yueya_fnf), 4,376 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/yueya_fnf.

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.