Telegram RegisterThe public register of Telegram
Telegram profile photo for 梦游配置文件

Channel

梦游配置文件

@mengyounb12

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

465subscribers

+88 since we began measuring on 29 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004481781771
TypeChannel
Username@mengyounb12
CreatedBetween 1 June 2026 and 19 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live25 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/mengyounb12

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

37746542129 August 2026 — 377 subscribers29 August 2026 — 377 subscribers29 August 2026 — 378 subscribers6 September 2026 — 437 subscribers13 September 2026 — 448 subscribers25 September 2026 — 465 subscribers29 August 202625 September 2026
6 measurements spanning 27 days, net +88. 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 364–478 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 23:18465+17
13 Sept 2026, 18:00448+11
6 Sept 2026, 05:40437+59
29 Aug 2026, 23:04378+1
29 Aug 2026, 20:30377no change
29 Aug 2026, 20:15377first reading

Engagement

13 posts held, back to 19 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
78.9%
avg views ÷ 465 subscribers
Avg views / post
367
7 posts measured
Reaction rate
1.13%
reactions ÷ views · ER floor
Posts in window
7
of 13 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 29 August 2026
Posts held13 (19 August 2026 – 29 August 2026)
Views total2,568
Reactions total29
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 20:30 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
9s
Average length
9s

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

54 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 74.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4074.1%
❤814.8%
👏23.70%
😍23.70%
🤡23.70%

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 12 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 54 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 19 August 2026 to 29 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

29 Aug 2026, 15:22 UTC51 views2 reactionsread 29 August 2026
Forwarded from @jyyydsnb66File

File, posted without a caption

🤡2

28 Aug 2026, 04:06 UTC960 views10 reactionsread 29 August 2026
File

梦游鬼帝v5 作者 梦游 c语言范围自瞄 cfg ini强化枪械 动态范围0.5 爆头率增强60% 头部吸附 算法识别对方血量低/离自己近处敌人触发自瞄Ai爆头算法(巅峰时期付费思路) ini0.2实体范围 ini范围子追 弹道聚集 辅助瞄准触发围 配置ini软锁自瞄 ​json人物追踪 date范围 发布频道 @mengyounb12

👍9❤1

23 Aug 2026, 12:53 UTC410 views5 reactionsread 29 August 2026

梦游迷斯拉 全软件加密防止泛滥 作者 梦游 金鱼 ✅连续吸附 ✅优化增幅 ✅爆头率增加 ✅减少准心扩散 ✅腰射准心吸附 ✅sav动态超大范围 ✅超远辅助瞄准增强 ✅概率子弹追踪 ✅概率追踪子弹延迟 ✅修复减伤范围增伤80% ✅子弹扩散减少 ✅人物模型范围扩大 ✅头部0.45范围 ✅人物四肢范围扩大 ✅子弹追踪 ✅辅助掩体判断 ✅掩体判断 ✅模型判断 ☑️全枪械防抖动/防抖 ☑️全枪械自瞄70° ☑️全枪械1.2倍子弹射速 ☑️爆头率极高 ✅ini身位范围 Max ✅强拉辅助瞄准 近/中✅腰射散步大幅度下降 ✅减少枪械后坐力 ✅AI智能动态瞄准 ✅仿内核自瞄 ✅腰射80%概率子追 ✅坐标自瞄 ✅子弹强行吸附 下载链接 https://new.818fka.com/shop/T8YPS4TY

👍5

22 Aug 2026, 03:40 UTC986 views9 reactionsread 29 August 2026
File

效果为行业顶尖 玩过以前版本的都知道效果有多厉害 包含配置文件所有效果 发布频道 @mengyounb12

👍9

20 Aug 2026, 04:28 UTC723 views5 reactionsread 29 August 2026
Poll

下个文件是付费还是公益

  1. 付费13%
  2. 公益87%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

❤5

20 Aug 2026, 01:18 UTC≈1,070 views2 reactionsread 29 August 2026
File

梦游鬼帝v3 作者 梦游 粘性自瞄 烟雾自瞄 敌人在烟雾中可以触发自瞄 射击优先射击头部 连续射击躯干部触发爆头(80%概率) 子追 弹道聚集 玩冲锋枪可以瞬秒敌人 此版本爆头率大大提升😍😍 更新内容 kt自瞄 范围 子追 json枪械增强爆头 c语言范围 减少后坐力 动态自瞄 ini坐标自瞄和枪械增强 发布频道 @mengyounb12

👏2

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

20 Aug 2026, 04:28 UTCAnonymous Poll195 voters

下个文件是付费还是公益

  1. 付费13%
  2. 公益87%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 13 most recent posts we hold, published 19 August 2026 to 29 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“梦游配置文件” (@mengyounb12), 465 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/mengyounb12.

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.