👇简体中文语言包👇 https://t.me/zh_cnaby

Channel
供求@cfdbgx「财阀担保」
@zvezdniynewbot
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
8subscribers
-1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003821167221 |
|---|---|
| Type | Channel |
| Username | @zvezdniynewbot |
| Description | 财阀集团官网: cfjt.xyz 24小时在线客服:@miili1111 |
| Created | 7 April 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/zvezdniynewbot |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:03 | 8 | no change |
| 9 Aug 2026, 18:42 | 8 | -1 |
| 9 Aug 2026, 12:32 | 9 | first reading |
Engagement
10 posts held, back to 7 April 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 1 pageof 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 10 posts for this entry, the most recent from 12 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 5
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.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 1 of the 10 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 7 April 2026 to 12 May 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
财阀科技群发引流源头价格⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 高质量 周套餐 U单位 🔆311/U-- -- 50个会员号 10000个精准群组 送 2000用户私信 🔆722/U-- -- 80个会员号 30000个精准群组 送3500用户私信 🔆1666/U-- -- 130个会员号50000个精准群组 送5000用户私信 🔆3140/U-- --150个会员号 包机 送10000用户私信 月套餐 RMB 单位 🔆888/U---- 100个会员号 30000个精准群组 送3000用户私信 🔆2444/U---- 200个会员号45000 个精准群组 送7000用户私信 🔆3666/U---- 300个会员号 60000 个精准群组 送9000用户私信 🔆4666/U---- 400个会员号 80000个精准群组 送11000用户私信 🔆8888/U-- --500个会员号 包机 送 17000用户私…
❤2
小额担保流程: 1.与担保方谈妥 2.给供需双方拉群沟通 4.对接好沟通 5.交押金到担保方 6.合作开始 7.合作结束,对接押金退还问题 押金种类: 目前押金的种类,只支持USDT 对接群介绍: 所有事情必须在我拉的群内沟通,私聊沟通的概不负责 赔付退还的机制: 如果双方合作过程中发生资金损失或者分歧,只接受双方一致认可的解决方案,才会执行,任何一方单方面说辞,是不会执行的。也就是退押金必须双方确认才可以退。供应方或者需求方失联,都是需要等7天的,也就是失联当天不算,等待后面7天,第8天动用押金退还或者赔付 押金明细状态名词解释: 1.有效: 代表双方或者服务供应方正在合作中 2.已清退: 代表双方的合作关系顺利终止,并且已经做好了各方面交接 3.已结账: 代表担保的业务已经办妥,资金已经结算给供应方 4.已赔付: 代表出事了,用押金赔付给需求方了 5.已终止: 代表仅仅是业务合作终止,并没有退回供应方的押金,是转移…
🤖群管机器人定制,800-3500RMB 永久使用,可用20个群 1、欢迎语(按钮) 2、关键字(删除、禁言、回复、踢人) 3、广告(按钮、支持单图、多图、广告置顶) 4、进群验证(自定义验证文字提示) 5、问候语(两个时间段) 6、垃圾消息处理(删除含链接、转发消息、超长消息、视频消息并禁言) 7、删除进退群消息 8、单独群广告(按钮、支持单图、多图、广告置顶) 9、单独群欢迎语(按钮) 10、群键盘按钮 11、私聊关键字按钮回复等 12、关键字处理编辑消息 13、定时开关群 14、统计当日进退群用户数据 15、转发特定用户消息 16、转发特定群消息 注:1-6点为基础配置 1-12为常规配置 13-16为补充配置 默认全开通为1-12点 图上全功能3500,需要个别的带功能问价 1个月 100u 3个月 200u 半年 350u 一年 4…
Photo, posted without a caption
财阀上压1000u https://t.me/qingtiantongxun
允儿共群上压5000u https://t.me/+XYEGNlDPkl82YjI8
供求@cfdbgx「财阀担保」 pinned «小额担保流程: 1.与担保方谈妥 2.给供需双方拉群沟通 4.对接好沟通 5.交押金到担保方 6.合作开始 7.合作结束,对接押金退还问题 押金种类: 目前押金的种类,只支持USDT 对接群介绍: 所有事情必须在我拉的群内沟通,私聊沟通的概不负责 赔付退还的机制: 如果双方合作过程中发生资金损失或者分歧,只接受双方一致认可的解决方案,才会执行,任何一方单方面说辞,是不会执行的。也就是退押金必须双方确认才可以退。供应方或者需求方失联,都是需要等7天的,也就是失联当天不算,等待后面7天,第8天动用押金退还或者赔付…»
小额担保流程: 1.与担保方谈妥 2.给供需双方拉群沟通 4.对接好沟通 5.交押金到担保方 6.合作开始 7.合作结束,对接押金退还问题 押金种类: 目前押金的种类,只支持USDT 对接群介绍: 所有事情必须在我拉的群内沟通,私聊沟通的概不负责 赔付退还的机制: 如果双方合作过程中发生资金损失或者分歧,只接受双方一致认可的解决方案,才会执行,任何一方单方面说辞,是不会执行的。也就是退押金必须双方确认才可以退。供应方或者需求方失联,都是需要等7天的,也就是失联当天不算,等待后面7天,第8天动用押金退还或者赔付 押金明细状态名词解释: 1.有效: 代表双方或者服务供应方正在合作中 2.已清退: 代表双方的合作关系顺利终止,并且已经做好了各方面交接 3.已结账: 代表担保的业务已经办妥,资金已经结算给供应方 4.已赔付: 代表出事了,用押金赔付给需求方了 5.已终止: 代表仅仅是业务合作终止,并没有退回供应方的押金,是转移…
Channel created
Showing the 10 most recent of 10 posts we hold for @zvezdniynewbot. 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 — 367,162 of 1,481,243entries 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.
Mentions
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“供求@cfdbgx「财阀担保」” (@zvezdniynewbot), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zvezdniynewbot.
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.