Telegram RegisterThe public register of Telegram
Telegram profile photo for 飞鱼支付-通知频道

Channel

飞鱼支付-通知频道

@feiyu52011

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

1,304subscribers

-14 since we began measuring on 16 August 2026

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

Register entry

Telegram ID-1003570718445
TypeChannel
Username@feiyu52011
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live17 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/feiyu52011

Growth

1,3041,3181,31116 Aug 2026, 19:15 — 1,318 subscribers16 Aug 2026, 19:30 — 1,318 subscribers17 Aug 2026, 19:57 — 1,304 subscribers16 Aug 2026, 19:1517 Aug 2026, 19:57
3 measurements spanning 1 day, net -14. 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,302–1,320 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 19:571,304-14
16 Aug 2026, 19:301,318no change
16 Aug 2026, 19:151,318first reading

Engagement

20 posts held, back to 14 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
14.8%
avg views ÷ 1,304 subscribers
Avg views / post
194
20 posts measured
Reaction rate
this channel exposes no reaction counts
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 August 2026
Posts held20 (14 August 202616 August 2026)
Views total3,871
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Aug 2026, 19:30 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.

Recent posts

16 Aug 2026, 15:33 UTC134 viewsread 16 August 2026

❗️通道维护 老铁们 明早八点开启 ❗️ ❗️通道维护 老铁们 明早八点开启 ❗️ ❗️通道维护 老铁们 明早八点开启 ❗️

16 Aug 2026, 03:26 UTC223 viewsread 16 August 2026
Photo

联通200码子爆满 橙绿依旧稳定80+ 无视并发 开启多加加量 宝们🇮🇶🇮🇶🇮🇶🇮🇶

16 Aug 2026, 02:27 UTC189 viewsread 16 August 2026
Photo

🥰8018联通原生 🥰8028联通原生固额200 200码子充足 橙绿依旧稳定 来点并发 宝们

16 Aug 2026, 00:50 UTC173 viewsread 16 August 2026
Photo

🥰8018联通原生 🥰8028联通原生固额100 200 200金额码子很足 橙绿还不错 来点并发宝子们➡️➡️➡️

16 Aug 2026, 00:27 UTC164 viewsread 16 August 2026
Photo

🥰8018联通原生 🥰8028联通原生固额200 200金额码子很足 橙绿还不错哦 宝子们开启多冲冲

15 Aug 2026, 23:45 UTC167 viewsread 16 August 2026
Photo

8月16日8点0分 编码8️⃣0️⃣1️⃣8️⃣🥰联通支付宝原生 费率调整为 1️⃣6️⃣⏹5️⃣ 8月16日8点0时 编码8️⃣0️⃣2️⃣8️⃣🥰联通支付宝固额原生100 200金额 费率调整为 1️⃣6️⃣⏹5️⃣ 8月16日8点0时 编码8️⃣0️⃣2️⃣0️⃣🥰微信联通原生 费率调整为 1️⃣6️⃣⏹5️⃣ 宝子们 早上八点准时开启 记得同步下费率 开启 默认接受❗️❗️❗️ 宝子们 早上八点准时开启 记得同步下费率 开启 默认接受❗️❗️❗️ 宝子们 早上八点准时开启 记得同步下费率 开启 默认接受❗️❗️❗️

15 Aug 2026, 15:57 UTC191 viewsread 16 August 2026

❗️通道维护 老铁们 明早八点开启 ❗️ ❗️通道维护 老铁们 明早八点开启 ❗️ ❗️通道维护 老铁们 明早八点开启 ❗️

15 Aug 2026, 03:29 UTC263 viewsread 16 August 2026
Photo

联通200码子依旧爆满 橙绿拉满 无视并发⚡️⚡️⚡️

15 Aug 2026, 03:09 UTC218 viewsread 16 August 2026
Photo

联通200码子爆满 橙绿依旧稳定80+ 无视并发 开启多加加量 宝们🇮🇶🇮🇶🇮🇶🇮🇶

15 Aug 2026, 02:45 UTC185 viewsread 16 August 2026
Photo

🥰8018联通原生 🥰8028联通原生固额200 200码子充足 橙绿依旧稳定 来点并发 宝们

Showing the 12 most recent of 20 posts we hold for @feiyu52011. 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,499,851 of 1,549,376entries 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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“飞鱼支付-通知频道” (@feiyu52011), 1,304 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/feiyu52011.

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.