✅社团名:#BBQ大好き ▫️名称:除灵猎人:第零羔羊 ▫️原名:Nebel Geisterjäger ~ 零号羔羊 ▫️版本:v2.15(STEAM版) ▫️贩卖日:2023 年 12 月 22 日 ▫️标签:#爆款 #精品 #RPG #安卓直装 #PC #无码 #赠品 #CV #NTR #制服 #调教 #恶堕 #巨乳 #亲热 🟢链接:➡️入正地址 ➡️ 下载地址 概要: 本作是男主视角的隐奸特化NTR游戏。 不同于直接从女主视角讲述NTR过程,玩家需要通过如心跳检测、电话联系、监控摄像头、询问路人等各种手段来获取情报,从上司的魔爪中保护女友。 动态生成女主与上司的行为逻辑,真正实现与无良上司的实时博弈。 偷窥、推特、AV、梦境、多视角呈现游戏中的事件,事件本身也会根据攻略进度衍生出大量差分。 纯爱可能!只要没有被完全NTR,便仍有挽回的机会,甚至还会根据玩家设定的下体大小产生截然不同的反馈。 共有5个结局,支…

Channel
Galgamex 游戏 | 黄油频道
@Gamex666
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,649subscribers
+406 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 | -1002881526388 |
|---|---|
| Type | Channel |
| Username | @Gamex666 |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Gamex666 |
Topic
Gaming — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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, 04:59 | 1,649 | +82 |
| 13 Sept 2026, 15:19 | 1,567 | +107 |
| 9 Sept 2026, 16:15 | 1,460 | +87 |
| 7 Sept 2026, 00:22 | 1,373 | no change |
| 4 Sept 2026, 15:20 | 1,373 | +79 |
| 1 Sept 2026, 07:27 | 1,294 | +39 |
| 29 Aug 2026, 13:17 | 1,255 | +5 |
| 26 Aug 2026, 14:22 | 1,250 | +2 |
| 23 Aug 2026, 22:05 | 1,248 | +2 |
| 20 Aug 2026, 10:16 | 1,246 | +2 |
| 17 Aug 2026, 19:57 | 1,244 | +4 |
| 14 Aug 2026, 17:47 | 1,240 | -3 |
| 7 Aug 2026, 21:16 | 1,243 | first reading |
Engagement
3 posts held, back to 6 September 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
- 0.384%
- avg views ÷ 1,649 subscribers
- Avg views / post
- 6.3
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 3 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.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 3 (6 September 2026 – 6 September 2026) |
| Views total | 19 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Sept 2026, 00:22 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.
Recent posts
社团名:#えんがわまにあ 名称:失足女友 原名:NTRレRPG オチカノ ~僕だけだった君がオンナになった理由を教えて~ STEAM发行日期:2025 年 4 月 26 日 标签:#爆款 #RPG #官中 #PC #安卓joi #无码 #NTR #后宫 #纯爱 链接:入正地址 下载地址 故事介绍: 诗乃是主人公的青梅竹马。 不仅喜欢打游戏,擅长料理,而且性格温柔,身材火辣。 简直是集合了万般优点令人垂涎欲滴的形象。 但凡有男人与她擦肩而过,都会忍不住回头看上一眼。 如此完美的存在,却在不知不觉间堕入无法挽回的局面。 游戏内容: 本游戏为无战斗的探索型RPG。 游戏前半部分中,玩家将在上学的10天内,分早,中,晚,夜,深夜共计50个回合, 自由的与女主角们享受日常生活并探索周防市,在此期间回收故事的分歧要素。 游戏后半部分将根据之前回收的要素,进入女主角堕落的结局。(存在纯爱路线) 游戏特色: 时间管…
社团名:#みるくせーき 名称:NTRhou ~ 国民的妻子被分享~ 原名:NTRhou~国民の妻はシェアされる~ 贩卖日:2024年04月05日 0点 分类:#RPG #AI汉化 #PC #安卓直装 #人妻 #职场 #甜蜜 #援交 #被NTR #寝取# 内射 #怀 链接:➡️入正地址➡️下载地址 概要: 作为受欢迎的年轻政治家,主人公每天都致力于政治活动。 为解决我国的少子化问题而苦恼,制定了禁断之法。 可以分享国民妻子…“NTR法” 和在街上遇到的有夫之妇和女孩子签订契约并生孩子!? 当然NTR法的对象是自己的妻子…
Showing the 3 most recent of 3 posts we hold for @Gamex666. 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 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Gamex666 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 7 September 2026 – 7 September 2026
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.
“Galgamex 游戏 | 黄油频道” (@Gamex666), 1,649 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Gamex666.
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.