兄弟姐妹们,广告稍微控制一点
Signed 释怀

Channel
@FQDSJ
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
21,822subscribers
-225 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002311947491 |
|---|---|
| Type | Channel |
| Username | @FQDSJ |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/FQDSJ |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 07:55 | 21,822 | +36 |
| 5 Sept 2026, 00:21 | 21,786 | +21 |
| 3 Sept 2026, 08:18 | 21,765 | -48 |
| 2 Sept 2026, 04:14 | 21,813 | -22 |
| 1 Sept 2026, 05:07 | 21,835 | -8 |
| 31 Aug 2026, 07:06 | 21,843 | -15 |
| 30 Aug 2026, 05:27 | 21,858 | -4 |
| 29 Aug 2026, 07:43 | 21,862 | -16 |
| 28 Aug 2026, 10:02 | 21,878 | -13 |
| 27 Aug 2026, 09:43 | 21,891 | +29 |
| 26 Aug 2026, 10:46 | 21,862 | +2 |
| 25 Aug 2026, 12:02 | 21,860 | -187 |
| 22 Aug 2026, 23:00 | 22,047 | no change |
| 22 Aug 2026, 22:45 | 22,047 | first reading |
388 posts held, back to 22 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 23 pages of 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 52 of 388 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 388 (22 August 2026 – 3 September 2026) |
| Views total | 485,366 |
| Reactions total | 65 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 13:35 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.
Measured directly from 11 videos 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.
65 reactions across 41 posts, in 5 distinct kinds. The most used accounts for 64.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 42 | 64.6% | |
| 👍 | 11 | 16.9% | |
| 💩 | 5 | 7.69% | |
| 🤣 | 5 | 7.69% | |
| 🫡 | 2 | 3.08% |
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 52 of the 388 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 65 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 388 most recent posts we hold, published 22 August 2026 to 3 September 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.
兄弟姐妹们,广告稍微控制一点
Signed 释怀
德州活码⚡️⚡️⚡️ 🔠🔠🔠🔠6️⃣6️⃣8️⃣🔣🔠🔠 🔥只做一个只靠积分赚钱的活码系统!!! 🔥最新强开功能!专防机器人炸码,还粉圈一片蓝天! ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 短域名10U一条!!! 活码纯积分模式!!! 无开户费! 推荐有奖励! ⚡️⚡️⚡️⚡️ 零偷粉!!!零偷粉!!!零偷粉!!! ⚡️不出继续访问 !无地区屏蔽! ⚡️超级无敌稳定短域名,定制市面任意后缀! ⚡️活码纯积分模式 一访问一积分! ⚡️活码强开耐用不死内码(强开所有卡密)! 😍😍😍😍😍😍😍 ⚡️⚡️⚡️⚡️⚡️: @Dzhm668 ⚡️⚡️⚡️⚡️⚡️: @dzhm778 😍😍😍😍: https://t.me/dzhm6688 🥰德州活码官网: 🔠🔠🔠🔠6️⃣6️⃣8️⃣🔣🔠🔠 dzhm668.cc 🔠🔠🔠🔠7️⃣7️⃣8️⃣🔣🔠🔠 dzhm778.cc
对接仅此一个号,不会用任何小号对接!小号对接都是诈骗的!仅此一个号!认准 @libais
Signed 李白(认准典藏ID:libais)
cpa有量的来报 单价你开
Signed 野豹 (包养一手工作室)
⭐️大量收粉认准王林❤️❤️ 一次合作终身朋友收以下粉 抖音同城热评V转 抖音同城热评浏览器 抖音自热V转 抖音协议点赞V转 抖音真人直播甩码V扫 快手采集V转 快手同城站街V转 金铲铲协议V转 色播V转 抖音自热浏览器 单价你开!联系方式 :@wangl 单价你开!联系方式 :@wangl 单价你开!联系方式 :@wangl 商务粉圈 @fqsw8 收粉频道 :https://t.me/wlsf88 粉圈派出所专业曝光频道:https://t.me/fqpcs1
Signed 王林-天马cpa
😀😃😃😄抖音系列 有量来报 价格 置顶 😀😃😃😄陌陌系列 有量来报 价格 置顶 😀😃😃😄探探系列 有量来报 价格 置顶 😀😃😃😄小红书系列 有量来报 价格 置顶 😀😃😃😄视频号系列 有量来报 价格 置顶 😀😃😃😄快手系列 有量来报 价格 置顶 🚨🚨 天马 / Q群/cpa 都有 全都有🚨🚨 🚨🚨其他渠道也可以报测试 不限渠道🚨🚨 【假粉不要来找存在感 来一个死一个】 🥰致富热线::@laohu6789 @lang1 @d1d1c @nanbowan6 @TGM066
Signed 浪子🌊 (无限收真粉)认准+888
给兄弟们讲一下,我这边稳定粉商基本都是包养包结的,我的要求很简单,要求一手粉商、工作室,量要求在200以上,不要拉稀仔,天天拿着几十个粉在那磨,没任何意义,打几十个我看不出来质量好坏,不要给我乱搞进来假粉、做数据,当然我不吃垃圾粉,每位兄弟来测试的都有足够的扶持空间 🥰报单找: 路飞 @lfo888 小助理 索隆 @cmt004 小助理 山治 @cmt0001 另外有好粉的,跳槽单价+1️⃣+2️⃣起步,单价无所谓,我给的起,我要的是好粉,我来给你们稳定包养
Signed 路飞(认准888)包养一手工作室
@axin333111 @洗米华 没钱玩你们妈的臭逼啊,没钱赌你妈的逼逼啊,跑路狗草泥马
🤣2❤1
Signed 释怀
联系我一下!!!!
💩1
Signed 鲸老大 收产值粉
卡密无限!测试开放!好粉单价无限!认准:+888 2222 3344 @asxxx
Signed 宵龍
收地推。收地推域名访问量 只想给你们一个稳定的家 收一线手子 代理 带上对接记录来 有好粉滴滴我 所有想做地推打粉得,联系免费扶持,一个粉结账 帮你走出困境日入过k @Luuu 瑞幸 @Luuu3 助理叁叁 @Luuu8 助理海绵 @Luuuuuu 接待助理小六 @Luckin520 收粉频道 @ditui66c 盖章频道 跳槽提供对接记录 单价+1 单价+1 单价+1 单价+1 过滤按你的来开 诚信经🈺 长久🈴作
Signed 瑞幸 没及时回复麻烦私信炸消息
都来打德州 ,来打德州的供需免费 你们放心打,广告我来发 https://t.me/dezoujinji
Signed 释怀
Showing the 12 most recent of 388 posts we hold for @FQDSJ. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
@FQDSJ named 1 handle 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“粉圈大事件” (@FQDSJ), 21,822 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/FQDSJ.
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.