项目名称:无限收贷款粉,无征信要求,只要是有贷款需求就可以来。 要求: 和客户说我们是银行贷款 金额1万以上,年纪20岁以上。 不杀鱼,不诈骗,不跑分洗钱 后端做手机卡 单价45 来一手上粉团队 联系人:@liuwei258 频道: 群组: ————————————————— 供需客服: @bansui0 ————————————————— 供需都是未经检验真假,可自行拉担保 —————————————————
Signed 往事随风

Channel
@bansui6
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
22,423subscribers
+1,176 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002677637289 |
|---|---|
| Type | Channel |
| Username | @bansui6 |
| Description | 供需信息8u 虚假广告10u 包月 包周 每日1发 打8/7折 2发6折 ————————————————————— 发布供需: @bansui1916 跑分交流群: @bansui88 赚钱项目跑分交流群: @bansui2 1916交流群:@gxgx1916 —————————————————————— ⚠️声明:本频道展示广告真假未经验证 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/bansui6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 19:15 | 22,423 | +19 |
| 28 Aug 2026, 20:17 | 22,404 | -43 |
| 27 Aug 2026, 20:02 | 22,447 | +128 |
| 26 Aug 2026, 18:16 | 22,319 | +159 |
| 25 Aug 2026, 17:43 | 22,160 | +15 |
| 24 Aug 2026, 19:56 | 22,145 | +69 |
| 23 Aug 2026, 06:06 | 22,076 | +95 |
| 21 Aug 2026, 14:36 | 21,981 | +126 |
| 20 Aug 2026, 13:03 | 21,855 | +135 |
| 19 Aug 2026, 13:35 | 21,720 | +34 |
| 18 Aug 2026, 12:16 | 21,686 | +86 |
| 17 Aug 2026, 13:04 | 21,600 | +111 |
| 16 Aug 2026, 06:38 | 21,489 | +30 |
| 14 Aug 2026, 20:08 | 21,459 | +15 |
| 13 Aug 2026, 07:47 | 21,444 | +135 |
| 12 Aug 2026, 10:47 | 21,309 | +62 |
| 11 Aug 2026, 20:01 | 21,247 | first reading |
24 posts held, back to 25 January 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 36 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. It is computed over the 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 24 (25 January 2026 – 28 August 2026) |
| Views total | 3,024 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 22:06 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 29 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.
Measured directly from 3 videos 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.
22 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 77.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 77.3% | |
| 🔥 | 4 | 18.2% | |
| 🥰 | 1 | 4.55% |
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 16 of the 24 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 22reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 25 January 2026 to 28 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.
项目名称:无限收贷款粉,无征信要求,只要是有贷款需求就可以来。 要求: 和客户说我们是银行贷款 金额1万以上,年纪20岁以上。 不杀鱼,不诈骗,不跑分洗钱 后端做手机卡 单价45 来一手上粉团队 联系人:@liuwei258 频道: 群组: ————————————————— 供需客服: @bansui0 ————————————————— 供需都是未经检验真假,可自行拉担保 —————————————————
Signed 往事随风
淘宝im推毒 指定话术+推文件给商家 毒包显示已读 截图和商家的聊天记录给客服交单 必须回复商家消息,严格按照要求做 0.4-1元一单 做完单截图二张图,一张和商家的聊天记录拉到最上面看到第一次打招呼的时间,第二张截图到文件的聊天记录,截图不带文件撤回的不结账,重复交单不结账,重复推不结账,文件未读不算单,必须当天找的商家才可以,不可以提前找商家 100以下0.4 100以上0.5 300单0.6 500以上1 认准: @xqlw9 做单群: https://t.me/xuqintabao ————————————————— 供需客服: @bansui0 ————————————————— 供需都是未经检验真假,可自行拉担保 —————————————————
❤1
Signed 往事随风
☎️ 实卡接码 🙎♂️代实名🙍♀️过人脸 💸微信支付宝代充代付,🅾️国际阿里云腾讯云等各种云服务器🅾️站群物理服务器✈️代开国际信用卡,paypal,信用卡代付 ✈️代开飞机大会员💻代办定制公司执照,可盖章打印代签字 联系飞机号: @wwcom
Signed 往事随风
☎️ 实卡接码 🙎♂️代实名🙍♀️过人脸 💸微信支付宝代充代付,🅾️国际阿里云腾讯云等各种云服务器🅾️站群物理服务器✈️代开国际信用卡,paypal,信用卡代付 ✈️代开飞机大会员💻代办定制公司执照,可盖章打印代签字 联系飞机号: @wegzs
Signed 往事随风
☎️ 实卡接码 🙎♂️代实名🙍♀️过人脸 💸微信支付宝代充代付,🅾️国际阿里云腾讯云等各种云服务器🅾️站群物理服务器✈️代开国际信用卡,paypal,信用卡代付 ✈️代开飞机大会员💻代办定制公司执照,可盖章打印代签字 联系飞机号: @wegzs
Signed 往事随风
经营能量无视单笔三万内 银联在开 牛户在开找料常规大混都来欢迎实力料主水房 需要联系 @ryyy54
Signed 往事随风
本供需频道限时5u一条 10u三条 关联三个交流群群组 全部为真实浏览! 限时三天 三天后恢复10u一条 供需发布联系 @bansui0
Signed 往事随风
😃😃有抖音的看过来,日入5000+ 🪺🪺🪺最新抖音代刷礼物最稳定项目 0风险 日入5000+简简单单 项目介绍:色料抖币充值📱 ✔️我这边用色料给你的抖音帐号充值钻石 你去我指定的直播间刷出来就可以 🟠利润:刷完一组工资500人民币(几分钟就可以刷完一组)一组一结帐 🤪🤨🧐🤓 🥸🤩😎😝 🐹结账支持:微信📱支付宝📖U📔 ⚠️新人第一次做单奖励188-2000元红包 九万支付上押公群:https://t.me/+xjsHbwMVfZlmMzY9 📱【点击进入九万支付赚钱项目群】 😐😑😬😲🆗🫠🫠🫠🫠😈 —————————————————————— ⚡️⚡️⚡️⚡️最新项目!碾压全网!安全无风险项目! 🇱🇾支付宝/微信/QQ/银行卡/代收 💠万福集团10万人做单群点击进入 🥸🤩😅😂🤣 😊😇😌🧐🤓 💠飞机最稳项目!日工资保底2000+ 无风险!无风险!无风险!重要的事情说三遍!⭐️利润: 拿你的(支付宝微信QQ)收款码…
🔥1
Signed 往事随风
😃😃有抖音的看过来,日入5000+ 🪺🪺🪺最新抖音代刷礼物最稳定项目 0风险 日入5000+简简单单 项目介绍:色料抖币充值📱 ✔️我这边用色料给你的抖音帐号充值钻石 你去我指定的直播间刷出来就可以 🟠利润:刷完一组工资500人民币(几分钟就可以刷完一组)一组一结帐 🤪🤨🧐🤓 🥸🤩😎😝 🐹结账支持:微信📱支付宝📖U📔 ⚠️新人第一次做单奖励188-2000元红包 九万支付上押公群:https://t.me/+xjsHbwMVfZlmMzY9 📱【点击进入九万支付赚钱项目群】 😐😑😬😲🆗🫠🫠🫠🫠😈 —————————————————————— ⚡️⚡️⚡️⚡️最新项目!碾压全网!安全无风险项目! 🇱🇾支付宝/微信/QQ/银行卡/代收 💠万福集团10万人做单群点击进入 🥸🤩😅😂🤣 😊😇😌🧐🤓 💠飞机最稳项目!日工资保底2000+ 无风险!无风险!无风险!重要的事情说三遍!⭐️利润: 拿你的(支付宝微信QQ)收款码…
❤1🔥1
Signed 往事随风
😃😃有抖音的看过来,日入5000+ 🪺🪺🪺最新抖音代刷礼物最稳定项目 0风险 日入5000+简简单单 项目介绍:色料抖币充值📱 ✔️我这边用色料给你的抖音帐号充值钻石 你去我指定的直播间刷出来就可以 🟠利润:刷完一组工资500人民币(几分钟就可以刷完一组)一组一结帐 🤪🤨🧐🤓 🥸🤩😎😝 🐹结账支持:微信📱支付宝📖U📔 ⚠️新人第一次做单奖励188-2000元红包 九万支付上押公群:https://t.me/+xjsHbwMVfZlmMzY9 📱【点击进入九万支付赚钱项目群】 😐😑😬😲🆗🫠🫠🫠🫠😈 —————————————————————— ⚡️⚡️⚡️⚡️最新项目!碾压全网!安全无风险项目! 🇱🇾支付宝/微信/QQ/银行卡/代收 💠万福集团10万人做单群点击进入 🥸🤩😅😂🤣 😊😇😌🧐🤓 💠飞机最稳项目!日工资保底2000+ 无风险!无风险!无风险!重要的事情说三遍!⭐️利润: 拿你的(支付宝微信QQ)收款码…
🔥1
Signed 往事随风
1916供需 ————————————————— 项目名称:微信户 没做过的来 200秒 联系人:@jiuchengyixi00 频道/群组: ————————————————— 供需都是未经检验真假,可自行拉担保 ————————————————
Signed 往事随风
本供需频道限时5u一条 10u三条 关联三个交流群群组 全部为真实浏览! 7月1号恢复10u一条 供需发布联系 @bansui0
❤1
Signed 往事随风
Showing the 12 most recent of 24 posts we hold for @bansui6. 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,364,485 of 1,626,884entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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.
“1916灰产赚钱资源(10u三条真人流量)” (@bansui6), 22,423 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/bansui6.
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.