Telegram RegisterThe public register of Telegram
Telegram profile photo for 清水

Channel

清水

@soqbDj

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,646subscribers

+208 since we began measuring on 30 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003896999366
TypeChannel
Username@soqbDj
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live15 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/soqbDj

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 42% 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 why it has no browse page of its own yet.

Growth

2,4382,6462,54230 August 2026 — 2,438 subscribers31 August 2026 — 2,451 subscribers3 September 2026 — 2,515 subscribers8 September 2026 — 2,601 subscribers12 September 2026 — 2,627 subscribers15 September 2026 — 2,646 subscribers30 August 202615 September 2026
6 measurements spanning 16 days, net +208. 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 2,407–2,677 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 20:582,646+19
12 Sept 2026, 12:392,627+26
8 Sept 2026, 20:012,601+86
3 Sept 2026, 16:002,515+64
31 Aug 2026, 07:042,451+13
30 Aug 2026, 19:152,438first reading

Engagement

19 posts held, back to 27 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.82%
avg views ÷ 2,646 subscribers
Avg views / post
154
9 posts measured
Reaction rate
3.75%
reactions ÷ views · ER floor
Posts in window
9
of 19 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. It is computed over the 1 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 August 2026
Posts held19 (27 August 2026 – 30 August 2026)
Views total1,385
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 19:15 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.

What this channel posts

Video runtime
30s
Average length
15s

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.

Reaction mix

4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣375.0%
❤125.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 2 of the 19 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 27 August 2026 to 30 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

30 Aug 2026, 14:03 UTC80 views3 reactionsread 30 August 2026
Photo

要不要上架一天不限制次数10u一天😂可以模糊美团名字前一后一

🤣3

Signed 清水

30 Aug 2026, 12:56 UTC123 viewsread 30 August 2026

最近这一个月你清水弟弟都饿死了老板丢不丢我单了希望有老板能丢点单大单也好小单也好,全部通知不管我有没有都要过来问一下

Signed 清水

30 Aug 2026, 12:30 UTC160 viewsread 30 August 2026

🚀清水 🔐 免费核验机器人。支持身份证二要素核验、有效期核验,运营商三要素,手机二要素核验,法人四要素核验,支付宝二要素核验,京东模糊,银行卡三要素核验,人脸核验带对比度,开户行查询,婚姻状态查询 更多功能等你体验...... 长期收购支付宝核验接口如: 支付宝二要素核验和支付宝三要素核验 单次核验就够 ✅ 支持签到 推荐🔥🔥 清水聊天频道 :https://t.me/BTMRaaaa 群内可以免费使用京东模糊美团模糊 还有机主模糊 清水官方频道 https://t.me/soqbDj 清水机器人 @hongniuheyaBot

Signed 清水

30 Aug 2026, 06:05 UTC172 viewsread 30 August 2026

😃😃😃😃 32🤖江苏神父🤖😀😀秒 45🤖广西神父🤖😀😀秒 46🤖海南神父🤖😀😀秒 13🤖河北个户🤖😀😀 43🤖湖南神父🤖😀😀秒 65🤖新疆神父🤖😃😀 41🤖河南社保🤖😃😀秒 37🤖山东神父🤖😃😀秒 42🤖湖北神父🤖😃😀秒 36🤖江西单头🤖😀😀 50🤖重庆神父🤖😃😀秒 34🤖安徽神父🤖😃😀秒 36🤖江西神父🤖😃😀秒 44🤖广东神父🤖😃😀 65🤖甘肃神父🤖😃😀秒 41🤖河南神父🤖😃😀秒 14🤖山西神父🤖😀😀秒 44🤖广东单地址🤖😃😀秒 12🤖天津神父🤖😀😀秒 33🤖浙江地址🤖😃😀秒 11🤖北京地址🤖😃😀秒 35🤖福建单地址🤖😃😀秒 ‼️报单联系 @B_B_T_X 在线秒回 量大的可以找我拿优势可以单开机器人

Signed 清水

30 Aug 2026, 06:05 UTC157 viewsread 30 August 2026

文字全户😀😃排队秒 公网补齐😀😃无视脱库 任意17位 公网猎魔😀😃无视脱库 可带排除 保真不保漏 人在既秒 同行代理来谈价格 有量有价

Signed 清水

29 Aug 2026, 19:27 UTC226 viewsread 30 August 2026

修复/维护 群聊中添加了美团模糊供用户使用不会扣除任何积分 然后清水机器人已经恢复运行正常 凌晨3点才全部修复完唉😅😅😅

Signed 清水

28 Aug 2026, 15:49 UTC328 viewsread 30 August 2026
Photo

美团点餐+美团订房⚡️⚡️⚡️⚡️ 美团内部工号直出 无遗漏 注:点餐只有详情无收货地址 加钱可以指定日期或出全部 渠道在线就秒 全天秒 全天秒🥳

Signed 清水

28 Aug 2026, 15:46 UTC270 viewsread 30 August 2026

文字全户😀😃排队秒 公网补齐😀😃无视脱库 任意17位 公网猎魔😀😃无视脱库 可带排除 保真不保漏 人在既秒 同行代理来谈价格 有量有价

Signed 清水

28 Aug 2026, 10:09 UTC320 viewsread 30 August 2026

😒全国身份证正反面(高清神父) 假有效期神父 ❤️❤️ 😵提供信息:名字 身份证号 😵出单结果:上图➕pdf文件 😵出单时间:全天秒 ps:别人出不来的 我这照出❗️

Signed 清水

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

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

“清水” (@soqbDj), 2,646 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/soqbDj.

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.