Telegram RegisterThe public register of Telegram
Telegram profile photo for 蜜蜂公群 @mfdb2

Channel

蜜蜂公群 @mfdb2

@mfdb2

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

5,715subscribers

+1,271 since we began measuring on 16 August 2026

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

Register entry

Telegram ID-1002267300460
TypeChannel
Username@mfdb2
Created22 January 2025measured — dated from the channel’s first post
First recorded16 August 2026
Last confirmed live10 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/mfdb2

Growth

4,2045,7154,959.516 August 2026 — 4,444 subscribers17 August 2026 — 4,448 subscribers20 August 2026 — 4,452 subscribers24 August 2026 — 4,461 subscribers27 August 2026 — 4,448 subscribers30 August 2026 — 4,429 subscribers1 September 2026 — 4,291 subscribers6 September 2026 — 4,204 subscribers10 September 2026 — 5,715 subscribers16 August 202610 September 2026
9 measurements spanning 25 days, net +1,271. 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 3,977–5,942 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 19:005,715+1,511
6 Sept 2026, 04:194,204-87
1 Sept 2026, 19:134,291-138
30 Aug 2026, 02:134,429-19
27 Aug 2026, 03:084,448-13
24 Aug 2026, 06:134,461+9
20 Aug 2026, 05:354,452+4
17 Aug 2026, 12:044,448+4
16 Aug 2026, 19:314,444first reading

Engagement

13 posts held, back to 22 January 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 27 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
36s
Average length
36s

Measured directly from 1 video 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.

Recent posts

27 Jun 2026, 23:59 UTC≈4,260 viewsread 16 August 2026
Photo

———— 蜜蜂担保公群导航 ———— 💰资金类 • 收U放料公群 • 收U白资代付 • 收U出U一体 🤝合作类 • 招代聊招代理 • 彩票套利项目 🛎️服务类 • 支付宝解封 🧳买卖类 • 无 蜜蜂联系方式 | 公群规则 | 报备教学

6 Jun 2026, 02:33 UTC≈3,500 viewsread 16 August 2026
Video

蜜蜂公群报备教学: 做单人员打开机器人:@mfdb2bot 点击“发起报备”选择公群点击“发送” 第一步“点击自动复制报备模板” 第二步“点击此按钮后提交报备信息” 第三步:发送你的报备信息提交 ⚠️注意“按照顺序才能提交成功”

6 Jun 2026, 02:33 UTC≈2,850 viewsread 16 August 2026

蜜蜂担保机器人:@mfdb2bot 1. 公群老板点击“我的公群”查看在押公群,点击“帮助”查看记账说明,点击“供需”自助发布供需,享每周赠送2条。 2. 做单人员点击“帮助”查看报备说明,点击“解封”自助解除禁言,其他功能:验群/客服/双向/工具。

2 Jun 2026, 05:56 UTC≈3,060 viewsread 16 August 2026

🤝合作类 (注意:不在此导航里面的群都是假公群,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负,不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息,涉及个人隐私的可以部分以星号代替,并私聊发完整的。) —— 招代聊招代理 —— 166 欧易手机兼职招代聊 押金1666u 公群通道:https://t.me/+aOrYr0G9Fx0yNzM1 188 萝莉岛/打赏游戏招代理 押金1000u 公群通道:https://t.me/+X5UON5Gd1F9iODdl —— 彩票套利项目 —— 183 乐娱体育日结负盈利90 押金1000u 公群通道:https://t.me/+3H9E9pf90r8wYjA1 175 乐娱体育%90负盈利秒结账 押金1111u 公群通道:https://t.me/+FsiKIdGRvvphNmI1 .

2 Jun 2026, 05:56 UTC≈3,060 viewsread 16 August 2026

🧳买卖类 (注意:不在此导航里面的群都是假公群,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负,不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息,涉及个人隐私的可以部分以星号代替,并私聊发完整的。) —— 飞机号会员 —— 172 本群招租 公群通道:https://t.me/+SHqnhNgOM0IxNmQ1 .

2 Jun 2026, 05:56 UTC≈3,100 viewsread 16 August 2026

🛎️服务类 (注意:不在此导航里面的群都是假公群,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负,不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息,涉及个人隐私的可以部分以星号代替,并私聊发完整的。) —— 支付宝解封 —— 122 悟空解封支付宝/支出/延迟/投诉 押金1000u 公群通道:https://t.me/+8DtbQNDtBp01MzU1 .

2 Jun 2026, 05:55 UTC≈2,900 viewsread 16 August 2026

💰资金类 (注意:不在此导航里面的群都是假公群,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负,不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息,涉及个人隐私的可以部分以星号代替,并私聊发完整的。) —— 收U白资代付 —— 118 彭于晏收u白资代付 押金2000u 公群通道:https://t.me/+FoKIJG5jeYkyOWNl —— 收U出U一体 —— 113 兔兔白资收U出U一体 押金3000u 公群通道:https://t.me/+SaDJVr8cYyM1YTE1 .

2 Jun 2026, 05:55 UTC≈2,840 viewsread 16 August 2026

💰资金类 (注意:不在此导航里面的群都是假公群,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不担保群老板个人信誉,私聊或其他地方交易后果自负,不是在公群内交易发生的纠纷一律不受理,切勿私发地址、卡号等关键交易信息,涉及个人隐私的可以部分以星号代替,并私聊发完整的。) —— 收U放料公群 —— 126 飞机🐟招个人码(支付宝微信) 押金8000u 公群通道:https://t.me/+DFxhB4jbnEwzYjM1 133 信用卡网贷代还 卡码入金 押金3000u 公群通道:https://t.me/+tKOzt4HRodFjODg1 137 九社工作室色料寻卡码/网贷代还收u 押金2000u 公群通道:https://t.me/+82Uffh8xbIY3Zjdl 152 云扬小额飞机色料 押金2000u 公群通道:https://t.me/+B7Qt1PVWOP05ZDc1 161 无风险飞机料招个人

1 Nov 2025, 05:03 UTC≈5,770 viewsread 16 August 2026

蜜蜂社区由跑跑艾伦创建,从事多年灰产行业,运营跑跑群3年无污点,现筹备担保业务,承接公群专群供需,不接诈骗、卖人等公群入住,感谢大家对蜜蜂社区支持!

1 Nov 2025, 05:03 UTC≈6,500 viewsread 16 August 2026

蜜蜂担保联系方式: 跑跑群组:@bbbb1 跑跑频道:@bbbbf 蜜蜂大群:@mfdb0 蜜蜂供需:@mfdb1 蜜蜂公群:@mfdb2 蜜蜂担保/群管/验群/报备/客服/自助供需/自助解封一体机器人:@mfdb2bot 公群负责人:@mfdb 专群负责人:@mfdb3 备用联系号:@mfdb4 备用联系号:@mfdb6 1秒记住蜜蜂拼音:@mifeng 公群【唯一上押地址】👇点击即复制 TX9QakbK853SF2ynrTGBMi8rabTQcKh7k8 注意:上押只收USDT不收RMB,使用其他账户和地址的都是骗子!

1 Nov 2025, 05:03 UTC≈7,900 viewsread 16 August 2026

蜜蜂担保公群规则: 一、交易过程中所有账号、地址、截图相关信息一定要在群里进行交易,涉及个人隐私的可以部分以星号代替,并私聊发完整的。蜜蜂担保只保障在公群内的交易,私下交易或其他地方交易,纠纷不予受理,不要相信任何私聊,若交易出现纠纷,私聊截图不能做为证据。 二、资金类公群: 1. 公群老板需方/料方/收U/注意:公群置顶规则必需“明确说明”料性/保料/保时/收U地址,以及做单流程时效规则。由蜜蜂担保方群内置顶,规则变动和修改,联系蜜蜂重新置顶。 2. 公群老板注意:做单作业小群,保留群组发言记录,以防纠纷没有证据!群组近期删除记录48h可查,以防删记录赖账! 3. 作业小群注意:群组历史记录设置为“可见”。成员权限只打开消息和媒体,邀请链接及时更换,以防骗子进群假冒! 4. 记账机器人:@mfdb9bot 拉进群设置成管理,才能正常使用,群里发言“帮助”查看使用教学。 三、押金退还规则:确认关群下架

1 Nov 2025, 05:03 UTC≈8,310 viewsread 16 August 2026

蜜蜂担保收费标准: 蜜蜂公群开群免收月租费,赠送供需广告,开群联系负责人:@mfdb

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

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

“蜜蜂公群 @mfdb2” (@mfdb2), 5,715 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/mfdb2.

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.