Telegram RegisterThe public register of Telegram
Telegram profile photo for 小趴菜聚集地

Channel

小趴菜聚集地

@yhtjxyzz

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

6,250subscribers

-173 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-1002797412170
TypeChannel
Username@yhtjxyzz
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/yhtjxyzz

Topic

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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

6,2506,4236,336.57 August 2026 — 6,423 subscribers8 August 2026 — 6,419 subscribers11 August 2026 — 6,383 subscribers14 August 2026 — 6,352 subscribers17 August 2026 — 6,327 subscribers20 August 2026 — 6,310 subscribers24 August 2026 — 6,307 subscribers27 August 2026 — 6,361 subscribers30 August 2026 — 6,351 subscribers3 September 2026 — 6,337 subscribers8 September 2026 — 6,309 subscribers12 September 2026 — 6,276 subscribers15 September 2026 — 6,250 subscribers7 August 202615 September 2026
13 measurements spanning 39 days, net -173. 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 6,224–6,449 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:396,250-26
12 Sept 2026, 08:376,276-33
8 Sept 2026, 08:196,309-28
3 Sept 2026, 08:426,337-14
30 Aug 2026, 18:246,351-10
27 Aug 2026, 19:556,361+54
24 Aug 2026, 16:336,307-3
20 Aug 2026, 15:586,310-17
17 Aug 2026, 15:396,327-25
14 Aug 2026, 08:266,352-31
11 Aug 2026, 07:316,383-36
8 Aug 2026, 01:226,419-4
7 Aug 2026, 17:476,423first reading

Engagement

21 posts held, back to 28 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 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 21 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

129 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 77.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10077.5%
2821.7%
😁10.775%

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

Measured over the 21 most recent posts we hold, published 28 July 2026 to 8 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.

Recent posts

8 Aug 2026, 14:21 UTC579 views31 reactionsread 12 August 2026

有没有想玩8.8块钱萤火全家桶的 2内核1断点

👍283

3 Aug 2026, 08:36 UTC≈2,910 views10 reactionsread 12 August 2026

接内核定制 数据 接破解 拜师 @jiang_snnow888

👍64

3 Aug 2026, 07:47 UTC≈1,370 views11 reactionsread 12 August 2026
Photo

这个dv不老实 boot有问题

👍92

1 Aug 2026, 18:09 UTC≈1,290 views4 reactionsread 12 August 2026
Forwarded from @snnow_DriverFile

本驱动特点 ## 能力亮点 ### 进程感知 内置进程定位能力,可按包名检索目标进程,并将目标进程绑定到统一操作上下文中。上层业务无需反复处理 /proc 遍历、进程生命周期判断和 PID 维护逻辑。 ### 模块态势感知 支持目标进程模块基址查询,适合用于 native so 定位、运行时符号偏移换算、模块加载状态确认等场景。接口返回结果可直接作为上层地址推导的基础。 ### 内存诊断通道 提供多路径内存访问封装,支持自动选择更合适的读取方式,减少上层调用侧对底层细节的依赖。对接层暴露统一的 peek`、`poke`、`load`、`store 风格接口,方便构建调试器、观测器、状态采集器和自动化分析工具。 ### 调试辅助能力 保留运行时 trap、命中记录、寄存器快照、patch 辅助等调试相关能力,为复杂 native 行为分析提供更深入的观察点。适合用于定位关键路径、分析状态变化和构建内部调试流水线。

2👍2

1 Aug 2026, 17:38 UTC≈1,130 views1 reactionsread 12 August 2026

开发完成 总耗时7day左右 一直闷声干大事 所以没说 现在我都内核也写的答辩 感谢github开源的项目 拥有的功能 断点 隐藏一系列

👍1

1 Aug 2026, 15:48 UTC≈1,160 views3 reactionsread 12 August 2026

无痕内核驱动正在开发 欢迎对接 @snnow1314

👍3

1 Aug 2026, 15:27 UTC906 views2 reactionsread 12 August 2026
Forwarded from @XU509Photo

绝对是算法解密,不过目前解密后会闪框,不过是在真实坐标附近闪框,能看个大概位置 真正的算法解密内核,绝不动内存,稳定航天绝密乱杀需要注意,算法解密,不遁地,不漏人 📱APP启动器不依赖mt管理器 ✅物资显示 精确寻包 🔌网页雷达 全队共享 一天只要8.8 先到先得 赞助地址 https://911.222bx.cn/shop/D295GMN4

👍2

31 Jul 2026, 18:12 UTC≈1,200 views1 reactionsread 12 August 2026

Q 你到底什么时候才能收手 A 对不起我们每个人都要吃饭的 🎲🎲🎲

👍1

31 Jul 2026, 18:11 UTC≈1,210 views1 reactionsread 12 August 2026

秦琼卖马颜面抛,杨志也曾卖宝刀,曹操曾走华容道, 仲达搜 装病父子笑,英雄总有落难日,谁没低头弯过腰。

👍1

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

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

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.

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

“小趴菜聚集地” (@yhtjxyzz), 6,250 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/yhtjxyzz.

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.