Channel
@XINBlKEFU
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
227,565subscribers
+6,728 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001263654599 |
|---|---|
| Type | Channel |
| Username | @XINBlKEFU |
| Description | 公群导航 @xbqqg 备用 @xbgq 供需频道 @xbrgx 备用 @xbbh 官方大群 @xbbda 备用 @xbqn 新开公群 @xbxkq 骗子曝光 @xbfpx 公告频道 @XINBlKEFU 买会员/买广告/发供需 联系人工客服 @xbkkf |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/XINBlKEFU |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 14 August 2026 and assigned it the closest of 31 fixed categories, at 40% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 12:47 | 227,565 | +7,246 |
| 16 Aug 2026, 05:05 | 220,319 | -518 |
| 14 Aug 2026, 19:16 | 220,837 | first reading |
14 posts held, back to 16 January 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 21 July 2026 |
|---|---|
| Posts held | 14 (16 January 2026 – 21 July 2026) |
| Views total | 23,100 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Aug 2026, 21:43 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.
Lifetime counters from Telegram’s own channel header, read 17 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.
对于拿现类业务提醒： 1、中介或车队验资需方地址是否新地址、流水是否符合盘口特征。 2、需方是否有在合作成功等先例。 3、尽量避免使用非官方机器人。尽量避免新盘口新中介大额合作。 盘口新号新地址，一切不合理的事都有合理的解释。 ⚠️重要提醒：担保支持过保3小时以后再下发，避免出现下发后跟踪抢劫之类的问题发生。交易完三个小时候后，无纠纷下发后不支持追溯。（此举与原保时规则并不冲突，纯粹用于预留安全时间。凡无视风控、强行要求立即下发而导致遭遇抢劫的，一切损失由行为人自行承担。）
关于重申新币担保业务底线的严正声明 新币担保核心业务是数字资产交易提供第三方担保服务。自成立以来，我司始终坚守业务底线，坚决不承接、不支持、不参与任何形式的军火、毒品、绑架、人口贩卖、恐怖融资。 平台设有巡查组，对所有群行为进行持续监测。任何试图利用本平台从事以上红线行为的用户，一经查实，我司将依法依规采取没收押金、永久拉黑，绝不姑息。望广大客户互相转告，知悉！ —— 新币管理团队
新币担保重要公告： 为防范区块交易量过载，地址风控风险，后续将每月更换。新币担保将于月度4月12日00:00分进行担保上押地址更换。老上押地址继续保留两个月，不用于新群上押，唯一上押地址正式更换为： TRC20: TTyc —— Q3757J —— jNZ92v 请各位用户认准以上地址格式（请核对首、中、尾三段） 望往所有新币担保用户知悉，惠存。任何疑问直接垂询 24小时客服 @xbkf 2026年4月1日
新币担保重要公告： 为防范区块交易量过载，地址风控风险，后续将每月更换。新币担保将于月度2月2日00:00分进行担保上押地址更换。老上押地址继续保留两个月，不用于新群上押，唯一上押地址正式更换为： TRC20: TTgSvGT4ncQje6pLvCaMKGiCnVZZcVhj61 ERC20: 0x4FbF87f9FcE0ff225bc278916f7De3348Af79dB2 望往所有新币担保用户知悉，惠存。任何疑问直接垂询 24小时客服 @xbkf 2026年2月1日
公群提醒： 1、注意！近期正对于新开群有多起骗子假担保利用个人简介冒充担保用户名，私聊客户发真地址收取结算费用/广告费 拉假群给真地址的套路频发之类等，在到专群联系真担保认领押金上押虚假交易下发押金， 老板们注意不要只看地址 担保号核对方式。——新币交易拼音首字111至999—— 备注好我们担保号新币官方唯一上押地址 小心被骗!我们地址是唯一的，有变动会提前发公告！其它任何地址都不要相信！请注意担保不会私聊客户索取任何费用。 2、谁上的押金备注谁是负责人，群名和负责人名称要一致，非必要情况不要修改群名和用户名，如需修改通知担保要同步修改群名和负责人的用户名，防止骗子利用相同的名字来办理业务！ 3、公群业务内容只允许对接本群的业务，不能同时做多个业务。 严禁私自添加业务， 如发现私自添加做别的业务最低罚款1000U起。 4、新开公群，开群后免费上公群导航 @xbqqg （月收类开群计费：公群退押100U起扣，超过100…
⚠️票务公群温馨提示： 1、公群业务内容只允许对接本群的业务，不能同时做多个业务。 （如:群内有做多个项目➕一个业务➕200u担保费。） 2、本群业务禁止单笔金额超过5000¥，只能用于帮客戸支付仁投报销费用，禁止掺杂其他业务。违者首次警告，再次将进行最低1000U的罚款。 3、票务公群禁止赊账给其它公群，如赊账、预付、空放公群出现纠纷概不处理！新币不担保个人信誉。 4、禁止利用公群押金让其他人帮本群做代付业务，除本群业务之外其余一切业务，请去拉新币专群上押交易，违者最低1000u起罚款，情节严重的 公群押金全部没收。 担保方提醒：交易请认准群内供方头衔，转账认准群内供方地址，转账后便发详情图到群里对接 留有作业记录，不可私下交易，私下交易出现纠纷担保不予处理！不担保个人信誉。不报备造成损失不予受理，如公群方引导私下交易，一经核实，罚款处理。
报备的重要性 ⚠️先报备再交易，无报备属于私下作业！ ⚠️私下作业不在担保范围内，出现纠纷不予处理！ 对服务方而言： “报备”是您劳动被官方系统承认的唯一方式。它意味着任务需求、价格、周期等关键信息已在群内存档，是您后续回款、申请权益的合法凭证。 对需求方而言： “报备”是您获得官方担保和售后服务的“入场券”。它确保了您的需求被正式承接，后续的任何质量、进度问题都有了追索依据。 此条款将不可控的、口头的“私下约定”，转化为可控的、有记录的“官方报备”。它是整个风控体系的第一道，也是最重要的一道防火墙。 由于缺乏报备记录，平台方无法核实交易的真实性、具体条款以及责任归属，失去了作为公正第三方进行裁决的基础。 私下交易脱离了监管体系，可能伴随欺诈、质量低下、恶意违约等高风险行为。无报备不在担保范围内，旨在隔离此类风险，避免其污染整个平台生态，保护大多数合规用户的体验。 通过这些规则，服务提供方能更安心地提供服务，需…
常规业务报备流程： 群老板以及在本群交易的客户请注意看本条担保规则 ①报备流程 - 双方先谈好交易规则 - 确认规则没有问题 - 由群供方管理提交报备-交易方群内确认报备信息-在由担保审核报备信息— 担保确认报备成功后，担保生效方可进行作业，未完成的交易报备请勿点击交易完成，点击确认完成的，之后出现纠纷的后果自负，超出报备有效期还在作业的/或者还在交易中误点击到完成交易的，请联系群供方管理重新报备。 ②群供方管理禁止引导客户私下交易 或是有意不给客户先进行报备的 此行为被举报一次 最低1000u起罚款 情节严重公群押金直接全部没收，有发生以上违规行为，交易方可以直接联系担保 举报核实处理！ 担保方提醒： 交易之前先看下群内供方置顶规则 作业认准群内供方管理头衔人员 作业无报备 交易没有保障 交易都是需要先报备 报备成功后在交易的，请各位老板严格按担保规则交易！ ③每一笔交易要采取报备，不报备不在担保范围内，如有引…
公群国内跑分： ①、贴卡业务规则 例如： 巫** 云南省农村信用社 6231**********3233 红塔农村商业银行红塔支行凤凰分理部 附言：** 老板 您们交易按此模版贴卡，这样才有可查询记录，如遇纠纷问题才便核实，禁止贴空卡 违者罚款处理，望各位老板配合！ 注意：所有交易在群内进行，交易应展示：喊卡、贴卡、到账加账、下发减账记录，涉及隐私部分群内可用***代替或适当打码，然后再私聊贴完整的卡号信息，不在群内发生的交易属于私下交易，不在担保范围内！ ②、国内跑分类担保佣金统一按月结400U。如查实群方引导私下交易，引导不报备，给予举报人奖励：罚款群方金额的10%-50%奖励！核实举报： @xbkf
跑分/白资类公群： 公群最低15000u起押/收u业务最低上押金20000U起，实际作业15000U 诚信金5000u 防跑路押金 注意：所有交易在群内进行，交易应展示：喊卡、贴卡、到账加账、下发减账记录，涉及隐私部分群内可用***代替或适当打码，然后再私聊贴完整的卡号信息，不在群内发生的交易属于私下交易，不在担保范围内！ 担保佣金抽取： （跑分/白资/承兑公群月结400U）。如查实群方引导客户私下交易，引导不报备，给予举报人奖励：罚款群方金额的10%-50%奖励！核实举报： @xbkf 温馨提示：押金多少，入款就多少，千万别打超。超额后发生纠纷需自行承担。 本群计算器记账类的 一律都要记账 故意不加账者担保费翻倍! ⚠️注意:>>>>结算费用地址： TT66hhnGtCietkCNd4izkuUEiRFmSygqLD 跑分类公群作业规范要求： 近期跑分类公群纠纷频发，现对所有跑分类公群作业规范要求：每笔作业…
固定类跑分类通知： 白资、一道、二道、承兑、等走量类公群 大公群30000U起，人头大公群30000U起，由群老板决定要不要审核链接。老的公群不受影响（注：首开公群免费扶持：一条,公群导航 @xbqqg 发布一条） 跑分类公群门槛最低15000u起。人头小公群15000U起，由群老板决定要不要审核链接。老的公群不受影响。U换白资公群 (无纠纷后-15天后才给退押）（注：首开公群免费扶持：供方频道或需方频道 每日新开公群发布条,公群导航 @xbqqg 发布一条） 一二道先u后资公群公群最低上押20000u起（实际作业金额15000U+5000U诚信金） 注意：带审核链接的公群：加一个经常在线审核进群的管理用户名，并写一份您群所做业务的群简介，格式要求：简短简洁、一目了然，请编辑好群简介找担保修改。 注意：带有审核链接的公群老板可以附加一位审核人用户名，但此用户名如做更换一定要找担保报备修改公群频道 @xbqqg …
卡商公群交易注意事项 1、进群后请先确认是否为新币官方公群，进群之后联系担保本群靓号：@xbjy111-999 新币交易拼音首字111-999 进行验证！ 2、验证真群后首先要确认群内管理员身份，认准公群老板以及业务员，并了解群公交易规则后，再进行交易。 人头卡商中介群公告 1、中介上人前必须在公群里@担保号进行交易报备。没有报备私自交易的，如遇纠纷不予处理。 2、所有公群交易和沟通必须在群内进行，不允许诱导客户私下交易或者拖延不报备，公群如诱导客户私下交易不报备，发现一次最低罚款1000U，下次翻倍处罚。 3、所有交易必须找公群负责人或者业务员报备说明情况得到担保号 确认才可以进行交易，否则交易无效，卡主失联和车队被抓这类行业风险都找担保协商处理。 4、请各位保存好，有关结算账户或重要消息请提前录好视频，视频中体现对方的飞机账户用户名以免以后出现纠纷不认。 5、公群报备存在撬客户问题，报备提交后中介用户名机器人会…
Showing the 12 most recent of 14 posts we hold for @XINBlKEFU. 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 — 1,137,373 of 1,481,306entries 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.
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.
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.
@XINBlKEFU named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“新币官方公示” (@XINBlKEFU), 227,565 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/XINBlKEFU.
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.