收购数据 请提供 样本 价格 来源 总量 样本不低于1w 总量不低于100w 推广合作 如您是频道主 或有其他引流渠道 能为bot 引流 我们支持合作 包括不限于 提供给您 机器人会员/积分/u等 合作联系 @wind_iu 请直接说明来意
👍24❤12🥰4🎉2

Channel
@xiaohaigeSGK
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
276,901subscribers
+11,778 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002304565448 |
|---|---|
| Type | Channel |
| Username | @xiaohaigeSGK |
| Description | 一诺通知 @xiaohaigeSGK 一诺供需 @yndb_gongqiu 交流大群 @XiaoHaiGe_SGK 交流二群 @yndb_xq 广告群组 @ynguanggao 供需商家 @YNDB_DBGZ 公群导航 @YNDB_GQGZ |
| Created | 2 November 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/xiaohaigeSGK |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 16 Nov 2026, 05:47 | 276,901 | -1,282 |
| 12 Nov 2026, 20:29 | 278,183 | -52 |
| 10 Nov 2026, 15:15 | 278,235 | +79 |
| 9 Nov 2026, 04:10 | 278,156 | +553 |
| 7 Nov 2026, 20:46 | 277,603 | +674 |
| 6 Nov 2026, 19:49 | 276,929 | +785 |
| 5 Nov 2026, 18:58 | 276,144 | +159 |
| 4 Nov 2026, 19:20 | 275,985 | +566 |
| 3 Nov 2026, 15:50 | 275,419 | +714 |
| 2 Nov 2026, 18:40 | 274,705 | +470 |
| 1 Nov 2026, 21:00 | 274,235 | +690 |
| 31 Oct 2026, 21:08 | 273,545 | +80 |
| 30 Oct 2026, 19:28 | 273,465 | +126 |
| 29 Oct 2026, 16:19 | 273,339 | -85 |
| 28 Oct 2026, 15:19 | 273,424 | +308 |
| 27 Oct 2026, 16:56 | 273,116 | +69 |
| 26 Oct 2026, 19:18 | 273,047 | +110 |
| 25 Oct 2026, 21:15 | 272,937 | -137 |
| 24 Oct 2026, 19:16 | 273,074 | +141 |
| 23 Oct 2026, 21:17 | 272,933 | first reading |
34 posts held, back to 2 November 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 209 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 26 October 2026 |
|---|---|
| Posts held | 34 (2 November 2024 – 26 October 2026) |
| Views total | 19,500 |
| Reactions total | 42 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 14:25 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.
Lifetime counters from Telegram’s own channel header, read 17 November 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.
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.
2,197 reactions across 33 posts, in 7 distinct kinds. The most used accounts for 31.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 693 | 31.5% | |
| 👍 | 566 | 25.8% | |
| 🤩 | 272 | 12.4% | |
| 🥰 | 170 | 7.74% | |
| 🎉 | 169 | 7.69% | |
| 👏 | 166 | 7.56% | |
| 🔥 | 161 | 7.33% |
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 33 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 2,197 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 2 November 2024 to 26 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @xiaohaigeSGK. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 34 most recent posts we hold for this entry, published 2 November 2024 to 26 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 1 of 1 post held from the last 30 days (100.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).
收购数据 请提供 样本 价格 来源 总量 样本不低于1w 总量不低于100w 推广合作 如您是频道主 或有其他引流渠道 能为bot 引流 我们支持合作 包括不限于 提供给您 机器人会员/积分/u等 合作联系 @wind_iu 请直接说明来意
👍24❤12🥰4🎉2
供需频道更新为:@yndb_gongqiu 有需要人工查档业务可在供需频道查看各项业务 货比三家!
👍14❤1👏1
合作联系 @wind_iu (有小小的门槛)
👍7❤5
🇺🇸 美国政府经济数据,正式上链。 美国商务部正与 Chainlink 合作,将来自美国经济分析局(BEA)的关键宏观经济数据通过预言机发布到区块链上。 目前已覆盖: ▸ 实际 GDP ▸ PCE 价格指数 ▸ 私人国内购买者实际最终销售 传统宏观经济数据,正在成为链上可调用的数据基础设施。 这可能只是美国政府拥抱区块链的开始。
👍5❤3
为了获取流量收割更多中国人的财富 美国CIA应允了孙割与景甜结发的请求 而在景甜提出5000万美金取卵费用后 因涉及大额支出 孙宇晨请求被CIA断然驳回 并发出制造流量继续收割的指令 孙宇晨虽然不舍 但上了这条贼船岂是那么容易下船的 一天特工 终身特工 孙宇晨知道 一旦背叛组织 他就会成为下一个陈志 孙宇晨最终还是选择了组织
👍17❤3
美国中情局给孙宇晨下达了从中国吸血100亿美金的政治任务 为了完成组织的任务 孙宇晨背叛了对白月光景甜是爱情 只为尽快实现100亿的目标 孙宇晨所有资产均为孙明义保管 背后金主为美国CIA
👍15❤3
孙宇晨是头号特务🕵️ 波场USDT主要用户都是中国人 孙宇晨是USAID(国际开发署/CIA美国中情局)培养和支持的头号特务,从中国吸血危害中国,其对中国危害⚠️不亚于土肥原贤二这些人 呼吁冯小刚快点去抓特务🕵️
👍13❤2
境外敌对势力、反党分子、煽动颠覆国家政权思想犯和行为犯、叛国者、民运分子、传销头子、头号洗钱分子、与陈志齐名的黑灰产头目孙宇晨同学曾参加过海外民运活动,早在2011年就在中国民主运动精神领袖方励之先生的追思会上代表九零后留学生发言。 他说道:“翻墙成为了互联网原住民的街头暗号,成为了他们的必修课;翻过一个方向所搭建的愚昧之墙,奔向另一个方向所许诺的愚昧之地,成为了这个国家最大的精神出走,一幕最盛大的出埃及记” 方励之(1936年2月12日—2012年4月6日),籍贯浙江杭州,生于北京,美籍华裔天体物理学家,是1980年代中国“新启蒙运动”领袖之一,因六四事件流亡美国,后任亚利桑那大学天体物理学教授。【情报来源于维基百科】 孙宇晨确实参加了方励之的追思会。当时他作为留美学生代表在会上发言,这也是他早期广为人知的公共政治参与事件之一。 【美国之音】 事件核心背景 时间与地点:2012年4月21日下午,追思会于美国纽约法拉盛喜…
👍13❤7🤩1
开学季充值特别活动 一年会员从300u调整为200u 永久会员从500u调整为300u 2026年8月28日12点始 详请联系 https://t.me/DBKYI
❤23👍10🔥1
是时候离开了。 从年初临危受命接过这个项目,到今天。那些通宵的夜、经历过的艰难时刻,都还清清楚楚。 最庆幸的不是把事情做成了,捋顺了,而是在这里遇到了一群真正志同道合的人————愿意在最难的时候一起扛,愿意为一件小事争到面红耳赤。如今项目也找到了可以完整托付的人,这让我很安心。 项目会一直运行下去,它不属于我,它属于所有认真待过它的人。我会在远处默默关注它,看它长大,替它高兴。 还有2年左右,这项目才有可能回到他原本的时刻,谁知道呢? 但项目肯定会让更多人收益,没有人有权利一家独大,也不会消失(只要市场有需要),也会有更负责的雨后春笋去维护它,继续事业。 如果有需要,我也会在适当时候回来,也可能也希望永远不会再回来,最好如此。 以后就聊聊天吧…我最擅长的 by:过客
❤25👍13
好一个先贤家族 即使父亲被迫害 还想着为党国建言献策 那种骄傲是与生俱来的身份🆔认同感 真以为能平反吗 真以为自己家族还是新中国的股东🙅
👍6❤2
孙割:妈妈~ 景甜:牛来! 哞~~~
👍11🤩6❤2
Showing the 12 most recent of 34 posts we hold for @xiaohaigeSGK. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@xiaohaigeSGK edited 2 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 4 posts on @xiaohaigeSGK 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.
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.
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.
@xiaohaigeSGK 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“一诺通知 @YNDB” (@xiaohaigeSGK), 276,901 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/xiaohaigeSGK.
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.