Channel
@zzzzee
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
5,818subscribers
-335 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002417081718 |
|---|---|
| Type | Channel |
| Usernames | @mysqfw @zzzzee |
| 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 | 20 August 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 20 August 2026 |
| On Telegram | t.me/zzzzee |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 15:33 | 5,818 | no change |
| 20 Aug 2026, 12:52 | 5,818 | -92 |
| 17 Aug 2026, 14:15 | 5,910 | -4 |
| 17 Aug 2026, 10:02 | 5,914 | -49 |
| 14 Aug 2026, 14:37 | 5,963 | -18 |
| 13 Aug 2026, 16:05 | 5,981 | -78 |
| 11 Aug 2026, 14:34 | 6,059 | -11 |
| 10 Aug 2026, 22:04 | 6,070 | -79 |
| 8 Aug 2026, 13:36 | 6,149 | -8 |
| 8 Aug 2026, 07:51 | 6,157 | +4 |
| 7 Aug 2026, 14:31 | 6,153 | no change |
| 7 Aug 2026, 14:19 | 6,153 | first reading |
43 posts held, back to 7 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 9 pagesof 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 11 of 43 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 43 (7 August 2026 – 11 August 2026) |
| Views total | 8,665 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:35 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 13 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.
12 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 50.0% | |
| 👍 | 6 | 50.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 11 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 12reactions 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 7 August 2026 to 11 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.
#行业曝光 ——打击骗子👊 骗票骗路费 🤖行业曝光 ——打击骗子请使用Bot: @K9Pay 🤖行业曝光 ——打击骗子请使用Bot: @K9Pay 本频道仅用于公开披露、悬赏通告及发布重要资讯或新闻。《真伪请自行甄别，涉及欺诈概不承担责任》 茂亿娱乐：@zaaaa，提供即时游戏体验及一键推广服务。 反骗交流群 反骗客服号 东南亚快讯 U地址监控 TRX兑换 TRX兑换群 票务代付号 机器人定制 资源信息站 全网资源库 TG反骗中心 茂亿娱付通 茂亿娱乐群 合顺付四方 老司机必备 记账机器人
#行业曝光 ——打击骗子👊 很会骗，到地方了抢劫蛇头。 🤖行业曝光 ——打击骗子请使用Bot: @K9Pay 🤖行业曝光 ——打击骗子请使用Bot: @K9Pay 本频道仅用于公开披露、悬赏通告及发布重要资讯或新闻。《真伪请自行甄别，涉及欺诈概不承担责任》 茂亿娱乐：@zaaaa，提供即时游戏体验及一键推广服务。 反骗交流群 反骗客服号 东南亚快讯 U地址监控 TRX兑换 TRX兑换群 票务代付号 机器人定制 资源信息站 全网资源库 TG反骗中心 茂亿娱付通 茂亿娱乐群 合顺付四方 老司机必备 记账机器人
👍2❤1
#行业曝光 ——打击骗子👊 寻找一个老大哥，原蝙蝠号是99666，飞机是这个，有认识的或许本人看到联系我一下。 🤖行业曝光 ——打击骗子请使用Bot: @K9Pay 🤖行业曝光 ——打击骗子请使用Bot: @K9Pay 本频道仅用于公开披露、悬赏通告及发布重要资讯或新闻。《真伪请自行甄别，涉及欺诈概不承担责任》 茂亿娱乐：@zaaaa，提供即时游戏体验及一键推广服务。 反骗交流群 反骗客服号 东南亚快讯 U地址监控 TRX兑换 TRX兑换群 票务代付号 机器人定制 资源信息站 全网资源库 TG反骗中心 茂亿娱付通 茂亿娱乐群 合顺付四方 老司机必备 记账机器人
❤2
#国内新闻 中国警方突袭抓捕潜藏国内的打粉引流团伙 👉新闻频道 牛马南洋录 👉社区 牛马生活录 投稿/爆料/澄清 👉：@xunyai @zzzzoo
#群友分享：给兄弟们分享一下我的一次艳遇。 我和我的兄弟朋友以及同事们经常去一家烧烤店，去一次就好说河道三四点，还经常和喝到天亮。来到大寨子，钱包涨不涨不知道，但是酒量那肯定是涨了不少了。别人喜欢喝Tiger，我只喜欢吴哥。 因为感觉Tiger口味太淡了，像喝水一样，还是吴哥有劲一点。因为经常去这家烧烤店喝酒，认识了几个妹子，大家也就经常一起喝酒。 有时吃完烧烤不尽兴，就去KTV唱歌继续喝。在KTV喝上头了，偶尔就会溜一下冰。有一次几个妹子喊我去KTV喝，三个妹子加我一个男的。你来我往，喝的都上头了，我就脱光上衣，光着膀子跟她们三个女的喝。 本人经常健身，体型不错，再加上本身有点小帅，随意妹子都喜欢跟我玩。后面为了玩的尽兴一点，就开始溜冰了，这东西容易上头，然后我们就借着劲玩的更大了，直接划拳比赛，输了的脱衣服。几轮下来，大家几乎都光光的了。 再加上酒精和冰的作用，妹子们也情不自禁了，于是就发生了大家能够想象的画面，吕…
#群友分享 看了这个视频你还敢招惹泰国扶手吗？ 上来就是一个蓄意轰拳，尼玛这一拳下去，能给你篮子打爆😂。表面上老公老公的叫着，吵架了你还真不一定能打过她，毕竟卖逼也是体力活整天都在锻炼，而你整天敲键盘，谁更强不言而喻。 PS：难怪泰国人妖能参军，诚不欺我🤣 👉新闻频道 牛马南洋录 👉社区 牛马生活录 投稿/爆料/澄清 👉：@xunyai @zzzzoo
❤1
色情直播给电诈引流，西安警方端掉窝点26人全部被采取刑事强制措施 8月9日公开消息显示，西安周至县公安局侦破一起电诈引流黑灰产案件。警方此前发现，周至县青化镇胡某多次将个人短视频账号出租给他人，用于色情直播引流并从中获利。 经过进一步侦查，警方锁定该引流窝点。8月5日，周至县公安局刑侦大队联合反特大队出动30余名警力，在西安市某区一家电竞酒店展开收网，当场抓获26人，查获涉案电脑2台、手机27部。 经查，该团伙以王某为首，以每半小时100元的价格租用他人短视频账号，通过色情直播诱导人员进入群聊，再为诈骗团伙提供引流服务。 目前，抓获的26人均已被采取刑事强制措施，案件正在进一步办理中。 👉新闻频道 牛马南洋录 👉社区 牛马生活录 投稿/爆料/澄清 👉：@xunyai @zzzzoo
#群友投稿：未来3—10年，一些可能越来越明显的趋势判断 1、不管什么监管，不管什么国家，未来整体环境只会越来越规范、越来越严格。钱会越来越难赚，过去那种靠信息差、胆子大、风口来的赚钱机会会越来越少。真正能够持续赚到钱的，依然是资本、技术、资源以及掌握核心生产力的人。 2、电诈行业会越来越难做，再也很难回到2022年前后那种所谓的“辉煌时期”。从去年到今年，整个行业已经明显走下坡路，全球反诈、跨境执法、资金监管都在持续加强。过去那种随便拉几个人、租个地方就能赚钱的时代基本过去了，这个行业未来只会越来越边缘化。 3、赌博行业短期内依然会存在，而且很难彻底消失。赌博存在了几千年，不会因为某一个国家监管就彻底消失。未来可能会越来越集中化、正规化，普通人越来越难从中获利，但真正掌握资源、平台、资金和流量的人，依然会有利润空间。 4、Telegram这类即时通讯软件未来依然会长期存在。它的服务器架构、隐私保护、生态以及全球用户基础，…
❤1
#网友分享 昨晚打PG，600打到2000没下，后来又送回去1000。剩下1000赢了400，就喊朋友出来吃饭，花了200多，之后又去打了一炮，花了600，最后还倒贴。 现在想想还不如不赢，钱基本都让弟弟享受了，弟弟爽了，钱也没了。前后干了两炮，给她干高潮两次，自己没射，后面又让我后入干了一炮。 还是想提醒一下，现在大环境不好，有钱尽量存起来，也要管住自己的小弟弟。做的时候爽，做完又心疼钱，实在忍不住就自己解决一下，别像我一样最后管不住自己。 👉新闻频道 牛马南洋录 👉社区 牛马生活录 投稿/爆料/澄清 👉：@xunyai @zzzzoo
👍1
#群友吐槽：各大盘总都看看吧，这就是公司和公司之间的差距。 别人家的公司业绩不好，解散了还和和气气地发遣散费；我们公司业绩不好，就要电你😅。五十多人充值50W人民币，不想想项目原因，到处找员工原因。粉都没有，接粉工具都有问题，那你们管理层不处理，员工上班不睡觉、不刷抖音干嘛？靠着加班就有业绩吗？ 哎，东南亚，这苦逼日子什么时候是个头啊。想跳槽，不认识好公司；不跳槽，每个月底薪等死，还担惊受怕的，怕遣返回去坐牢。现在出国当狗推，真不如进厂当厂狗了，起码还能免费玩几个厂妹，舒服舒服。 👉新闻频道 牛马南洋录 👉社区 牛马生活录 投稿/爆料/澄清 👉：@xunyai @zzzzoo
#突发事件 干拉省大金欧市一名副警察局长被发现死在卫生间内，目前具体死因还不清楚，初步怀疑可能是谋杀。 👉新闻频道 牛马南洋录 👉社区 牛马生活录 投稿/爆料/澄清 👉：@xunyai @zzzzoo
盗窃空置园区？西港警方逮捕4名嫌疑人 今天上午，西港4分区行政警察局联合当地民防力量，在西港4分区4村4组一处废弃大楼内成功破获一起撬门入室盗窃案。 行动中，警方当场抓获4名涉案嫌疑人。目前，嫌疑人已被移交西港市警察局，以便接受进一步讯问并依法按法律程序处理。 👉新闻频道 牛马南洋录 👉社区 牛马生活录 投稿/爆料/澄清 👉：@xunyai @zzzzoo
Showing the 12 most recent of 43 posts we hold for @zzzzee. 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.
Citation-graph rank — 931,408 of 1,584,733entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
@zzzzee named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“牛马南洋录” (@zzzzee), 5,818 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/zzzzee.
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.