正在处理售后了授权地址到时候我再对接一下别的
👍7
Signed 羽墨(全网收广告位)

Channel
@YUMONB6688
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
19,194subscribers
-5,849 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002309412596 |
|---|---|
| Type | Channel |
| Username | @YUMONB6688 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/YUMONB6688 |
Ecommerce storefront — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:00 | 19,194 | -797 |
| 16 Sept 2026, 06:37 | 19,991 | -486 |
| 14 Sept 2026, 16:02 | 20,477 | -288 |
| 13 Sept 2026, 05:42 | 20,765 | -628 |
| 11 Sept 2026, 07:41 | 21,393 | -937 |
| 8 Sept 2026, 15:58 | 22,330 | -1,235 |
| 5 Sept 2026, 10:57 | 23,565 | -945 |
| 3 Sept 2026, 12:00 | 24,510 | -143 |
| 2 Sept 2026, 09:42 | 24,653 | -388 |
| 1 Sept 2026, 07:08 | 25,041 | -11 |
| 31 Aug 2026, 10:12 | 25,052 | -10 |
| 30 Aug 2026, 12:43 | 25,062 | -7 |
| 29 Aug 2026, 10:27 | 25,069 | -11 |
| 28 Aug 2026, 12:14 | 25,080 | +8 |
| 27 Aug 2026, 14:43 | 25,072 | +13 |
| 26 Aug 2026, 16:57 | 25,059 | -3 |
| 25 Aug 2026, 14:58 | 25,062 | +5 |
| 24 Aug 2026, 17:45 | 25,057 | +6 |
| 23 Aug 2026, 05:34 | 25,051 | +7 |
| 21 Aug 2026, 16:46 | 25,044 | first reading |
52 posts held, back to 22 July 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 59 pages of 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 8 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 52 (22 July 2026 – 29 August 2026) |
| Views total | 3,703 |
| Reactions total | 44 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:39 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.
179 reactions across 42 posts, in 8 distinct kinds. The most used accounts for 65.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 117 | 65.4% | |
| ❤ | 44 | 24.6% | |
| 😍 | 4 | 2.23% | |
| 👀 | 3 | 1.68% | |
| 💘 | 3 | 1.68% | |
| 😇 | 3 | 1.68% | |
| 🥴 | 3 | 1.68% | |
| 🥰 | 2 | 1.12% |
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 42 of the 52 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 179 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 52 most recent posts we hold, published 22 July 2026 to 29 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.
正在处理售后了授权地址到时候我再对接一下别的
👍7
Signed 羽墨(全网收广告位)
喵的手刚刚好我直接回来给你们处理售后了兄弟们不要急手还是有点疼 客服:@YUMONB667 客服:@wuqiunb886 客服上班时间 早上:7:00点—12:00点 下午:15:00点—20:00点 晚上:22:00点—凌晨2点 卡网1号:https://xl.8x.fit/shop/YUMONB6688 卡网2号:https://xl.8x.fit/shop/YUMO666
👍4❤1
Signed 羽墨(全网收广告位)
新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。
Signed SOSO搜搜
#频道互推 #相似推荐 ------------------------------ 📢 三角洲威龙数据号【三角洲0.1数据号】 📢 ws群发【WhatsApp群发】ws打粉、引流 📢 WS实卡接码【绮梦号商】 📢 代认证/备案域名加急/注册营业执照/ 📢 手机卡电销卡 📢 全球海外注册卡流量卡邮寄 📢 大头四方实卡接马⚠ 📢 抖音兼职🅥灰产赚钱项目 📢 繁花FB IG 推特 TK源头账号批发 📢 668官方靓号地址业务 ------------------------------ ☁️ 互推入口:@sosoo
Signed SOSO搜搜
出大事了客服被狗咬了现在要去医院😭😭😭
👍10❤3😇3🥴2
Signed 羽墨(全网收广告位)
兄弟们售后我都看到了晚上给你们处理
👍2
Signed 羽墨(全网收广告位)
数据号反馈感谢兄弟的支持😘买了羽墨数据号都不用羡慕别人的极品号了 ✅全部高质量 价格低至0元 售后 @YUMONB77 反馈 @YUMONB77 👍1号卡网:https://shop.682fk.com/shop/@666666666 👍2号卡网:https://lv.youxi186.com/shop/331
❤1👍1
Signed 羽墨(全网收广告位)
刷到一个频道后,通常还想找更多同类入口。 SOSO 精选频道会随机推荐一批已收录频道。 适合继续发现相近内容。
👍1
Signed SOSO搜搜
#频道互推 #相似推荐 ------------------------------ 📢 三角洲威龙数据号【三角洲0.1数据号】 📢 ws群发【WhatsApp群发】ws打粉、引流 📢 代认证/备案域名加急/注册营业执照/ 📢 WS实卡接码【绮梦号商】 📢 手机卡电销卡 📢 全球海外注册卡流量卡邮寄 📢 大头四方实卡接马⚠ 📢 抖音兼职🅥灰产赚钱项目 📢 668官方靓号地址业务 📢 繁花FB IG 推特 TK源头账号批发 ------------------------------ ☁️ 互推入口:@sooo
👍1
Signed SOSO搜搜
客服在线回复售后中前几天没有时间补了一些三角洲数据号今天会把售后处理完毕 客服:@YUMONB667 客服:@wuqiunb886 客服上班时间 早上:7:00点—12:00点 下午:15:00点—20:00点 晚上:22:00点—凌晨2点 卡网1号:https://xl.8x.fit/shop/YUMONB6688 卡网2号:https://xl.8x.fit/shop/YUMO666
👍8
Signed 羽墨(全网收广告位)
1
👍6💘1
Signed 羽墨(全网收广告位)
新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。
👍1
Signed SOSO搜搜
Showing the 12 most recent of 52 posts we hold for @YUMONB6688. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“羽墨数据号「免费数据号」” (@YUMONB6688), 19,194 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/YUMONB6688.
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.