没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍7

Channel
@My_Name_Sheep
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
37,795subscribers
+9,104 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002261818785 |
|---|---|
| Type | Channel |
| Username | @My_Name_Sheep |
| Description | 广告联系 @didb431 |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/My_Name_Sheep |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 06:20 | 37,795 | +677 |
| 4 Sept 2026, 09:54 | 37,118 | +231 |
| 2 Sept 2026, 21:27 | 36,887 | +184 |
| 1 Sept 2026, 18:08 | 36,703 | +273 |
| 31 Aug 2026, 17:46 | 36,430 | +226 |
| 30 Aug 2026, 20:43 | 36,204 | +162 |
| 30 Aug 2026, 00:09 | 36,042 | +253 |
| 28 Aug 2026, 22:24 | 35,789 | +187 |
| 28 Aug 2026, 00:43 | 35,602 | +83 |
| 27 Aug 2026, 03:48 | 35,519 | +168 |
| 26 Aug 2026, 06:53 | 35,351 | +95 |
| 25 Aug 2026, 05:04 | 35,256 | +90 |
| 24 Aug 2026, 05:46 | 35,166 | +380 |
| 22 Aug 2026, 14:47 | 34,786 | +241 |
| 21 Aug 2026, 08:27 | 34,545 | +374 |
| 20 Aug 2026, 09:14 | 34,171 | +218 |
| 19 Aug 2026, 12:38 | 33,953 | +279 |
| 18 Aug 2026, 12:03 | 33,674 | +197 |
| 17 Aug 2026, 13:04 | 33,477 | +864 |
| 16 Aug 2026, 06:12 | 32,613 | first reading |
225 posts held, back to 9 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 66 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 204 of 207 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 September 2026 |
|---|---|
| Posts held | 225 (9 July 2025 – 8 September 2026) |
| Views total | 84,846 |
| Reactions total | 1,879 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Sept 2026, 13:11 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 8 September 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 13 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,467 reactions across 218 posts, in 17 distinct kinds. The most used accounts for 67.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,655 | 67.1% | |
| ❤ | 518 | 21.0% | |
| 😭 | 83 | 3.36% | |
| 🤬 | 60 | 2.43% | |
| 👏 | 19 | 0.77% | |
| 😁 | 18 | 0.73% | |
| 🤔 | 18 | 0.73% | |
| 😍 | 16 | 0.649% | |
| 🔥 | 15 | 0.608% | |
| 👎 | 13 | 0.527% | |
| 🖕 | 12 | 0.486% | |
| 💩 | 11 | 0.446% | |
| 🥰 | 11 | 0.446% | |
| 🎄 | 5 | 0.203% | |
| 🎉 | 5 | 0.203% | |
| 🤓 | 5 | 0.203% | |
| 🤩 | 3 | 0.122% |
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 218 of the 225 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,467 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 225 most recent posts we hold, published 9 July 2025 to 8 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.
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍7
库洛米 V21.0.0 更新内容: 1.修复容器内物资无效 2.修复物资的问题 3.优化物资列表 4.新增完美解密一,无延迟,实时解密,0 内存 5.重构部分算法,防止特征 6.增加稳定性 7.修复优化若干问题 bug 建议使用前先重置一下配置 已拿捏三角洲最新加密,并且写好了三种解密方法,若加密和谐,最快速度更新备用解密 题卡地址:🔗 https://gtq.fakajs.cn/shop/kuluomi886 代理点我注册 对接码:kuluomi ❗️❗️➡️点我加入官方频道 ❗️❗️➡️点我加入官方群组
👍9🤔1
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍7
😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+参与联系负责人 @didb431 全网收广告位出的直接私信我 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道
👍6
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍5
避雷这个傻子频道,就是昨天那个咕噜熊改名字的,你看老子搞不搞你,以为换个频道就有用? 卖的un也是10年项目垃圾东西
👍7
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍12
三角洲EO公益算法解密 公益解密卡密: 点我查看 ❗️❗️➡️ @EO66789 ❗️❗️➡️ @EO66669
👍10
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍5
✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接加入🥰 😀😀😀😀😀
👍6
三角洲已下发加密,天眼udp公益解密欢迎来使用❤️目前解密能使用哈 公益udp解密目前唯一一家 解密无效果或者解密失败的换网络即可 🌟🙃🌟➡️ @tianyan63
👍11
【三角洲No One内部解密】 😀No One内部🎮目前三角洲最稳定的算法解密 好评如潮 交流群开放.绝对颠覆传统 功能完善媲美端游DMA项目. 🛒全网统一零售价: 😀😀😀/周 功能:透视+自瞄+物资 😀😀😀😀/月 功能:透视+自瞄+物资+追踪 💵支付方式:微信/支付宝/USDT 【官方保障】 ✔️ 无法使用 → 全额退款 ✔️ 封禁10年 → 全额退款 ✔️ 与描述不符 → 全额退款 定制级算法解密,已连续稳定多个赛季,无视游戏任何更新与检测!已适配最新赛季国服,无视偏漏,无视加密,无视破解,本项目主打高端,严格控制人数,严格控制软件包!适用于主播/职业护航/追求极致稳定性的玩家! 开卡咨询客服:@ZYR5201314 点我加入No One官方通知频道 点我加入No One官方通知频道 点我加入No One官方通知频道
👍9❤2
Showing the 12 most recent of 225 posts we hold for @My_Name_Sheep. 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.
@My_Name_Sheep edited 1 post 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.
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.
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.
@My_Name_Sheep 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“山海经内核频道” (@My_Name_Sheep), 37,795 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/My_Name_Sheep.
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.