贷款渠道 青年 老年V3 常年售卖 95188问题直接包售后 别人家不敢包 我包 并承诺不会再有95188出现彻底研究明白了 收贷款渠道 青年 老年 V3 以及村推 价格直接一步到位名盘名码 440起收渠道 欢迎一手对接 @molong0976 @molong0971 接反扫 中断 人脸 短信 @GPFS001 @gangpao02
❤2👍1

Channel
@molong0976
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,330subscribers
+158 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002167841858 |
|---|---|
| Type | Channel |
| Username | @molong0976 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/molong0976 |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 72% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Oct 2026, 20:38 | 1,330 | +18 |
| 28 Oct 2026, 20:58 | 1,312 | +24 |
| 25 Oct 2026, 18:29 | 1,288 | +9 |
| 23 Oct 2026, 05:08 | 1,279 | -1 |
| 20 Oct 2026, 11:10 | 1,280 | +16 |
| 17 Oct 2026, 04:07 | 1,264 | +9 |
| 13 Oct 2026, 23:58 | 1,255 | +16 |
| 9 Oct 2026, 05:37 | 1,239 | +15 |
| 2 Oct 2026, 18:01 | 1,224 | +32 |
| 22 Aug 2026, 06:36 | 1,192 | +12 |
| 19 Aug 2026, 08:04 | 1,180 | +8 |
| 18 Aug 2026, 16:30 | 1,172 | first reading |
13 posts held, back to 25 July 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 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 13 posts for this entry, the most recent from 18 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
19 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 84.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 84.2% | |
| 👍 | 2 | 10.5% | |
| 🔥 | 1 | 5.26% |
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 7 of the 13 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 25 July 2026 to 18 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.
贷款渠道 青年 老年V3 常年售卖 95188问题直接包售后 别人家不敢包 我包 并承诺不会再有95188出现彻底研究明白了 收贷款渠道 青年 老年 V3 以及村推 价格直接一步到位名盘名码 440起收渠道 欢迎一手对接 @molong0976 @molong0971 接反扫 中断 人脸 短信 @GPFS001 @gangpao02
❤2👍1
全网寻找 村推能做老年V3 贷款渠道 青年 老年 V3 440收贷款渠道 手里有资源欢迎来合作 长年不停工 全年收货 欢迎各位老板来洽谈合作 全年运转不停工 @molong0971 @molong0976 🥰🥰🥰🥰 接团队反扫 中断 短信 人脸 资金安全有保障 @GPFS001 @gangpao02
95188 处理教程 以及还有另一种办法 那个办法是包上 @molong0976
贷款渠道 价格 大幅度下调 青年V3 老年V3 持续开工不停工状态 接团队 散户 及各大团队长 等等 需要的老板欢迎来洽谈合作 售后老样子不变 95188包处理 反扫持续开工 不停工 短信 中断 代还花呗 @gangpao02 @GPFS001
贷款渠道 青年 老年 V3 持续开工稳定输出 不快不慢不着急 需要的老板前来预定 无限接预定 另外接帮上95188保证百分百帮你吧号登录上去 需要的老板您喊我 @molong0976 @molong0971 持续接反扫 中断 短信验证 代还花呗 掉实名代还花呗 @gangpao02 @GPFS001
反扫正常开工接单 来团队 统一回92 长期对接团队 白天全天候在线 到晚上凌晨4点 魔龙全程担保资金问题 有任何资金问题方可找魔龙 中断 人脸 短信 皆可反扫 @GPFS001 @gangpao02 @molong0971
❤3
现在上号95188的较多魔龙这里带售后不会像别人家一样不带售后 以及帮助码商上号,以前打95188电话可以上 现在不行了 主动打电话 都变成手持驳回 口子半死半活 需要辅助上号的 喊我 前提是没有 上传过之后的
❤4
现在上号 95188 主动打电话 直接驳回 变成手持 号变成废品上不去 需要帮忙 上号的 可以联系我以前打电话那种方法已经不能行了变手持嗷嗷的 @molong0971
钢炮反扫 魔龙担保资金 回款无忧 秒回款 统一回款92 长期对接团队 额度大 每天无上限扫 资金问题魔龙全程担保无忧 @gangpao02 @GPFS001 @molong0971
❤2
很多人纠结下一个跑路的是不是你龙 放心吧你龙格局没有那么小 不至于跑 无论有没有货来货给 没货要退钱也是秒退 合作过的都知道我痛快不痛快 @molong0971 +888 0364 1279
❤3👍1🔥1
全行业寻找稳定渠道 青年 老年 V3 以及各种稳定渠道 价格置顶 常年不停工 极常年保bc 不拖拖拉拉 结账不墨迹 售后准时准点 寻求合作 🥰🥰🥰🥰 @molong0971 +888 0364 1279
承接团队反扫 回款快 姿势帅 费率置顶 可拉群 单独对接 需要的老板滴滴 @nc00000 @gangpao02
Showing the 12 most recent of 13 posts we hold for @molong0976. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by
Channels on the register whose posts name this channel's handle.
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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“教主V3/公司/业务频道(业务请私聊)” (@molong0976), 1,330 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/molong0976.
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.