Telegram RegisterThe public register of Telegram
Telegram profile photo for 茂名公告@mmgg0668

Channel

茂名公告@mmgg0668

@mmgg0668

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

5,876subscribers

-512 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002849734546
TypeChannel
Username@mmgg0668
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/mmgg0668

Growth

5,8766,3886,1327 August 2026 — 6,388 subscribers8 August 2026 — 6,375 subscribers11 August 2026 — 6,327 subscribers14 August 2026 — 6,152 subscribers17 August 2026 — 6,102 subscribers20 August 2026 — 5,978 subscribers24 August 2026 — 5,959 subscribers27 August 2026 — 5,904 subscribers30 August 2026 — 5,876 subscribers7 August 202630 August 2026
9 measurements spanning 23 days, net -512. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5,799–6,465 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 18:155,876-28
27 Aug 2026, 16:285,904-55
24 Aug 2026, 11:565,959-19
20 Aug 2026, 13:045,978-124
17 Aug 2026, 21:386,102-50
14 Aug 2026, 14:186,152-175
11 Aug 2026, 11:146,327-48
8 Aug 2026, 14:246,375-13
7 Aug 2026, 18:166,388first reading

Engagement

13 posts held, back to 22 February 2026the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 8 pagesof 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 13 posts for this entry, the most recent from 25 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

58 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 77.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4577.6%
👍712.1%
🔥35.17%
👎23.45%
💩11.72%

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 12 of the 13 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 58reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 22 February 2026 to 25 July 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.

Recent posts

25 Jul 2026, 14:19 UTC≈2,150 views1 reactionsread 12 August 2026
Photo

针对抽奖特殊情况的处理方案: 发起抽奖的老师/商家如果突发情况没办法继续上课,需要给予中奖的群友返还双倍色币的补偿。 一般普通抽奖是200色币,工兵抽奖是300色币。X2返还给中奖人即可 没有色币的老师/商家可以进行RMB1:10色币的比例给中奖的群友发红包补偿,100色币=10元 拒不履行的老师/商家永久拉黑不再接受上榜 2026.7.26起执行 2026.7.26日前有取消抽奖或是抽中老师不在茂名了的联系群主进行1比1的色币返还 好心茂名 @hxmm0668

1

16 Jun 2026, 11:32 UTC≈5,460 views3 reactionsread 12 August 2026
Photo

6月第一届好心茂名扶贫大使名单 排名不分先后,大家或是新手有什么不懂的在群里都可以@他们咨询,被@到的大使们有时间的情况下给予耐心解答。 由于有的人喜欢经常改名,大家认准群验证 扶贫大使 的后缀 好心茂名 @hxmm0668

2🔥1

13 Jun 2026, 15:37 UTC≈4,850 views1 reactionsread 12 August 2026

色币是什么? 色币是 好心茂名 @hxmm0668 群内流通的虚拟货币也是群内积分。 色币可以干什么? 主要用于日常抽奖/资源兑换使用,也可以进行变现交易。 一般抽奖所需200色币 工兵名额抽取所需300色币 资源兑换所需就需要根据价值设定 如何获取色币? 1、日常获取色币规则 2、资源兑换获取色币 3、交易买卖色币

1

13 Jun 2026, 15:29 UTC≈4,440 views3 reactionsread 12 August 2026

开通资源兑换色币机制 支持一切修车周边资源以及非修车资源的兑换 或是一些玩腻的私货 或者是一些修车干货 或是如何在内网劝良家下海的技巧 或者如果在内网攻略学妹的玩法 或是一些乱七八糟的周边 或是一些灰产网赚小项目 群体壮大,有需就有求,我们的目的不单单是为了出击修车。 不管是什么,只要你认为能拿得出手,都可以通过群内的积分商城去上架给群友们兑换,兑换色币所得归提供资源人所有(10%手续费) 上架兑换找群主 @maoming4 群友在群内发送‘色币兑换’即可唤出可兑换的资源商品列表

3

13 Jun 2026, 15:06 UTC≈4,000 viewsread 12 August 2026

平时不水群,用到色币时伤悲。 有很多新人以及不常水群的群友根本无法参与各种优惠活动,现开通群内色币流通交易机制 色币与人民币的汇率是1:10 可直接找群主 @maoming4 购买 群友之间也可以直接出售交易 汇率可以溢价到1:12(不得超过12的汇率,否则直接清空账户色币) 转色币有10%的手续费/私底下协商好谁支付。 转币直接私聊群主 发送;我要转1000色币给XXX,手续费我给/他给 🔥 好心茂名色币获取规则

21 Apr 2026, 12:16 UTC≈7,230 views7 reactionsread 12 August 2026
Forwarded from @mmhp0668Photo

七七 @Ting285 琪琪 @tianxinsj06 QQ1229547429 微信tian060880 支付宝119***@qq.com(**家) 七七骗定事件证据确凿,现已全面拉黑,鉴于琪琪那个号八九不离十也是同一个代聊开的号,为了避免风险一起拉黑。 事件经过纠纷处理得出结果,具体事情原由经过就不一一在这里细说经过了,大家留意账号避险就行。 茂名群 @maomingqun

7

5 Apr 2026, 17:14 UTC≈9,660 views7 reactionsread 12 August 2026

近期出现过不止一两例被骗定金的事情,而且都是我们榜上老师的头像资料,但实际不是我们榜上验证的TG号,只是骗子套用我们榜上老师的头像。这种情况只要细心一点就可以避免,联系老师需要在我们榜单上面去联系或者是在群导航去联系。那些私聊你的全部是骗子无一例外,实在拿捏不准就在群里问一下,收定金超过一百也视为是骗子。

6👎1

1 Apr 2026, 09:56 UTC≈9,690 views15 reactionsread 12 August 2026
Photo

我真的是让你们给蠢哭了,平时口水那么多,说这个投诉那个投诉,就不会花点口水教新手写报告教新手投诉吗?就算自持身份不好意思写报告可以直接私聊群主投诉,是中介也好是个人也好,只要货不对板/服务对不上号那自然就会有方案处理他们。整天在那里阿巴阿巴个不停背地里也没少享受平台给你们带来的便利吧? 另外最近的某些老师,你们是经过个人验证上榜的,多的我就不说了,课表服务做到位大家没什么好说,但凡我接到投诉超过两个与实际不符的即刻下榜。(我也不会让人恶意抹黑老师,一切依据事情实际情况处理) 新群友/潜水党避免踩坑,出击前多沟通多了解,想要好的出击体验就一定不能让小脑控制大脑,文明出击,互相尊重,老师好说话学生体验好,学生好说话老师也不会自断财路。 🚨新人出击教程之修车老司机速成记 【出击安全指南】 【防骗指南】 【出击需谨慎,谨防传染病】 【应急预案】 【出击经验分享篇】

7👍7💩1

31 Mar 2026, 11:27 UTC≈7,640 views1 reactionsread 12 August 2026

目前 无忧老师 小璇老师 各两张-200的工兵券 ,是沿用 排雷工兵计划 还是抽奖形式你们自行讨论一下,晚上十点前讨论不出结果就抽奖形式发放。

1

24 Mar 2026, 17:24 UTC≈9,770 views1 reactionsread 12 August 2026

近排有二五出没,老师接单多留心眼,大家出击注意安全,还没有进安全群的可以联系老师推荐进群 查看进入安全群条件

1

9 Mar 2026, 18:47 UTC≈12,100 views9 reactionsread 12 August 2026

🚨我们的老朋友财神跟人人喊打的射线恶魔混在一起玩,对待那位只能是零容忍,凡是好心茂名的商家或个人老师出现在财神那个群即刻下榜禁言处理 —— 🚨还有一个就是最近有空,之前找我换号的都可以联系我换了。拖了大家那么久非常抱歉。 —— 🚨新人出击教程之修车老司机速成记 【出击安全指南】 【防骗指南】 【出击需谨慎,谨防传染病】 【应急预案】 【出击经验分享篇】

8👎1

27 Feb 2026, 17:27 UTC≈11,800 views3 reactionsread 12 August 2026

非常时期非常手段,尽可能的去维护大家的养老基地,目前 @maomingqun 茂名群已经开启审核加入,如有需要进群的可以私信群主审核进群。 有权限的管理员切勿操作同意进群。

3

Showing the 12 most recent of 13 posts we hold for @mmgg0668. 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

Citation-graph rank — 1,055,001 of 1,627,445entries 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.

Forward network

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.

Mentions

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.

Cite this entry

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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“茂名公告@mmgg0668” (@mmgg0668), 5,876 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/mmgg0668.

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.