Telegram RegisterThe public register of Telegram

Channel

XY的小窝

@BFYU91

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

2,821subscribers

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

Register entry

Telegram ID-1003951673200
TypeChannel
Username@BFYU91
Description小宇NB,LX解密作者
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held1
On Telegramt.me/BFYU91

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 23:312,821first reading

Engagement

18 posts held, back to 10 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
8.33%
avg views ÷ 2,821 subscribers
Avg views / post
235
18 posts measured
Reaction rate
1.94%
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 16 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 13 August 2026
Posts held18 (10 August 202613 August 2026)
Views total4,228
Reactions total70
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 23:31 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

Photos
29
Videos
1
Links
15

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

70 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 77.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5477.1%
👍1420.0%
🥰22.86%

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 16 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 70reactions 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 10 August 2026 to 13 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

13 Aug 2026, 22:31 UTC57 views1 reactionsread 13 August 2026
File

漏打教程公益漏打单自瞄 将游戏放置后台 开启注入 公益卡密258000 随意使用 原作者SunnySummer 请进入频道过频道验证 转发频道https://t.me/YouYu520

1

Signed 小 宇

13 Aug 2026, 22:14 UTC62 views2 reactionsread 13 August 2026

哈喽我是小宇,今天在我Q群的人应该知道发生什么事情了,现在讲点心里话吧,我入挂圈是在2024年4月7日,那一天我我当时拿着vivoy35+这个手机在快手直播,认识了一个叫小印的主播,我们都是45帧的设备,但是他的实力比我高的不是一点两点,他总是直播能收获特别多的粉丝,在这一刻我心生了嫉妒,我想着我为什么不能这么有实力,在下播的时候我问他为什么这么强,他告诉我多练,他教了我许多练技术的方法,但是我练了很久很久,还是一样菜,在到后面我发现他玩上了pak美化,我和他说我也想要,他告诉我了我一个叫TG的应用,我听了过后我去找了许多人,终于要到了TG,然后我得到了直装,在这一刻我入了挂圈,再到2025年1月9日,我进入了国体这个圈子,我结识了许多朋友和作者,经过他们的教学,我做出了第1款国体范围,做出来之后,我也是选择了公益,在第1场直播,我人数超出了最高人数,达到了1800人,看着屏幕右上角的人数,我的虚荣心得到了满足,这一刻我想着我要

2

Signed 小 宇

13 Aug 2026, 16:25 UTC103 views5 reactionsread 13 August 2026
Photo

这个UI和绘制怎么样 源码还是泛滥的 可以的话LX给你们搞这个 还是公益,饿死了都公益 准备搞外部模拟解密 来点❤️支持一下 小宇的心里话https://t.me/BFYU91/143

5

Signed 小 宇

13 Aug 2026, 12:30 UTC136 views17 reactionsread 13 August 2026

晚点发布一个001公益版 需要的来点爱心

17

Signed 小 宇

13 Aug 2026, 09:46 UTC159 views3 reactionsread 13 August 2026
File

三笙单解密【公益版】 已发布,纯属公益 卡密找我领取 领取卡密 @BFYU6

3

Signed 小 宇

12 Aug 2026, 21:44 UTC172 views5 reactionsread 13 August 2026

睡醒了,有点饿,但是没钱吃饭 所以我要回归范围了😁 不要喷我,公益一周

👍41

Signed 小 宇

12 Aug 2026, 14:58 UTC195 views5 reactionsread 13 August 2026

等会发布一下双笙,很多人玩的挺稳定的

4👍1

Signed 小 宇

12 Aug 2026, 12:58 UTC356 views1 reactionsread 13 August 2026
File

LX解密内核公益版 使用坐标解密😭 注意演戏 UI和绘制都是泛滥源码 会概率拉闸网波,封了别喷我 公益卡密在下方评论区 反馈联系 @BFYU6 公益版频道 @LXJieMi

👍1

Signed 小 宇

12 Aug 2026, 09:49 UTC208 views10 reactionsread 13 August 2026

有没有想玩双笙单解密的 来点赞给你们公益

👍73

Signed 小 宇

12 Aug 2026, 07:41 UTC369 views4 reactionsread 13 August 2026
File

天骄已破解,卡密随便输入 运行文件放到tmp里

3👍1

Signed 小 宇

11 Aug 2026, 16:07 UTC215 views2 reactionsread 13 August 2026

破解不收费,投稿就好了

🥰2

Signed 小 宇

Showing the 12 most recent of 18 posts we hold for @BFYU91. 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,337,788 of 1,345,403entries 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“XY的小窝” (@BFYU91), 2,821 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/BFYU91.

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.