Telegram RegisterThe public register of Telegram
Telegram profile photo for 搞钱项目 点这联系

Channel

搞钱项目 点这联系

@FBTYSAZMJH

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

76subscribers

+2 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-1003321864013
TypeChannel
Username@FBTYSAZMJH
Created22 November 2025measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/FBTYSAZMJH

Growth

7476757 August 2026 — 74 subscribers9 August 2026 — 74 subscribers16 August 2026 — 76 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net +2. 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 74–76 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 08:0976+2
9 Aug 2026, 21:4774no change
7 Aug 2026, 18:2174first reading

Engagement

9 posts held, back to 22 November 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
68.4%
avg views ÷ 76 subscribers
Avg views / post
52.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 9 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held9 (22 November 20253 August 2026)
Views total52
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 21:47 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.

Reaction mix

3 reactions across 2 posts, in 1 kind.

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

Measured over the 9 most recent posts we hold, published 22 November 2025 to 3 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.

Recent posts

3 Aug 2026, 17:15 UTC52 viewsread 9 August 2026

SDK ,DPI自有技术欢迎各位大佬洽谈, 诚招数据商代理,专出快递礼品女性数据 扶贫传销数据 百万数据 教育,理财,送礼品,微拉,空降,兼职(名字,年龄,地址,身份证,籍贯,洗实时微信 可带头像,支付宝等) 棋牌/BC/短信直播贷款/股民/群呼 手拨 短信料,学生单位要素/相亲/快杀 精聊料,,全球高资产数据 海外渗透,爬虫,撞库,内鬼,API接口采集 实时活跃料 可指定包库! 各类型tg ws line viber zalo 等皆可定制,适用各国高端项目,精聊,快杀,刷单,兼职,实时数据抓取/劫持/渗透 已上押公群 支持担保 客服: @svip020 频道: @svip_h

7 Jul 2026, 17:34 UTC85 views1 reactionsread 9 August 2026

🔥大众集团香烟🔥 硬中华🔥150/条,软中华🔥150/条 细金边中华🔥125/条,细雨花石🔥150/条 📣📣包回收/扣件包补💸💸 细金边中华🔥125/条 细雨花石🔥150/条 钻石荷花🔥165/条 软珍品楼🔥155/条 木盒硬粗和天下🔥240/条 1916硬红爆🔥295/条 1916软黄爆🔥295/条 木盒大重九🔥295/条 👍👍👍包回收/扣件包补👌👌👌 大众香烟客服:@Ly68666 双向机器人:@Dzxybybot

1

7 Jul 2026, 17:22 UTC69 viewsread 9 August 2026

🔥大众集团香烟🔥 硬中华🔥150/条 软中华🔥150/条 双开中🔥150/条 细金边中华🔥125/条 细雨花石🔥150/条 钻石荷花🔥165/条 软珍品楼🔥155/条 木盒硬粗和天下🔥240/条 1916硬红爆🔥295/条 1916软黄爆🔥295/条 木盒大重九🔥295/条 👍👍👍包回收/扣件包补👌👌👌 大众香烟客服:@Ly68666 双向机器人:@Dzxybybot

24 Nov 2025, 14:16 UTC≈1,180 views2 reactionsread 9 August 2026

🩷飞机广告全天代发🔥 可发任何文案 🩷飞机广告全天代发🔥 可发任何文案 🩷飞机广告全天代发🔥 可发任何文案 🔰外卖美食类🔰修车类🔰招聘类🔰BC类🔰换汇类🔰币圈项目类🔰色粉🔰兼职类🔰棋牌类🔰体育类🔰股票类🔰BC周边产业 👊五麟老牌代发 无视风控👍 👍诚信合作,真金不怕火炼!👊 🌈长期专注于飞机代发业务 人工筛选精准群组 ❤️客户可以随时更换广告内容和联系方式 出群发器,永久使用不限多开, 教代发技术无视风控🤝白嫖勿扰 频道 https://t.me/YSSKK9999 联系 @wl058 双向 @wl0588bot

2

Showing the 9 most recent of 9 posts we hold for @FBTYSAZMJH. 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

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

“搞钱项目 点这联系” (@FBTYSAZMJH), 76 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/FBTYSAZMJH.

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.