Channel
@erdao111
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
760subscribers
-63 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002400697973 |
|---|---|
| Type | Channel |
| Username | @erdao111 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/erdao111 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 15:16 | 760 | -36 |
| 31 Aug 2026, 15:45 | 796 | -16 |
| 24 Aug 2026, 07:08 | 812 | +4 |
| 15 Aug 2026, 17:57 | 808 | -15 |
| 15 Aug 2026, 01:30 | 823 | first reading |
20 posts held, back to 8 June 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.
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 14 August 2026. An engagement rate over an empty window would be a number about nothing.
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 5 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 1 reactions 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 8 June 2026 to 14 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.
只打三方产品 ！ ！ ！（要打直流的去问其他人） 点位；对私9个点，对公7个点（法人不接受同台的不要） 接受点位者先； 1，查看法人微信资质（经营账户是否正常可以收付款，不正常的不要）（发截图我）开三方进款号需要用到微信，且微信经营账户必须是正常的。但不是用微信收款 2，让法人准备好新的手机号3-4个，注册新微信用（历史不用的请找回重新绑定新手机号）查看公户状态请先自我测试85块进出款正常（发截图我）公户日限额(发截图我） 3，（女法人，不配合的法人，公户以前跑过分）都不要，以贷款骗来的法人请先洗好脑在联系 4，华夏 民生 工行 招行不要，其他10万额度以上都可以来谈 5，法人带 - 执照 基本户资料 u盾 公章 绑定执照和u盾的手机卡 3-4个注册微信的手机卡，落地 成都，开工时间10天左右 手里有公户的可以联系我，同台打，不用上押！
精聊一道现存规则 现存回u交易规则 1需方在柜台无卡现金存款给供方，ATM机现金存款，供方回USDT。 2:柜台存现， 限制单笔金额20000起步， 3只接ATM或者柜台无卡现存不接任何形式APP转账，飘账到账以后保24小时或退回，工行需保撤回，保验证 射完给小票+身份证(缺一不可)拿卡默认规则 4.出图查账回款，保证效率，没有合格回单给补.需方发出存款凭证后供方15分钟内查账，若无法查账，或者不回复，时间到默认到账，加账。提供身份证正面回单正面和撕毁回单照片。 5.拉停，要需方同意，需方不同意，不得拉停，如卡死拉停，需要30分钟，需方尽力配合，联系客户，如有特殊情况联系不到客户双方协商损失！ 6.需方保供方单笔进款开始算24小时内司法，天眼查为准。如需方保时内导致司法冻结，保时内司法，供方需在保时内反馈，超时反馈无效，不认可，卡余大于单笔入金赔单笔，卡余小于单笔入金赔卡余。如遇到到银行风控止付，没有实际报警人，长…
8月3日，4日，5日，6日，7日外出，会不定时看飞机
做六合彩的看清楚规则，保72小时司法，保时内出司法，只赔付200u码费，没有一比一赔付
招🕶经营小额二道码-日量百万欢迎各大承兑车队合作 二道招反扫车，点位天花板 实力车队可以保量，小车可以扶持 业务联系人： @xiaoyi080
能吃转账码的来一个，电商精聊料，保当天司法投诉
来个大额反扫枪车，底料常规
微信经营码开通流程: 1.打开微信搜索“微信收款助手” 2.点击“开通经营码” 3.提交身份证、银行卡、店铺图片（网上找图就行） 4.选择营业范围、营业地区 5.提交后1-3天出结果，大部分当天出。 注:不是所有号都可以开通，没有申请入口的就是不能开。
常规二道，境外微信零钱出，要微信经营码置顶打，单笔千内，量大管饱
做六合彩的车一定要避开周六日，这两天不做推广，量不大的
每天垫钱，垫不动了，不管是谁，做业务就走专群，空放免谈！
二道来能吃量的微信经营码车，只要能跟上节奏，量管够
Showing the 12 most recent of 20 posts we hold for @erdao111. 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.
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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“小怡业务对接” (@erdao111), 760 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/erdao111.
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.