Telegram RegisterThe public register of Telegram
Telegram profile photo for 香蕉🍌(手抓数据号)

Channel

香蕉🍌(手抓数据号)

@xjsgp

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

67subscribers

+18 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-1003823812073
TypeChannel
Username@xjsgp
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 October 2026
Last confirmed live10 October 2026
Measurements held8
On Telegramt.me/xjsgp

Growth

497461.57 August 2026 — 49 subscribers8 August 2026 — 54 subscribers14 August 2026 — 74 subscribers29 August 2026 — 73 subscribers6 September 2026 — 71 subscribers14 September 2026 — 70 subscribers9 October 2026 — 67 subscribers10 October 2026 — 67 subscribers677 August 202610 October 2026
8 measurements spanning 64 days, net +18. 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 45–78 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 22:2367no change
9 Oct 2026, 02:5667-3
14 Sept 2026, 19:5570-1
6 Sept 2026, 10:1671-2
29 Aug 2026, 08:4473-1
14 Aug 2026, 22:0874+20
8 Aug 2026, 00:0854+5
7 Aug 2026, 12:1749first reading

Engagement

20 posts held, back to 8 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
31.5%
avg views ÷ 67 subscribers
Avg views / post
21.1
10 posts measured
Reaction rate
7.79%
reactions ÷ views · ER floor
Posts in window
10
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 5 of 10 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 October 2026
Posts held20 (8 August 2026 – 7 October 2026)
Views total211
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Oct 2026, 22:23 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
9
Links
8

Lifetime counters from Telegram’s own channel header, read 10 October 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

36 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍925.0%
😢411.1%
🤔411.1%
❤38.33%
🎉38.33%
👏38.33%
🔥38.33%
🤮38.33%
👎25.56%
🤝25.56%

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 12 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 36 reactions 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 8 August 2026 to 7 October 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 Oct 2026, 07:48 UTC5 views1 reactionsread 10 October 2026
File

秋叶公益软件版拦截 适配无root用户 采用新思路 推荐使用半火游玩 一一一一一一一一一一一一 更新日期:10.7 全新规则 适配1.38 作者:秋叶 无卡密验证 局内开启 半离线拦截 发布频道: @QIUIENB6 反馈联系: @K78NB

👍1

5 Oct 2026, 06:01 UTC6 views2 reactionsread 10 October 2026
File

🐕🐕🐕全网首个无需改机型模块拦截防火墙断点gcloud解决加载人脸 10.3更新 更新内容:增加清理 点我查看效果视频 点我提卡 点我提卡 点我提卡 点我提卡 发布频道 @QIUIENB6 上飞机之后直接大退即可 解绑链接

👍2

4 Oct 2026, 17:18 UTC11 views1 reactionsread 10 October 2026
File

更新时间:2026年10月5日 更新内容:优化UI流畅度、优化CPU占用、增加过渡动画、优化UI、增加算法解密无视闪框 ps:请在桌面执行出悬浮窗后再打开游戏 tis:此项目耗费了我大量精力时间金钱也希望各位能游玩一下制作耗时三天项目维护啥的也是需要精力金钱这次公益给你们 主要亮点:内核级触摸连点器、内核及触摸自瞄、陀螺仪自瞄、内置算法解密无视偏框、非常多半火功能如:微加速、自定义射速、自定义据点、超大范围等以及内核级触摸连点器搭配鬼手天赋秒开箱 key: QIUIENB6 支持上分、地铁偷箱、地铁猛攻 全部功能支持裸奔(范围未知) 4系用户推荐刷入内置驱动5系及以上用户推荐刷入天堂驱动如果不能刷驱动还支持纯C读取所以支持虚拟机 使用效果展示视频 有问题反馈 @K78NB

👍1

2 Oct 2026, 08:44 UTC16 viewsread 10 October 2026
File

🌟秋叶赞助版iptables全火C++拦截6.0🌟 🚀采用新思路 —————— 10.2更新 💰收费版比公益版更稳定。 ✅全新规则,适配1.38。 👤作者:秋叶 更新内容:防超体全火内置局内判断无需频繁手动交互局内自动开启并放行10012、17500等端口 支持半火上分、全火 📢发布频道:@QIUIENB6 💬反馈联系:@K78NB 💸赞助点我:点我 🔓解绑点我:点我

25 Sept 2026, 04:53 UTC32 views1 reactionsread 10 October 2026
File

🐕🐕🐕全网首个无需改机型模块拦截防火墙断点gcloud解决加载人脸 点我查看效果视频 点我提卡 点我提卡 点我提卡 点我提卡 发布频道 @QIUIENB6

👍1

19 Sept 2026, 03:40 UTC32 viewsread 10 October 2026
File

秋叶sh全防 采用修改器新思路 最后更新:9.19 伪切后台状态、gclod上报 支持:刷刀、全火、半火上分 一一一一一一一一一一一一一一一一 全新C++写法 适配1.38 作者:秋叶 无卡密验证 发布频道: @QIUIENB6 反馈联系: @K78NB 🆘玩了不反馈死全家🆘 😀玩了不反馈死全家😀 🆘玩了不反馈死全家🆘 一一一一一一一一一一一一一一一一 目前已公益 使用方法:桌面执行既可无悬浮窗

Showing the 12 most recent of 20 posts we hold for @xjsgp. 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.

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.

Mentions

Named by 2 registered channels — 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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“香蕉🍌(手抓数据号)” (@xjsgp), 67 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/xjsgp.

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.