Channel
@suosuo698956
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
214subscribers
+4 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004387336312 |
|---|---|
| Type | Channel |
| Username | @suosuo698956 |
| Created | 11 August 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/suosuo698956 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:55 | 214 | +4 |
| 12 Aug 2026, 08:45 | 210 | first reading |
5 posts held, back to 11 August 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.
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 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 5 (11 August 2026 – 12 August 2026) |
| Views total | 78 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 08:45 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 5 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 11 August 2026 to 12 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.
✈️【收到新的报告】 【深圳报告】https://t.me/jngeh 【所在位置】宝安#西乡#固戍 【老师艺名】锁锁 【联系方式】@suosuo89996 【验证留名】军 【验证时间】8月11日 【上课价位】888 【人照几成】9.5分 【颜值分数】9.5分 【身材分数】9分 【课表服务】双飞 【态度分数】10分 【优点缺点】花样多 【推荐程度】五星推荐 【体验细节】跟锁锁老师约了个双飞，40分钟路程，到达位置，停好车，老师指引上门，进门见到老师，一眼就认出来了，跟相片相差不大，身材不错，也很热情，闲聊几句，锁锁就手拉手的带我洗澡，老师洗的很用心，回到课室，老师搭档也过来了，活泼可爱的妹子，锁锁老师就开始从胸往下面舔，老师搭档就和我舌吻起来，舌了二三分钟，一左一右，舔的我好舒服，锁锁老师就一下吮着我的小弟弟，老师搭档就把咪咪送我嘴来，也给舔了小妹妹，好多水，然后锁锁老师加快口速，实在着不住爆了一次，清理干净，二姐妹相互换了位…
❤1
感谢哥哥们的支持，每天中午十二点准时开课，闺蜜也在可约双飞 艺名：锁锁（环保/92/95） 位置：深圳#宝安#固戍 课费：400🛩️500👄爆888双飞 私聊：@suosuo89996 双向：@suosuolove520_bot
https://t.me/SZ_nmctm/1166444
宝宝们，之前的号不用了，现在用这个小号，宝宝们不要走空哦！
Channel created
Showing the 5 most recent of 5 posts we hold for @suosuo698956. 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 — 987,130 of 1,350,102entries 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.
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.
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.
“锁锁个人频道” (@suosuo698956), 214 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/suosuo698956.
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.