Telegram RegisterThe public register of Telegram
Telegram profile photo for 越风集团-信誉至上

Channel

越风集团-信誉至上

@yuefeng8

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

1,335subscribers

-55 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-1001540230788
TypeChannel
Username@yuefeng8
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/yuefeng8

Growth

1,3351,3901,362.57 August 2026 — 1,390 subscribers8 August 2026 — 1,386 subscribers11 August 2026 — 1,370 subscribers14 August 2026 — 1,361 subscribers18 August 2026 — 1,350 subscribers20 August 2026 — 1,342 subscribers24 August 2026 — 1,337 subscribers27 August 2026 — 1,335 subscribers7 August 202627 August 2026
8 measurements spanning 20 days, net -55. 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 1,327–1,398 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 13:261,335-2
24 Aug 2026, 21:241,337-5
20 Aug 2026, 20:481,342-8
18 Aug 2026, 03:521,350-11
14 Aug 2026, 20:431,361-9
11 Aug 2026, 15:141,370-16
8 Aug 2026, 18:211,386-4
7 Aug 2026, 23:481,390first reading

Engagement

18 posts held, back to 30 June 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
4.29%
avg views ÷ 1,335 subscribers
Avg views / post
57.3
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held18 (30 June 20265 August 2026)
Views total172
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:48 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.

What this channel posts

Video runtime
13s
Average length
13s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 2 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 1reactions 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 June 2026 to 5 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

3 Aug 2026, 07:19 UTC68 viewsread 7 August 2026
Photo

泰达正式开启注册 8月5日上午九点开放充提 无分红模式注册链接: https://888.tdyule62.com/reg/IXW31R 分红模式注册链接: https://888.tdyule62.com/reg/74X3NU ———————————— ✯ 泰 达 ✯ ➤ 国內线路: https://666.tdyule8444.com https://666.tdyule4141.com https://666.tdyule9289.com https://666.tdyule6443.com https://666.tdyule5451.com ➤ 海外线路: https://888.tdyule62.com https://888.tdyule19.com https://888.tdyule06.com https://888.tdyule66.com https://888.tdyule49.com

28 Jul 2026, 11:59 UTC118 viewsread 7 August 2026

虚拟币最新充值方式 比如点击申请充值1000 他会提示你转账999.52类似 一样要按照提示转账小数点切记 不然不会自动到账的 用户只要提单一次就知道固定有小数点的 新方式会比较安全合理回查的时候也比较明确

21 Jul 2026, 11:22 UTC214 views1 reactionsread 7 August 2026

A模式分红线路 待遇为2000+实时反水0.5%+ 日结+综合佣金+月分红15%-25% B模式无分红线路 待遇为2000+实时反水0.6%+日结+综合佣金 综合佣金解析: 系统先计算团队每个会员当天产生的: 权重工资+效益工资=综合佣金总额 再根据团队累计的总权重值,自动匹配综合佣金发放比例: 团队权重15:发放20% 团队权重35:发放40% 团队权重75:发放60% 团队权重150:发放80% 团队权重300:发放100% 例如,团队当天产生: 权重工资:1000元 效益工资:500元 综合佣金:1500元 团队总权重:75 权重75对应发放60%,最终发放: 1500元 × 60%=900元

1

20 Jul 2026, 13:23 UTC196 viewsread 7 August 2026

开启预留! 当天开业盈利拿35万奖金 无盈利扶持领取588到18888

10 Jul 2026, 09:41 UTC260 viewsread 7 August 2026

汇众更新通知: 1:电脑网页/手机网页/APP/小程序投注偏好设置更新为根据偏好币种作为基础计价依据。 2:手机网页/APP/小程序更新投注倍数新/旧切换,旧模式为蓝图倍数逻辑。 网页版刷新即可,APP需重新下载。

Showing the 12 most recent of 18 posts we hold for @yuefeng8. 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 — 469,108 of 1,621,754entries 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“越风集团-信誉至上” (@yuefeng8), 1,335 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/yuefeng8.

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.