Telegram RegisterThe public register of Telegram
Telegram profile photo for 伤痕数据号(免费数据号)

Channel

伤痕数据号(免费数据号)

@shsjh78

On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

16,130subscribers

+1,248 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003152998552
TypeChannel
Username@shsjh78
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/shsjh78

Growth

14,88216,13015,5066 August 2026 — 14,882 subscribers6 August 2026 — 14,931 subscribers7 August 2026 — 15,083 subscribers8 August 2026 — 15,221 subscribers9 August 2026 — 15,334 subscribers10 August 2026 — 15,404 subscribers11 August 2026 — 15,472 subscribers12 August 2026 — 15,627 subscribers13 August 2026 — 15,721 subscribers14 August 2026 — 15,941 subscribers16 August 2026 — 16,130 subscribers6 August 202616 August 2026
11 measurements spanning 10 days, net +1,248. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 14,695–16,317 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 08:1216,130+189
14 Aug 2026, 19:2715,941+220
13 Aug 2026, 08:0515,721+94
12 Aug 2026, 10:0515,627+155
11 Aug 2026, 09:3815,472+68
10 Aug 2026, 10:0515,404+70
9 Aug 2026, 10:0415,334+113
8 Aug 2026, 08:4115,221+138
7 Aug 2026, 10:2215,083+152
6 Aug 2026, 09:3114,931+49
6 Aug 2026, 04:0214,882first reading

Engagement

127 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 28 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.35%
avg views ÷ 16,130 subscribers
Avg views / post
1,350
127 posts measured
Reaction rate
1.34%
reactions ÷ views · ER floor
Posts in window
127
of 127 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 August 2026
Posts held127 (4 August 202615 August 2026)
Views total171,146
Reactions total2,300
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 19:39 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.

Reaction mix

2,037 reactions across 107 posts, in 22 distinct kinds. The most used accounts for 75.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,54675.9%
23511.5%
🤯994.86%
😭412.01%
😡281.37%
🔥221.08%
😍180.884%
🍌100.491%
😢80.393%
😁70.344%
👏60.295%
🥰30.147%
🌭20.098%
😎20.098%
🤓20.098%
🫡20.098%
🏆10.049%
🐳10.049%
🗿10.049%
😈10.049%
2 further kinds20.098%

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 127 of the 127 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,300reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 127 most recent posts we hold, published 4 August 2026 to 15 August 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.

Recent posts

15 Aug 2026, 13:05 UTC792 views34 reactionsread 15 August 2026

对接吃肉,用我的卡网百分百不会被跑路,你母跑了我都不可能跑😋

👍22😡9😍3

15 Aug 2026, 11:11 UTC≈1,080 views24 reactionsread 15 August 2026

进厂了,卖数据号的我应该是第一个进厂的😭

👍221🔥1

15 Aug 2026, 11:04 UTC≈1,060 views25 reactionsread 15 August 2026

没拉人的可以拉一下朋友,拉一个给20级3个给50级5个给60级 拉5一共是给3个20级 一个50级一个60级 拉小号啥的都不算,必须是玩挂圈的,必须是玩授权号,玩直装内核之类的才行,其余的拉进来也不算

👍231🔥1

15 Aug 2026, 10:43 UTC≈1,100 views30 reactionsread 15 August 2026

8点照常发免费授权号,现在还没上班等后天可能要九点发免费授权号了

👍26😍31

15 Aug 2026, 07:08 UTC≈1,330 views31 reactionsread 15 August 2026

我服了,你们被无限隔离打败的能不能用一下卡网的清理啊,百分百有效果先执行5.3.2.1然后执行通杀人脸的1然后设备百分百无任何问题,没root的恢复出厂设置就行

👍272😍2

15 Aug 2026, 07:03 UTC≈1,300 views19 reactionsread 15 August 2026

价格已上涨,售后依旧吊打全网客服全天在线,都是花钱请的客服,态度和售后速度吊打全网,全天在线售后,依旧是最牛逼

👍18😍1

15 Aug 2026, 06:51 UTC≈1,340 views22 reactionsread 15 August 2026

给你们售后的号,发完你们如果已读了就尽快上号验,如果发现售后的号已读了,然后过了半天又说没上号看,有什么什么问题的就补不了了,尽量不要出现这种情况,你们什么时候已读的我们客服都可以看到,7点已读的第二天然后说没看号,号有人脸什么的,谁也确保不了是不是你自己造成的,所以说不要出现这种情况让客服很为难,有问题的就算没录屏,偶尔一次的我们也补了

👍201😍1

15 Aug 2026, 06:47 UTC≈1,470 views19 reactionsread 15 August 2026

卡网:http://shop.jyarts.top/ 对接码 shsjhnb 来人对接吃肉就完事了,你们搞内核,直装注入啥的,直接对接就完事了,全网最低对接价,你们负责卖售后,我全包

👍171😍1

15 Aug 2026, 06:23 UTC≈1,250 views15 reactionsread 15 August 2026

卡网授权号3点要涨价了,最近没什么号了,等量大了就降回去,你们不急的话可以先不买,等降价再买也可以的

👍15

15 Aug 2026, 04:21 UTC≈1,360 views14 reactionsread 15 August 2026

无限招收剪辑,有意向的进群找群主了解

👍11🔥1😍1😢1

Showing the 12 most recent of 127 posts we hold for @shsjh78. 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.

Posts edited after publishing

@shsjh78 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.

First edit seen
14 August 2026
Most recent edit
14 August 2026

Citation-graph rank

Citation-graph rank — 1,415,048 of 1,481,217entries 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.

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.

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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“伤痕数据号(免费数据号)” (@shsjh78), 16,130 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/shsjh78.

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.