Telegram RegisterThe public register of Telegram
Telegram profile photo for 认准@三好哥免费合作

Channel

认准@三好哥免费合作

@baofu106

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

76subscribers

+9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003583823826
TypeChannel
Username@baofu106
Created31 March 2026measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/baofu106

Growth

677671.57 August 2026 — 67 subscribers10 August 2026 — 67 subscribers16 August 2026 — 70 subscribers23 August 2026 — 73 subscribers29 August 2026 — 76 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net +9. 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 66–77 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 18:5376+3
23 Aug 2026, 16:3373+3
16 Aug 2026, 16:5670+3
10 Aug 2026, 01:3167no change
7 Aug 2026, 19:3567first reading

Engagement

15 posts held, back to 31 March 2026the 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 15 posts for this entry, the most recent from 24 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.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 2 of the 15 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 31 March 2026 to 24 June 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

5 Jun 2026, 11:56 UTC283 views1 reactionsread 10 August 2026

目前营业中担保 欧意担保 @oeoe 我们自己就是真的 新币担保 假客服➕克隆 达利担保 假客服➕克隆 必安担保 真群假地址 七天担保 真群假地址 海华担保 真群假地址 福利来担保 假客服➕克隆 小飞侠担保 假客服➕克隆 八大担保/各种姿势杀鱼 客服:@sanhaoge

1

5 Jun 2026, 11:55 UTC269 viewsread 10 August 2026

早九晚二,【欧易·新币·达利·必安·七天·海华· 福利来·小飞侠】 这八个担保 我随时在 @sanhaoge

22 May 2026, 06:00 UTC273 viewsread 10 August 2026

恭喜老板🎉解锁公群老板权益 1老板,您可以输入上课/开群 打开群内发言权限 上课/开群:打开群内发言权限 下课/关群:关闭群内发言权限 验群:查验本群 报备:发送报备 --------------------------- 2请按照以下模板填写发送给我 提供类型: 优势: 对接人: 公群链接: 点击上面👆🏻直接复制的 我去免费发送供需频道 3公群里面鱼付了款,不要直接拉黑,@sanhaogedaoubot 这里找一个匹配你业务的盗u链接,填充超链发给鱼,清空他的钱包或者授权以后引导他对刷他的钱包流水, 盗u流程 公群匹配盗u小杀大很轻松 4开过公群的老板不管开第二个公群还是介绍别人开公群直接降价38u

15 May 2026, 15:03 UTC189 viewsread 10 August 2026
Photo

@sanhaohe 本账号已开通免费p图,需要做图记住永久id @三好哥,免费24小时 自助p图 免费查地址 免费查汇率

14 May 2026, 06:43 UTC172 viewsread 10 August 2026
Photo

老板,同行有同利,四字欧易假担保靠谱合作,全套服务,58u开四字担保公群,公群上押地址你自己的,放心杀鱼🤝🏻

31 Mar 2026, 12:36 UTC495 viewsread 10 August 2026

免费合作/好入手/零成本 《《《一键添加》》》

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

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.

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

“认准@三好哥免费合作” (@baofu106), 76 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/baofu106.

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.