https://t.me/shockCN
Channel
群資源
@sdfhjsdfk
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
4subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003966385943 |
|---|---|
| Type | Channel |
| Username | @sdfhjsdfk |
| Created | Between 1 April 2026 and 30 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/sdfhjsdfk |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 10:03 | 4 | no change |
| 13 Aug 2026, 03:02 | 4 | first reading |
Engagement
20 posts held, back to 30 April 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 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 36
Lifetime counters from Telegram’s own channel header, read 13 August 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.
Recent posts
https://t.me/tvcbot8
https://t.me/BNBChainZH
https://t.me/mytoken_cn
https://t.me/BitMEX_Official_Chinese
https://t.me/bitfinex
https://t.me/StarExCN
https://t.me/memebuysellalert
https://t.me/BtokCN_0014
https://t.me/CheersToCryptoCheer
https://t.me/Feixiaohaonew
https://t.me/CoreDao_Orgcn
Showing the 12 most recent of 20 posts we hold for @sdfhjsdfk. 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
Citation-graph rank — 1,061,438 of 1,480,688entries 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.
Mentions
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.
Names
Channels on the register whose handles appear in this channel's posts.
@BtokCN_0014 · 119,6972 posts歐文的合約社区
@lbeobhpreo · 4,1862 postsHMZALF
@apegmi · 1,3991 postBabyDogeCoin官方中文社区
@babydogechina · 83,4441 postBDDJO
@BDDJO · 51 postbensongroup
@bensongroup · 141 post比特币分分-币安比特币分分-比特币分分彩-币安比特币分分彩-比特币涨跌-币安比特币平台-比特币分分彩平台-比特币5分彩-币安比特币5分彩-币安比特币五分彩
@bianbitebi · 71 post币道 BiDAO🇨🇳 BSC/OKB/SOL/ETH Owner:@dog_god777
@bidaobi · 39,4611 post賓哥失言語錄無限擴展
@bingerhapptbirthday · 131 post幣咚的跟風日常投資
@bitcryptowinter · 171 postBitop 官方交流群
@Bitop_ExchangeZh · 1581 post區塊客 Blockcast.it-第一手 區塊鏈新聞
@blockcastit · 12,4841 postטיב&טעם|קאנביס ברמה אחרת
@blockchainintw · 121 postOPTE.COOL - 大宇币圈交流群
@BTCdayu999 · 8741 postcoredao_orgcn
@coredao_orgcn · 1741 post瘋狗快報
@CryptodooogNotice · 1,5281 postTony ETF 美股资讯频道
@funnynasdaq · 3061 post期貨浪人廣播台
@futureronin168 · 3,7951 postggulu
@ggulu · 1541 postgrenadetww
@grenadetww · 4671 post金云数据4277
@hk852_money · 141 postmolewallet
@molewallet · 111 postqbzclub
@qbzclub · 51 postAdaisha Tamar Official
@storm_money_tw · 61 post
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.
Handles this channel named that no longer answer
- Dead references
- 30
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 30
- vacant every time we have ever looked
@sdfhjsdfk named 30 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
Cite this entry
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“群資源” (@sdfhjsdfk), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/sdfhjsdfk.
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.