双向的可以联系机器人 @fanfanfk_bot
👍4

Channel
@dfmlaobashujuhao
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
26,690subscribers
-43 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002038841555 |
|---|---|
| Type | Channel |
| Usernames | @dfmlaobashujuhao @ssnb123 |
| Description | 只有一个本频道!其他皆是盗图假冒! |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 30 |
| On Telegram | t.me/dfmlaobashujuhao |
Gaming — 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 55% 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 |
|---|---|---|
| 10 Sept 2026, 18:22 | 26,690 | no change |
| 10 Sept 2026, 17:47 | 26,690 | -69 |
| 8 Sept 2026, 16:56 | 26,759 | -12 |
| 5 Sept 2026, 10:19 | 26,771 | +22 |
| 3 Sept 2026, 12:18 | 26,749 | -1 |
| 2 Sept 2026, 04:25 | 26,750 | -6 |
| 1 Sept 2026, 05:13 | 26,756 | +6 |
| 31 Aug 2026, 03:43 | 26,750 | +2 |
| 30 Aug 2026, 05:48 | 26,748 | +8 |
| 29 Aug 2026, 03:14 | 26,740 | +1 |
| 28 Aug 2026, 01:34 | 26,739 | +39 |
| 27 Aug 2026, 04:35 | 26,700 | +7 |
| 26 Aug 2026, 02:55 | 26,693 | -5 |
| 24 Aug 2026, 23:23 | 26,698 | -8 |
| 23 Aug 2026, 10:03 | 26,706 | +22 |
| 21 Aug 2026, 18:08 | 26,684 | +19 |
| 20 Aug 2026, 15:08 | 26,665 | +12 |
| 19 Aug 2026, 14:11 | 26,653 | -41 |
| 18 Aug 2026, 16:17 | 26,694 | -14 |
| 17 Aug 2026, 13:37 | 26,708 | first reading |
43 posts held, back to 16 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 61 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.
| Window | Rolling 30 days · latest post in window 10 September 2026 |
|---|---|
| Posts held | 43 (16 July 2026 – 10 September 2026) |
| Views total | 82,380 |
| Reactions total | 348 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 18:22 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.
Lifetime counters from Telegram’s own channel header, read 10 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
661 reactions across 42 posts, in 16 distinct kinds. The most used accounts for 48.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 321 | 48.6% | |
| 🤔 | 122 | 18.5% | |
| 😱 | 79 | 12.0% | |
| ❤ | 72 | 10.9% | |
| 💘 | 23 | 3.48% | |
| 🙊 | 11 | 1.66% | |
| 🌭 | 9 | 1.36% | |
| 🤓 | 8 | 1.21% | |
| 😁 | 5 | 0.756% | |
| ❤🔥 | 2 | 0.303% | |
| 🔥 | 2 | 0.303% | |
| 😴 | 2 | 0.303% | |
| 🤗 | 2 | 0.303% | |
| ✍ | 1 | 0.151% | |
| 😍 | 1 | 0.151% | |
| 🙏 | 1 | 0.151% |
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 43 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 661 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 43 most recent posts we hold, published 16 July 2026 to 10 September 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.
双向的可以联系机器人 @fanfanfk_bot
👍4
老品牌还得认准老八靠谱真实😝🙃😜🤨😜
👍7
下单卡网:https://lbuid.top
👍7🤔1
就这个质量吊打全网了
👍10
❤️三角洲每天凌晨免费送号[卡网里面] 三角洲全网最低价数据号来袭 老八数据号重磅回归全网最真实的数据号没有之一四年老店吊打全网上号器技术 30-60级10-50M价格6.5元 30-60级50-100M价格10元 30-60级100M以上价格20元 30-60级500-1000M价格30元 ⚠️卖假号死妈死全家出门被车撞 🥰 ❗️❗️关注✈️TG频道不迷路别让更多人被无良商家割韭菜: https://t.me/dfmlaobashujuhao ⚠️频道每日送免费数据号优先通知⚠️ 🥰认准数据号卡网: https://lbuid.top https://lbuid.top https://lbuid.top ❤️售后客服:@lbsjh68
👍9
卡网已经维护成功可以打开了 刚工作室抓了点号已经上架了时隔两个月我回归了必须使用我的上号器才能上号防冻结 用其他的登录不上就算登录上了也直接冻结
👍6
回归了兄弟们
👍5
暑假怎么这么快就要过去了兄弟们降价了补了新货不赚钱了成本价给你们做福利 全网最低价就有性价比最高质量的三角洲手游数据号! ✅认准数据号卡网:https://new.687faka.com/shop/ssnb123 退游黑号没有号主无需使用过滤器和禁玩系统避免被封号
❤8🤔5👍3
暑假怎么这么快就要过去了兄弟们降价了补了新货不赚钱了成本价给你们做福利 全网最低价就有性价比最高质量的三角洲手游数据号! ✅认准数据号卡网:https://new.687faka.com/shop/ssnb123 退游黑号没有号主无需使用过滤器和禁玩系统避免被封号
👍7❤1
Photo, posted without a caption
👍9
Photo, posted without a caption
👍9
Photo, posted without a caption
👍8🤔1😱1
Showing the 12 most recent of 43 posts we hold for @dfmlaobashujuhao. 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.
@dfmlaobashujuhao edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“三角洲老八数据号【三角洲数据号】” (@dfmlaobashujuhao), 26,690 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/dfmlaobashujuhao.
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.