Telegram RegisterThe public register of Telegram
Telegram profile photo for 三角洲MVP官方群

Channel

三角洲MVP官方群

@MVP777888

On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

24,416subscribers

+12,942 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002597191158
TypeChannel
Username@MVP777888
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/MVP777888

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

Previous handles

@MVP777888 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@SO668866
held 8 August 20268 August 2026

Growth

11,47424,41617,9458 August 2026 — 11,474 subscribers8 August 2026 — 11,824 subscribers9 August 2026 — 12,267 subscribers10 August 2026 — 12,620 subscribers11 August 2026 — 12,826 subscribers12 August 2026 — 13,009 subscribers13 August 2026 — 13,837 subscribers14 August 2026 — 15,357 subscribers16 August 2026 — 16,251 subscribers17 August 2026 — 17,181 subscribers18 August 2026 — 17,427 subscribers19 August 2026 — 17,682 subscribers20 August 2026 — 17,928 subscribers21 August 2026 — 18,413 subscribers23 August 2026 — 18,650 subscribers24 August 2026 — 19,065 subscribers25 August 2026 — 19,186 subscribers26 August 2026 — 19,312 subscribers27 August 2026 — 19,444 subscribers28 August 2026 — 19,577 subscribers29 August 2026 — 19,928 subscribers30 August 2026 — 20,233 subscribers31 August 2026 — 20,471 subscribers1 September 2026 — 20,737 subscribers2 September 2026 — 20,945 subscribers3 September 2026 — 21,141 subscribers5 September 2026 — 21,578 subscribers8 September 2026 — 22,427 subscribers11 September 2026 — 23,207 subscribers13 September 2026 — 23,539 subscribers14 September 2026 — 23,840 subscribers16 September 2026 — 24,126 subscribers19 September 2026 — 24,416 subscribers8 August 202619 September 2026
33 measurements spanning 42 days, net +12,942. 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 9,533–26,357 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 04:5524,416+290
16 Sept 2026, 19:2024,126+286
14 Sept 2026, 18:5723,840+301
13 Sept 2026, 08:4023,539+332
11 Sept 2026, 12:5923,207+780
8 Sept 2026, 20:5922,427+849
5 Sept 2026, 16:0121,578+437
3 Sept 2026, 19:3721,141+196
2 Sept 2026, 10:4520,945+208
1 Sept 2026, 12:4720,737+266
31 Aug 2026, 15:3920,471+238
30 Aug 2026, 19:1420,233+305
29 Aug 2026, 15:4319,928+351
28 Aug 2026, 15:4619,577+133
27 Aug 2026, 17:3719,444+132
26 Aug 2026, 17:1819,312+126
25 Aug 2026, 20:1819,186+121
24 Aug 2026, 19:0319,065+415
23 Aug 2026, 02:3618,650+237
21 Aug 2026, 17:4618,413first reading

Engagement

196 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 61 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.28%
avg views ÷ 24,416 subscribers
Avg views / post
800
37 posts measured
Reaction rate
1.28%
reactions ÷ views · ER floor
Posts in window
37
of 196 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 3 September 2026
Posts held196 (5 August 20263 September 2026)
Views total29,613
Reactions total380
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 17:36 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
2m 12s
Average length
19s

Measured directly from 7 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.

Reaction mix

1,258 reactions across 181 posts, in 8 distinct kinds. The most used accounts for 97.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,22497.3%
🔥110.874%
🥰80.636%
👏70.556%
30.238%
👨‍💻30.238%
🤓10.079%
🤝10.079%

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 181 of the 196 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 1,258 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 196 most recent posts we hold, published 5 August 2026 to 3 September 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

3 Sept 2026, 16:10 UTC73 views4 reactionsread 3 September 2026

😀😃😀卧槽 有这么好的频道你咋不早点告诉我? 林羽/enen/雪花/橘子含泪推荐的大牛频道 三角洲新赛季 即将更新 吊打全网 TG群 @KGKG111333 QQ不禁言交流群 1109339843

👍4

Signed 金牌客服

3 Sept 2026, 12:15 UTC248 views9 reactionsread 3 September 2026

#频道互推 #相似推荐 ------------------------------ 📢 七夜改文件官方🇨🇳《副频道》 📢 昆明公开榜 📢 小福星的个人频道 📢 马桶先生 📢 沈阳最新资源 📢 小芳的日常 📢 秋叶公益项目主频道 📢 简州 三角洲 【官方频道】 📢 婉棠的频道 📢 如一小窝 ------------------------------ ☁️ 互推入口:@sososo

👍9

Signed SOSO搜搜

2 Sept 2026, 12:33 UTC594 views12 reactionsread 3 September 2026

😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+参与联系负责人 @didb431 全网收广告位出的直接私信我 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道

👍12

2 Sept 2026, 12:10 UTC259 views12 reactionsread 3 September 2026

#频道互推 #相似推荐 ------------------------------ 📢 迪迦拯救昆明📸CCTV 📢 Cc公益端口 数据号 通知频道 📢 上海(怡红院)人气榜 📢 kg集团 📢 贵阳 技师 📢 长沙来嫖 📢 AJ文案社🏖头像馆🌈壁纸 📢 源头-机器人开发|源码|网站|定制搭建二开 📢 鱼子酱授课日记 📢 悠悠的频道 ------------------------------ ☁️ 互推入口:@souso

👍12

Signed SOSO搜搜

2 Sept 2026, 06:15 UTC203 views7 reactionsread 3 September 2026
Forwarded from @KGKG111333Video

🚨🚨🚨 ➡️三角洲KG内核 UDP解密 ❤️支持三角洲-国服 ❤️可以无视三角洲加密坐标 ❤️无需配置任何参数 ❤️不动任何游戏数据! ❤️支持全系统 支持纯C模式 懒得介绍了 功能齐全 无需多说 下单地址 https://yun.ffkpp.top/shop/33EAJS2A

👍7

Signed 金牌客服

1 Sept 2026, 16:36 UTC140 views9 reactionsread 2 September 2026
Forwarded from @kuluomi886Photo

❗️❗️❗️❗️❗️❗️❗️❗️❗️❗️ 解密版本题卡链接: https://luoye.yjsfk.cn/shop/kuluomi886 交流群反馈加时活动 客服看到会随机挑选私信赠送加时5h 工艺版本网盘下载最新版本: https://drive.uc.cn/s/a17ea05433874?public=1 库洛米工艺无解密v1.0.0版本 库洛米收费解密v15.0.0版本 库洛米三角洲本地模型sh 工艺版本卡密 @kuluomi886

👍9

1 Sept 2026, 12:05 UTC541 views14 reactionsread 2 September 2026

#频道互推 #相似推荐 ------------------------------ 📢 七夜改文件官方🇨🇳《副频道》 📢 昆明公开榜 📢 马桶先生 📢 沈阳最新资源 📢 小芳的日常 📢 小福星的个人频道 📢 秋叶公益项目主频道 📢 简州 三角洲 【官方频道】 📢 江北❤紫凝的心房 📢 未设置 ------------------------------ ☁️ 互推入口:@SosoCnBot

👍14

Signed SOSO搜搜

1 Sept 2026, 05:29 UTC146 views5 reactionsread 1 September 2026
Forwarded from @KGKG111333Video

🚨🚨🚨 ➡️三角洲KG内核 UDP解密 ❤️支持三角洲-国服 ❤️可以无视三角洲加密坐标 ❤️无需配置任何参数 ❤️不动任何游戏数据! ❤️支持全系统 支持纯C模式 懒得介绍了 功能齐全 无需多说 下单地址 https://yun.ffkpp.top/shop/33EAJS2A

👍5

Signed 金牌客服

31 Aug 2026, 16:17 UTC394 views10 reactionsread 1 September 2026

😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+参与联系负责人 @didb431 全网收广告位出的直接私信我 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道

👍10

31 Aug 2026, 12:00 UTC508 views8 reactionsread 1 September 2026

#频道互推 #相似推荐 ------------------------------ 📢 迪迦拯救昆明📸CCTV 📢 Cc公益端口 数据号 通知频道 📢 上海(怡红院)人气榜 📢 kg集团 📢 贵阳 技师 📢 长沙来嫖 📢 AJ文案社🏖头像馆🌈壁纸 📢 源头-机器人开发|源码|网站|定制搭建二开 📢 黎明通知频道 📢 过往集团业务频道 ------------------------------ ☁️ 互推入口:@soso

👍8

Signed SOSO搜搜

31 Aug 2026, 07:22 UTC99 views5 reactionsread 31 August 2026
Forwarded from @KGKG111333Video

🚨🚨🚨 ➡️三角洲KG内核 UDP解密 ❤️支持三角洲-国服 ❤️可以无视三角洲加密坐标 ❤️无需配置任何参数 ❤️不动任何游戏数据! ❤️支持全系统 支持纯C模式 懒得介绍了 功能齐全 无需多说 下单地址 https://yun.ffkpp.top/shop/33EAJS2A

👍5

Signed 金牌客服

30 Aug 2026, 23:35 UTC111 views4 reactionsread 31 August 2026

😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+参与联系负责人 @didb431 全网收广告位出的直接私信我 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道

👍3🔥1

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

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 10 registered channels — 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.

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

“三角洲MVP官方群” (@MVP777888), 24,416 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/MVP777888.

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.