🐹五月天官方人工客服 专业接待 · 诚信服务 · 值得信赖 ⚠️ 请认准官方身份,谨防冒充! ❗️ 非888号码,全部谨慎核实,谨防假冒客服。 唯一号码 +888 0357 2956 🔹 永久用户名:@chengxincha 🔹 用户名含义:诚信查(全拼) 认准官方渠道,避免上当受骗! 五月天官方客服,为每一份信任负责。
👍3🤔1

Channel
@SGK251
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
30,398subscribers
+25,097 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1004424137219 |
|---|---|
| Type | Channel |
| Username | @SGK251 |
| Created | 28 July 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 58 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/SGK251 |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 11:21 | 30,398 | +662 |
| 15 Nov 2026, 10:08 | 29,736 | +660 |
| 12 Nov 2026, 03:19 | 29,076 | +229 |
| 10 Nov 2026, 07:50 | 28,847 | +193 |
| 8 Nov 2026, 21:45 | 28,654 | +171 |
| 7 Nov 2026, 14:51 | 28,483 | +285 |
| 6 Nov 2026, 13:51 | 28,198 | +368 |
| 5 Nov 2026, 10:19 | 27,830 | +348 |
| 4 Nov 2026, 06:21 | 27,482 | +319 |
| 3 Nov 2026, 06:19 | 27,163 | +220 |
| 2 Nov 2026, 04:48 | 26,943 | +200 |
| 1 Nov 2026, 01:00 | 26,743 | +230 |
| 31 Oct 2026, 02:01 | 26,513 | +111 |
| 30 Oct 2026, 00:36 | 26,402 | +208 |
| 28 Oct 2026, 23:58 | 26,194 | +88 |
| 28 Oct 2026, 01:20 | 26,106 | +116 |
| 26 Oct 2026, 22:41 | 25,990 | +163 |
| 25 Oct 2026, 22:16 | 25,827 | +123 |
| 24 Oct 2026, 19:28 | 25,704 | +149 |
| 23 Oct 2026, 19:51 | 25,555 | first reading |
34 posts held, back to 28 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 107 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.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 34 (28 July 2026 – 17 November 2026) |
| Views total | 23,768 |
| Reactions total | 38 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 05:40 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 2 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.
188 reactions across 27 posts, in 8 distinct kinds. The most used accounts for 61.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 115 | 61.2% | |
| ❤ | 56 | 29.8% | |
| 👏 | 5 | 2.66% | |
| 🎉 | 3 | 1.60% | |
| 🤔 | 3 | 1.60% | |
| 🤡 | 3 | 1.60% | |
| 🤪 | 2 | 1.06% | |
| 🥰 | 1 | 0.532% |
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 30 of the 34 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 188 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 34 most recent posts we hold, published 28 July 2026 to 17 November 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.
Telegram’s own ‘edited’ marker: 3 of 5 posts held from the last 30 days (60.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🐹五月天官方人工客服 专业接待 · 诚信服务 · 值得信赖 ⚠️ 请认准官方身份,谨防冒充! ❗️ 非888号码,全部谨慎核实,谨防假冒客服。 唯一号码 +888 0357 2956 🔹 永久用户名:@chengxincha 🔹 用户名含义:诚信查(全拼) 认准官方渠道,避免上当受骗! 五月天官方客服,为每一份信任负责。
👍3🤔1
📢 永久会员专属权益升级公告 即日起,开通永久会员,即可尊享多项专属福利! 🎖 永久会员尊享权益 ① 大头查询 —— 永久免费查询 ② 抖音反查 —— 永久免费查询 ③ 人工查询 —— 尊享专属 9 折优惠 💎 一次开通,长期尊享 无需重复开通,会员权益长期有效。 💰 会员价格亲民,权益超值! 永久会员价格实惠,开通即可享受多项专属福利,性价比十足! 📌 具体会员价格及开通方式,请前往机器人「充值中心」查看。 感谢各位老板一直以来的支持与信任,我们将持续优化服务,为大家带来更优质的使用体验。 ✨ 开通永久会员,解锁专属权益!
👍5
❄️【立冬快乐】❄️ 立冬已至,寒意渐浓,温暖如约而来! 祝各位老板: 💰 财源滚滚,日进斗金! 🧧 生意兴隆,订单不断! 🚀 事业蒸蒸日上,贵人常伴! 💎 客户多多,收入多多,USDT多多! 🔥 好运常在,财运亨通,盆满钵满! 愿这个冬天,大家有衣暖身,有钱暖心,有人相伴,有财相随! 祝各位老板立冬快乐,整个冬天财运爆棚,发财发大财! 🎉 ❤️ 来自五月天团队的祝福
👍10❤2🤔2
之前的信誉记录频道被人举报导致被封。🥹 今天开始重新更新新的信誉记录 信誉记录频道 https://t.me/zhuanyekai
👍6❤2🎉2
机器人打算优化🤔 有没有什么意见可以评论区发下让我有个参考。
👍5
机器人用不了,显示没加入频道的但是你都加入的原因是因为tg显示bug 加入新频道就可以恢复正常使用 https://t.me/U7mvp
👍11❤1
业务频道被官方强制删除。这另我很是悲伤🥹 新的频道已经弄好了,请各位用户不要走丢 用户名永久不变 @SGK250 -我们永远不会跑路的
👍5🤡3🤪2❤1🎉1
📣正在制作新的业务频道。请耐心等待
👍9
大频道被官方强制删除了没了,等待恢复
👍8
有没有尝试过邀请50人可以免费获得会员呀?
👍18
各位 机器人只是辅助查询 真正的查询还得是我们人工付费查询并不是说机器人是万能的 人工才是多样的 各种各样的业务机器人只能查询一些基本普通的信息 机器人查询不到的只能靠我们 我相信很多人的顾虑是担心怕被骗!‼️ 各位可以先下下小单子试试我这里! 这里主打诚信经营 https://t.me/sgk250
❤11👏1
最后一次温馨提示‼️ 机器人与群组客服只有唯一有个 @chengxincha 其他的都是冒充假冒的,被骗概不负责
❤7👍4
Showing the 12 most recent of 34 posts we hold for @SGK251. 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.
@SGK251 edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 5 posts on @SGK251 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
@SGK251 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.
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.
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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“五月天社工库通知频道” (@SGK251), 30,398 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/SGK251.
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.