Channel
@fshan103
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
3,087subscribers
+31 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002703575320 |
|---|---|
| Type | Channel |
| Username | @fshan103 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/fshan103 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 05:36 | 3,087 | +31 |
| 6 Aug 2026, 21:15 | 3,056 | no change |
| 6 Aug 2026, 21:04 | 3,056 | first reading |
22 posts held, back to 20 June 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 3 pagesof Telegram’s post history, 20 posts per page.
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 7 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 22 (20 June 2026 – 7 August 2026) |
| Views total | 3,206 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00:00 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.
6 reactions across 6 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.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 8 of the 22 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 20 June 2026 to 7 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.
🎉 无敌暴龙战士 @Xxiao0720 派福利啦 🎁 奖品清单 • 美式☕19.9元 × 10 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 抽奖专栏 • 加入 修车出击大队推广轮播群 • 加入 小小❤️小屋 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言19次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-08-10 19:00:00 📜 抽奖说明 🈲 自言自语 脚本凑数 左右互搏 满屏盖楼 兑奖联系 @Xxiao0720 ✨ 愿好运伴随每一位参与者，祝大家好运！
🎉 禅城 @mao7676 P半价 🎁 奖品清单 • P半价 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 小懒猫的小家🏘️ • 加入 修车出击大队推广轮播群 • 加入 抽奖专栏 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-08-10 14:00:00 📜 抽奖说明 1 本活动不兑现 炸号无效 兑奖联系 @mao7676 2 自开奖日7天内有效，老师因个人原因需延长有效期！ 3 半价券需提交出击报告，已开启中奖选手自动拉黑，提交报告即解除！ ✨ 愿好运伴随每一位参与者，祝大家好运！
🎉 禅城 @xiyangyang52066 P半价 🎁 奖品清单 • P半价 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 禅城 喜洋洋 🉑外 • 加入 修车出击大队推广轮播群 • 加入 抽奖专栏 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-08-09 20:00:00 📜 抽奖说明 1 本活动不兑现 炸号无效 兑奖联系 @xiyangyang52066 2 自开奖日7天内有效，老师因个人原因需延长有效期！ 3 半价券需提交出击报告，已开启中奖选手自动拉黑，提交报告即解除！ ✨ 愿好运伴随每一位参与者，祝大家好运！
🎉 热心又帅气的师兄派福利啦 🎁 奖品清单 • 卤蛋2.88元 × 10 • 鸡腿6.66元 × 5 • 标准版猪脚饭18.88元 × 3 • 豪华版猪脚饭28.88元 × 3 • 顶配版猪脚饭50元 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 抽奖专栏 • 加入 玉哥的出击心得与日记🍀 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-08-12 15:30:00 📜 抽奖说明 🈲 自言自语 左右互搏 满屏盖楼 脚本凑数 兑奖联系 @verdant55440 ✨ 愿好运伴随每一位参与者，祝大家好运！
🎉 大沥小小 @Xxiao0720 优惠福利 🎁 奖品清单 • P半价 × 1 • P - 100优惠券 × 5 • PP - 200优惠券 × 3 • 🧧9.9 × 10 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 小小❤️小屋 • 加入 修车出击大队推广轮播群 • 加入 抽奖专栏 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-08-09 14:00:00 📜 抽奖说明 1 半价/课费优惠不兑现，🧧兑现，炸号无效，兑奖联系 @Xxiao0720 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 半价券需提交出击报告！ 中奖选手已开启自动拉黑抽奖…
🎉 乐沙儿白嫖/优惠券 🎁 奖品清单 • 普通P白嫖劵 × 1 • 300通用优惠券 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 魅魔.骚货.服务天花板.潮喷.SM.剧情.野战.车震.露出.av浴.艳舞.乐沙儿姐姐的后宫男宠🫧 • 加入 抽奖专栏 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：无限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-08-08 14:00:00 📜 抽奖说明 1 本次活动不兑现，炸号无效，兑奖联系 @lesha44133 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 白嫖券需提交出击报告！ 白嫖中奖选手已开启自动拉黑抽奖，提交报告即解除 ✨ 愿好运伴随每一…
❤1
✨ 命运揭晓时刻 ✨ 禅城香香 @xiang2678 半价 开奖了 抽奖人数：42，发言达标人数：14，抽奖号数：81 1. KFC在逃土豆泥【祝福11次】 中得：P半价 抽奖说明： 1 本次活动不兑现，炸号无效，兑奖联系 @xiang2678 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 半价券需提交出击报告 🔍 杜绝黑幕，点击查看本次开奖全程验证
✨ 命运揭晓时刻 ✨ 桂城 @kikizhuzhu 半价 开奖了 抽奖人数：39，发言达标人数：15，抽奖号数：87 1. 梁工【祝福6次】 中得：P半价 抽奖说明： 1 本次活动不兑现，炸号无效，兑奖联系 @kikizhuzhu 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 半价券需提交出击报告 🔍 杜绝黑幕，点击查看本次开奖全程验证
❤1
✨ 命运揭晓时刻 ✨ 桂城 @a557769z P半价 开奖了 抽奖人数：8，抽奖号数：13 1. 4°冰可乐🥤【祝福2次】 中得：P半价 抽奖说明： 1 本次活动不兑现，炸号无效，兑奖联系 @a557769z 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 半价券需提交出击报告 🔍 杜绝黑幕，点击查看本次开奖全程验证
🎉 禅城香香 @xiang2678 半价 🎁 奖品清单 • P半价 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 修车出击大队推广轮播群 • 加入 抽奖专栏 • 加入 香香的小家🏡 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-07-29 14:00:00 📜 抽奖说明 1 本次活动不兑现，炸号无效，兑奖联系 @xiang2678 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 半价券需提交出击报告 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
❤1
🎉 桂城 @kikizhuzhu 半价 🎁 奖品清单 • P半价 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 Kiki的秘密花园 • 加入 修车出击大队推广轮播群 • 加入 抽奖专栏 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-07-28 20:00:00 📜 抽奖说明 1 本次活动不兑现，炸号无效，兑奖联系 @kikizhuzhu 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 半价券需提交出击报告 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
❤1
🎉 桂城 @a557769z P半价 🎁 奖品清单 • P半价 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 修车出击大队推广轮播群 • 加入 抽奖专栏 • 加入 贝贝🍒 • 需消耗无限宝石：30 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-07-28 14:00:00 📜 抽奖说明 1 本次活动不兑现，炸号无效，兑奖联系 @a557769z 2 自开奖日七天内有效 老师因个人原因，需延长有效期。 3 半价券需提交出击报告 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
Showing the 12 most recent of 22 posts we hold for @fshan103. 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 — 793,786 of 1,169,250entries 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.
Named by 5 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.
@fshan103 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“抽奖专栏” (@fshan103), 3,087 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/fshan103.
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.