😃😀😃 📣在家无聊想要兼职赚点零花钱的 ✅2026最赚钱项目 一台设备 两台设备均可操作 ✅不死卡 纯绿色 无风险 无押金 无套路 ✅有耐心 听指挥 几个小时随便搞大几百 ✅做单联系 @wanfengZ6 ✅结账记录查看https://t.me/wanfengZ3 😄😄😄😄😄😄😄😀
👍7
Signed ᅠ隐藏用户『@KSZZ660』

Channel
@BYNMOD
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,788subscribers
+36 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003562773306 |
|---|---|
| Type | Channel |
| Username | @BYNMOD |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/BYNMOD |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 16:55 | 10,788 | -8 |
| 2 Sept 2026, 06:13 | 10,796 | -23 |
| 1 Sept 2026, 05:05 | 10,819 | -3 |
| 31 Aug 2026, 04:16 | 10,822 | +3 |
| 30 Aug 2026, 03:16 | 10,819 | -8 |
| 29 Aug 2026, 05:35 | 10,827 | +12 |
| 28 Aug 2026, 04:13 | 10,815 | -15 |
| 27 Aug 2026, 05:17 | 10,830 | +4 |
| 26 Aug 2026, 02:33 | 10,826 | +22 |
| 25 Aug 2026, 05:24 | 10,804 | +8 |
| 24 Aug 2026, 03:14 | 10,796 | -7 |
| 22 Aug 2026, 14:11 | 10,803 | +3 |
| 21 Aug 2026, 07:13 | 10,800 | +13 |
| 20 Aug 2026, 07:05 | 10,787 | +24 |
| 19 Aug 2026, 09:54 | 10,763 | -11 |
| 18 Aug 2026, 12:18 | 10,774 | -2 |
| 17 Aug 2026, 13:17 | 10,776 | +3 |
| 16 Aug 2026, 06:15 | 10,773 | +5 |
| 14 Aug 2026, 14:38 | 10,768 | +19 |
| 13 Aug 2026, 05:22 | 10,749 | first reading |
138 posts held, back to 5 August 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 30 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 136 of 137 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 138 (5 August 2026 – 1 September 2026) |
| Views total | 46,863 |
| Reactions total | 1,377 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 20:10 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.
Measured directly from 4 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.
1,391 reactions across 136 posts, in 14 distinct kinds. The most used accounts for 85.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,191 | 85.6% | |
| 🕊 | 61 | 4.39% | |
| ❤ | 56 | 4.03% | |
| 🤯 | 29 | 2.08% | |
| 😡 | 14 | 1.01% | |
| 😍 | 12 | 0.863% | |
| 😁 | 8 | 0.575% | |
| 🥰 | 8 | 0.575% | |
| 😭 | 4 | 0.288% | |
| 🤩 | 3 | 0.216% | |
| 😈 | 2 | 0.144% | |
| 🏆 | 1 | 0.072% | |
| 👏 | 1 | 0.072% | |
| 😢 | 1 | 0.072% |
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 137 of the 138 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,391 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 138 most recent posts we hold, published 5 August 2026 to 1 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.
😃😀😃 📣在家无聊想要兼职赚点零花钱的 ✅2026最赚钱项目 一台设备 两台设备均可操作 ✅不死卡 纯绿色 无风险 无押金 无套路 ✅有耐心 听指挥 几个小时随便搞大几百 ✅做单联系 @wanfengZ6 ✅结账记录查看https://t.me/wanfengZ3 😄😄😄😄😄😄😄😀
👍7
Signed ᅠ隐藏用户『@KSZZ660』
Photo, posted without a caption
👍7
Signed 挽小婷 【比翼鸟官方客服】回消息速度比你女朋友甩你都快
Photo, posted without a caption
👍6🥰1
Signed 挽小婷 【比翼鸟官方客服】回消息速度比你女朋友甩你都快
Photo, posted without a caption
👍5❤1
Signed 挽小婷 【比翼鸟官方客服】回消息速度比你女朋友甩你都快
😍😍😍打单,带老板吃豆😋
👍6🤯3
✔️蜜雪高质量无限授权源头自营✔️ ➡️😃😃退游号😃😃退游号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 🥇一年诚信经营,三年售后兜底 😙😍😗😋😝🙃😜🤨😜 👍👍购买链接: https://new.818fka.com/shop/MH6 https://new.818fka.com/shop/MH6 👍唯一售后客服 @MXSH678 🤝 📱唯一频道: @MXSJH6 🔥购买必须录制全程视频 方便售后 支持首次登录任何问题售后 ⚠️二卖出门被车撞死⚠️ ⚠️跑路出门被车撞死⚠️ 📱数据号通知频道【务必加入】 https://t.me/MXSJH6
👍8
Signed 牛子鸡
已重新上传至网盘
👍14
Signed 小屿 大王
紧急更新v9
👍15🥰2
Signed 犹入无人之境
用了比翼鸟,感觉爆率都变高了😋😋😋
👍13🕊3❤2🤯2
Signed 晴天雨-海的那边是什么😭😭😭
已经上传V8 最新卡网:https://www.bodonglexiang.top/shop/888JQ 反馈 @WXT588
👍9❤2
Signed 犹入无人之境
马上更新启动器
👍8🥰1
Signed 犹入无人之境
😃😀😃 📣在家无聊想要兼职赚点零花钱的 ✅2026最赚钱项目 一台设备 两台设备均可操作 ✅不死卡 纯绿色 无风险 无押金 无套路 ✅有耐心 听指挥 几个小时随便搞大几百 ✅做单联系 @wanfengZ6 ✅结账记录查看https://t.me/wanfengZ3 😄😄😄😄😄😄😄😀
👍13❤1🕊1
Signed ᅠ隐藏用户『@KSZZ660』
Showing the 12 most recent of 138 posts we hold for @BYNMOD. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“比翼鸟官方频道” (@BYNMOD), 10,788 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/BYNMOD.
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.