林盟主📱信誉频道 认准@NBlxj pinned a photo

Channel
林盟主📱信誉频道 认准@NBlxj
@xyxyxinyu
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
5,687subscribers
-612 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001803550818 |
|---|---|
| Type | Channel |
| Username | @xyxyxinyu |
| Created | Between 1 September 2022 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/xyxyxinyu |
Topic
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 23:59 | 5,687 | -58 |
| 13 Sept 2026, 11:21 | 5,745 | -86 |
| 9 Sept 2026, 08:42 | 5,831 | -98 |
| 3 Sept 2026, 20:20 | 5,929 | -28 |
| 31 Aug 2026, 13:27 | 5,957 | -37 |
| 28 Aug 2026, 23:43 | 5,994 | -54 |
| 26 Aug 2026, 06:13 | 6,048 | -37 |
| 23 Aug 2026, 05:25 | 6,085 | -32 |
| 19 Aug 2026, 09:35 | 6,117 | -88 |
| 16 Aug 2026, 20:16 | 6,205 | -23 |
| 12 Aug 2026, 23:12 | 6,228 | -64 |
| 10 Aug 2026, 06:13 | 6,292 | -12 |
| 7 Aug 2026, 13:47 | 6,304 | +5 |
| 7 Aug 2026, 04:32 | 6,299 | first reading |
Engagement
22 posts held, back to 6 August 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 9 pages 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 22 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
8.11部分手机口结账聊天记录 点击蓝色字体跳转 😘林盟主手机口320u有预付课结 😄手机口做单教程视频😄 😄手机口价格福利待遇😄 上口客服 @puawc 😘林盟主集团抖音代刷 😄抖音代刷项目介绍😄 😄抖音代刷常见问题解答😄 抖音代刷客服 @puawq 😄林盟主24小时不禁言红包群 😄林盟主集团官方频道
Signed 希希 客服(发资料秒上)
林盟主📱信誉频道 认准@NBlxj pinned a photo
8.11部分抖音代刷结账聊天记录
Signed 安妮(抖音代刷客服)
林盟主📱信誉频道 认准@NBlxj pinned a photo
8.9部分手机口结账聊天记录 点击蓝色字体跳转 😘林盟主手机口320u有预付课结 😄手机口做单教程视频😄 😄手机口价格福利待遇😄 上口客服 @puawc 😘林盟主集团抖音代刷 😄抖音代刷项目介绍😄 😄抖音代刷常见问题解答😄 抖音代刷客服 @puawq 😄林盟主24小时不禁言红包群 😄林盟主集团官方频道
Signed 希希 客服(发资料秒上)
林盟主📱信誉频道 认准@NBlxj pinned a photo
8.9部分抖音代刷结账聊天记录
Signed 安妮(抖音代刷客服)
林盟主📱信誉频道 认准@NBlxj pinned a photo
8.8部分手机口结账聊天记录 点击蓝色字体跳转 😘林盟主手机口320u有预付课结 😄手机口做单教程视频😄 😄手机口价格福利待遇😄 上口客服 @puawc 😘林盟主集团抖音代刷 😄抖音代刷项目介绍😄 😄抖音代刷常见问题解答😄 抖音代刷客服 @puawq 😄林盟主24小时不禁言红包群 😄林盟主集团官方频道
Signed 希希 客服(发资料秒上)
林盟主📱信誉频道 认准@NBlxj pinned a photo
8.8部分抖音代刷结账聊天记录
Signed 安妮(抖音代刷客服)
Showing the 12 most recent of 22 posts we hold for @xyxyxinyu. 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
Named by 18 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.
@sebi · 67,13019 postsYY担保灰产项目供需·限时10U(赚钱资源) @yyyy7
@yyyy7 · 27,41319 posts🥈柬埔寨供需50U限时10u双频道 @DAVA
@huyagg · 14,52113 posts林盟主集团官方频道 认准@puawc
@laomo2 · 3,7002 posts博无忧-☀️全平台爆料
@ahqptbl · 31 post迪行者:权威曝光
@bbb677 · 2381 post博涯-✨曝光爆料平台
@bgblpt · 3311 post菲柬迪-曝光-迪拜
@bvtyuj · 1191 post博资传媒-📹全平台曝光
@bzcm004 · 811 post蝌蚪频道-点亮曝光
@dds2288 · 2471 post全球安危曝光
@fhjdbjj · 401 post曝光骗子 / 渠道骗子 / 反诈先锋
@FZXF1_1 · 13,9571 post百集 全网曝光
@qili903 · 1111 post博音-🗣华人爆料
@qnsbgbl · 31 post博中-柬埔寨华人爆料
@shjtjpzbl · 511 post兔兔-曝光爆料
@tyyyyuoq · 101 post火狼 曝光爆料
@vkolbvfr · 1191 postJY 進源实物盘
@yeye · 6,5891 post
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“林盟主📱信誉频道 认准@NBlxj” (@xyxyxinyu), 5,687 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/xyxyxinyu.
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.