Telegram RegisterThe public register of Telegram
Telegram profile photo for 📢50U/条 舵手联盟供需频道

Channel

📢50U/条 舵手联盟供需频道

@dslm666

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

20,691subscribers

+101 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001874362689
TypeChannel
Username@dslm666
Description舵手联盟:一个专注海外资源对接的社群 🚫禁止涉及任何🇨🇳包含港澳台业务有发现一律永封!禁止讨论任何政治话题! 官方社群: @dslm888 官方频道: @dslm333 公群导航: @dslm555 骗子曝光: @dslmpzbg 总舵主: @dslmzdz 广告办理: @dslmll 双向机器人: @dslm_bot 供需机器人: @dslmgj_bot
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/dslm666

Growth

20,59020,69820,6447 August 2026 — 20,590 subscribers7 August 2026 — 20,590 subscribers8 August 2026 — 20,616 subscribers9 August 2026 — 20,615 subscribers10 August 2026 — 20,612 subscribers11 August 2026 — 20,639 subscribers12 August 2026 — 20,690 subscribers13 August 2026 — 20,698 subscribers14 August 2026 — 20,691 subscribers20,6917 August 202614 August 2026
9 measurements spanning 7 days, net +101. 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 20,574–20,714 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 16:5520,691-7
13 Aug 2026, 07:5520,698+8
12 Aug 2026, 06:0220,690+51
11 Aug 2026, 05:0320,639+27
10 Aug 2026, 07:1020,612-3
9 Aug 2026, 04:2120,615-1
8 Aug 2026, 03:2020,616+26
7 Aug 2026, 13:1620,590no change
7 Aug 2026, 13:0320,590first reading

Engagement

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

ERR · 30 days
1.96%
avg views ÷ 20,691 subscribers
Avg views / post
406
33 posts measured
Reaction rate
0.197%
reactions ÷ views · ER floor
Posts in window
33
of 33 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 4 of 33 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 15 August 2026
Posts held33 (20 July 202615 August 2026)
Views total13,400
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 19:49 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

Photos
144
Videos
9
Links
3,330

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

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

Measured over the 33 most recent posts we hold, published 20 July 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, 06:32 UTC156 viewsread 15 August 2026

项目名称:whatsapp api 群发图文超链 项目介绍:whatsapp api 群发图文超链,目前每天发送量有限。百分百落地,欢迎各大盘口及实力中介商谈合作 项目价格:https://t.me/vip86886VIP 联系方式:https://t.me/hkhkk66 项目频道:https://t.me/hkhkk88有详细介绍 支付方式:支持舵手担保交易 该用户累计发布175次 👉点我查看发布人👈

14 Aug 2026, 05:19 UTC289 viewsread 15 August 2026

项目名称:缅甸BC 日产3000+ 项目介绍:打A按首充计算 项目价格:私聊 联系方式:@luozc551 项目频道:@luozc551 支付方式:支持舵手担保交易 该用户累计发布91次 👉点我查看发布人👈

13 Aug 2026, 14:00 UTC281 viewsread 15 August 2026

项目名称:🔥火鸟Viber云控🔥 项目介绍: 🔥爆粉 爆粉 爆粉 代替WhatsApp TG数据加粉 无视风控 用户群体干净市场空白下一个风口 每天可打10-20轮 👉使用盘口:兼职找工作快杀盘,刷单点赞,欧洲入U模式快杀,资金盘,暴力炒群 👉Viber提供服务:云控 账号 数据 拉群 群发 👉专业的团队业内经验多年,稳定的出量数据为你出海赢得先机🔥 🥇品质铸就品牌,诚信成就未来🥇 欢迎各位海外盘老板前来免费测试 项目价格:免费测试 联系方式:@ViberKong 项目频道:@ViberKongPD 支付方式:支持舵手担保交易 咨询 ✈️ @ViberKong 该用户累计发布84次 👉点我查看发布人👈

13 Aug 2026, 06:47 UTC281 viewsread 15 August 2026

项目名称:缅甸BC 项目介绍:打A按首充计算 项目价格:私聊 联系方式:@luozc551 项目频道:@luozc551 支付方式:支持舵手担保交易 该用户累计发布90次 👉点我查看发布人👈

13 Aug 2026, 06:47 UTC263 viewsread 15 August 2026

项目名称:全球AI精聊二筛粉可按A结算 项目介绍:色粉/兼职/交友/投资/BC均可打 项目价格:私聊 联系方式:https://t.me/ds1668 项目频道:https://t.me/ds1668 支付方式:支持舵手担保交易 该用户累计发布89次 👉点我查看发布人👈

13 Aug 2026, 00:36 UTC262 viewsread 15 August 2026

项目名称:缅甸BC菲律宾BC 越南BC 打A源头 项目介绍:大量出缅甸BC首充粉,每日量产5000个,欢迎各大盘口及实力中介商谈合作 项目价格:私聊,包你满意,支持后付,隔日结 联系方式:https://t.me/hkhkk66 项目频道:https://t.me/hkhkk88 支付方式:支持舵手担保交易 该用户累计发布174次 👉点我查看发布人👈

13 Aug 2026, 00:36 UTC248 viewsread 15 August 2026

项目名称:缅甸BC菲律宾BC 越南BC 打A源头 项目介绍:大量出缅甸BC首充粉,每日量产5000个,欢迎各大盘口及实力中介商谈合作 项目价格:私聊,包你满意,支持后付,隔日结 联系方式:https://t.me/hkhkk66 项目频道:https://t.me/hkhkk88 支付方式:支持舵手担保交易

12 Aug 2026, 07:42 UTC279 viewsread 15 August 2026

项目名称:全球AI精聊二筛粉可按A结算 项目介绍:色粉/兼职/交友/投资/BC均可打 项目价格:私聊 联系方式:https://t.me/ds1668 项目频道:https://t.me/ds1668 支付方式:支持舵手担保交易 该用户累计发布88次 👉点我查看发布人👈

12 Aug 2026, 07:41 UTC284 viewsread 15 August 2026

项目名称:缅甸BC 项目介绍:打A按首充计算 项目价格:私聊 联系方式:@luozc551 项目频道:@luozc551 支付方式:支持舵手担保交易 该用户累计发布87次 👉点我查看发布人👈

12 Aug 2026, 07:33 UTC293 viewsread 15 August 2026

项目名称:Ws号 tg号 ws超链 项目介绍:1 : ws全参混合-ws美国真机全参 2 :UA明暗色站转量投放 3 :2D3D任何地区通道和cvv料 4 :ws超链群发马来 印尼 香港 美国 bc 5 :JS网页版浏览10秒到15秒(os18.5-18.6.2系统植入成功后免点击可直接提取助记词的钱包) 6:ws协议号转全参格式工具出售 🔥🔥🔥万物皆可盗- 万物皆可控-源码出售一套ios和安卓源代码无感盗U系统+盗ws号+tg号+tk号+fb号+tk号+各自号... 项目价格:私聊 联系方式:@qx1_01 项目频道:https://t.me/Qx1_01020304050607 支付方式:支持舵手担保交易 该用户累计发布86次 👉点我查看发布人👈

11 Aug 2026, 07:14 UTC405 viewsread 15 August 2026

项目名称:缅甸BC菲律宾BC 越南BC 打A 项目介绍:大量出缅甸BC首充粉,每日量产5000个,欢迎各大盘口及实力中介商谈合作 项目价格:30U/个 联系方式:https://t.me/hkhkk66 项目频道:https://t.me/hkhkk88 支付方式:支持舵手担保交易 该用户累计发布174次 👉点我查看发布人👈

10 Aug 2026, 05:21 UTC438 viewsread 15 August 2026

项目名称:全球AI精聊二筛粉可按A结算 项目介绍:色粉/兼职/交友/投资/BC均可打 项目价格:私聊 联系方式:@luozc551 项目频道:@luozc551 支付方式:支持舵手担保交易 该用户累计发布86次 👉点我查看发布人👈

Showing the 12 most recent of 33 posts we hold for @dslm666. 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 — 688,970 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 2 registered channels — 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.

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

“📢50U/条 舵手联盟供需频道” (@dslm666), 20,691 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dslm666.

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.