Channel
@DuluShequ
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
936subscribers
-22 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002091203197 |
|---|---|
| Type | Channel |
| Username | @DuluShequ |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/DuluShequ |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 00:08 | 936 | -11 |
| 21 Aug 2026, 07:33 | 947 | -3 |
| 14 Aug 2026, 03:26 | 950 | -8 |
| 8 Aug 2026, 00:48 | 958 | no change |
| 7 Aug 2026, 12:37 | 958 | first reading |
20 posts held, back to 6 August 2025 — 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 27 October 2025. An engagement rate over an empty window would be a number about nothing.
5 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 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 2 of the 20 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 6 August 2025 to 27 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
2025年10月27日 蓝线看作双锯齿，红线看作联合形。 103528的上涨 (1）或者是蓝线的 xx 浪， (2）或者是红线的下一阶段，该阶段是上涨的，或者是 x 浪、 xx 浪或 b 浪，更复杂。如果是（1）还需要一次下跌，跌破蓝点103528，然后找到底部开始上涨。 如果是（2）需要涨到119398以上。 117996很关键，超过它有可能否定 #波浪理论学习
❤3
#BTC 夜間埋伏多📈 進場：105800-104800附近 止盈：110500-113500-🛫 止損：103800
#ETH 夜間掛單多📈 進場：3803-3760附近 止盈：4050-4150-🛫 止損：3700
2025年9月5日BTC日线图 8月15号说了124474是顶 9月2号说了107255是小级别底有可能进行反弹。头挺努力了，但不超过113000是无效努力，必须刺破113000才能转强。 #波浪理论学习
❤2
2025年9月3日BTC日线图 8月15号就说了124474是顶， 昨天说了”107255是个小级别底，有可能进行反弹 昨天已经进行了反弹， 112075是反弹的压力位。如果能突破它则反弹继续。 黄金创历史新高，离3720还远吗？黄金调整4个月期间有多少人失去了信心和耐心？甚至还有人认为已经历史大顶。很荒谬吧？英伟达跳空下跌，离163.96元又近了一点。当华尔街大行们纷纷看高200元的时候，我的看法就是跟他们反着来。 #波浪理论学习
2025年9月2日BTC日线图 8月15号就说了124474是顶， 黑线跌了3段。昨天说了"107350不能假设是底", 果然又跌出了新低到107255。 107255是个小级别底，有可能进行反弹。支撑位仍然是绿色虚线105386。112075是反弹的压力位。 #波浪理论学习
2025年9月1日BTC日线图 8月15号就说了124474是顶 上周说了好几天“108666起没有上升推动浪也还没有上升引导楔形，无法看作底部。 得到了验证，果然继续下降。现在是黑线第3段的继续。 107350没有好出身，不能假设是底 支撑位在画了好多天的绿色虚线105386。 #波浪理论学习
2025年8月20日BTC日线图 124474已经是蓝点的顶。 如果跌破110694是扩大级别变成红点的顶。 今天的压力位置在117915， 上涨不超过2340刀之前不构成反弹还在下跌中， 超过2340刀以后才是反弹。 #波浪理论学习
2025年8月19日BTC日线图 124474已经是小级别顶。 如果跌破110694是扩大级别，这里是多头必守的。 今天的压力位置在117587， 收盘低于它仍有下跌动力，高于它才能反弹。 #波浪理论学习
2025年8月18日BTC日线图 8月13号和14号连续两天说了 ”这次上涨在创新高以后会有回撤风险。 两个意思， 一个是创新高，，一个是小心回撤。 124474已经小级别做顶。 今天压力线在117257，低于它则还有不跌动力。 74000以来的上涨趋势线今天被跌破 如果跌破它2天以上收不回去，则可能接续下跌，下跌最少13780刀。 #波浪理论学习
2025年8月15日BTC日线图 连续两天说了“这次上涨在创新高以后会有回撤风险。” 现在创新高了，也开始回撤， 124474已经小级别做顶。 今天压力线在121688，价格低于它则还有下跌动力。 74000以来的上涨趋势线今天在116148，如果跌破它则可能结束这个上涨 下跌最少13780刀。 #波浪理论学习
2025年8月14日BTC日线图 上涨到123218——135096之间都是正常的。 今天已经实现进入该区域。 这次上涨在创新高以后会有回撤风险。 从最高点会有超过13780刀的下跌。 这个最高点目前未知。 #波浪理论学习
Showing the 12 most recent of 20 posts we hold for @DuluShequ. 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“嘟噜社区” (@DuluShequ), 936 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/DuluShequ.
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.