1楼:兄弟们,来看科幻片吧。 2楼:不信谣,不传谣。 3楼:何方道友,在此布置的幻境。 编者:吾甚贱,阅全篇。
👍10🤬4🥰2❤1👎1

Channel
@nanxu01
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
125subscribers
+22 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001579912383 |
|---|---|
| Type | Channel |
| Username | @nanxu01 |
| Created | Between 1 August 2021 and 15 September 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/nanxu01 |
Other / unclassifiable — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 |
|---|---|---|
| 3 Oct 2026, 11:56 | 125 | +13 |
| 18 Sept 2026, 14:40 | 112 | +2 |
| 1 Sept 2026, 14:25 | 110 | -3 |
| 25 Aug 2026, 20:05 | 113 | +7 |
| 18 Aug 2026, 12:37 | 106 | +3 |
| 11 Aug 2026, 16:00 | 103 | no change |
| 11 Aug 2026, 15:48 | 103 | first reading |
15 posts held, back to 15 September 2022 — 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 15 posts for this entry, the most recent from 10 October 2022. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
108 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 71.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 77 | 71.3% | |
| 👎 | 10 | 9.26% | |
| 👏 | 6 | 5.56% | |
| 🤬 | 4 | 3.70% | |
| 🥰 | 4 | 3.70% | |
| ❤ | 2 | 1.85% | |
| 🔥 | 2 | 1.85% | |
| 🤔 | 2 | 1.85% | |
| 😁 | 1 | 0.926% |
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 13 of the 15 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 108 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 15 September 2022 to 10 October 2022, 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楼:兄弟们,来看科幻片吧。 2楼:不信谣,不传谣。 3楼:何方道友,在此布置的幻境。 编者:吾甚贱,阅全篇。
👍10🤬4🥰2❤1👎1
Video, posted without a caption
👍5👎1
还有那些新手小白,群里24小时循环导航就是不看,置顶不看,该说的我都说了就是尼玛不看,天天让我为最低级的骗术一而再再而三给你们上课,活该被骗!
👍12
Photo, posted without a caption
Video, posted without a caption
项目名称:固话 项目介绍:办理固话线,一台一天九小时1500,两台3000以此类推。看地区可涨,操作好后放置不用打理一天稳入账,支持担保。结账只USDT。 联系人: @telangpu2 【累计发布广告2次】 ▫️ ▫️ ▫️ ▫️ 发布联系 @nanxu5bot ───────────────
❤1👍1
Telegram五大用户体系,你是哪个? 1:纯小白用户:不懂模仿者以为这里到处都是赚大钱的东西,一点防范意识都没有。 2:乞丐帮:到处要钱! 3:混日子群众:担保没拉过,业务没做过到处坑蒙拐骗!赚生活费! 4:装大逼用户:到处抹黑跟预言家,说这个跑路那个跑路,结果自己反而是骗子。 5:王者玩家:业务广,到哪都受欢迎,不坑蒙拐骗,实打实做业务,秒担保。
👍1
项目名称:固话 项目介绍:办理固话线,一台一天九小时1500,两台3000以此类推。看地区可涨,操作好后放置不用打理一天稳入账,支持担保。结账只USDT。 联系人: @telangpu2 ▫️ ▫️ ▫️ ▫️ 发布联系 @nanxu5bot ───────────────
项目名称:免验证25-29 项目介绍:洗过的带id~免数据费,找我直接拉担保上量 最后收波人 位置不多了 想做的抓紧了 来找我的,必须拉担保 联系人: @Achun916 ▫️ ▫️ ▫️ ▫️ 发布联系 @nanxu5bot ───────────────
👍3
项目名称:空白日结zm 项目介绍:3月账单,30+好友,无限制,3半6全(50个里49个全),晚上挂设备晚上10点结账 隔天挂 续租高!!! 价格:220-250量大找群主谈价格 上号联系群管理,脾气好上号快,不喷不骂,上号多的有奖励,结账群里每天都有福利! 联系人:@qwerr112688 不上的进来聊聊天做个朋友观察也行。 ▫️ ▫️ ▫️ ▫️ 发布联系 @nanxu5bot ───────────────
👍4
Posted without readable text
👍13👎2🤔2
Posted without readable text
👍1
Showing the 12 most recent of 15 posts we hold for @nanxu01. 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.
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.
@nanxu01 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“【鹿头担保】供需20U一条联系机器人客服发布” (@nanxu01), 125 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/nanxu01.
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.