Telegram RegisterThe public register of Telegram

Channel

蛋蛋公益端(强势回归)

@Nbomb914

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

20,772subscribers

+2,739 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001671007435
TypeChannel
Username@Nbomb914
Description广告联系 @didb431
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Nbomb914

Growth

17,94420,77219,3587 August 2026 — 18,033 subscribers8 August 2026 — 18,028 subscribers9 August 2026 — 17,999 subscribers10 August 2026 — 17,972 subscribers11 August 2026 — 17,944 subscribers12 August 2026 — 18,291 subscribers13 August 2026 — 19,794 subscribers14 August 2026 — 20,772 subscribers7 August 202614 August 2026
8 measurements spanning 7 days, net +2,739. 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 17,520–21,196 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:3820,772+978
13 Aug 2026, 12:0719,794+1,503
12 Aug 2026, 13:0518,291+347
11 Aug 2026, 09:3317,944-28
10 Aug 2026, 10:0117,972-27
9 Aug 2026, 07:5117,999-29
8 Aug 2026, 05:4518,028-5
7 Aug 2026, 16:4518,033first reading

Engagement

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

ERR · 30 days
0.888%
avg views ÷ 20,772 subscribers
Avg views / post
184
20 posts measured
Reaction rate
1.85%
reactions ÷ views · ER floor
Posts in window
20
of 33 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. It is computed over the 16 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 August 2026
Posts held33 (9 January 202615 August 2026)
Views total3,688
Reactions total64
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 20:33 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

Photos
1,190
Videos
19
Links
22

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

94 reactions across 26 posts, in 6 distinct kinds. The most used accounts for 67.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6367.0%
1819.1%
🤔66.38%
🔥55.32%
😁11.06%
🥰11.06%

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

Measured over the 33 most recent posts we hold, published 9 January 2026 to 15 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

15 Aug 2026, 07:13 UTC312 views3 reactionsread 15 August 2026

合法催债!没有风险!非黑产!绿色项目💰💰💰 只需要一个手机! 无需两个手机,无需电脑,无任何风险 做完秒结账❤️正规项目 合法不犯法❤️ 无需本金 无需押金👉无风险 任何设备都可以做,最新软件不泄漏隐私🔏 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot

👍3

Signed 派大星

14 Aug 2026, 18:29 UTC63 views9 reactionsread 15 August 2026
Forwarded from @kuluomi886Photo

三角洲公益解密·库洛米公益项目|8月14日版 欢迎来拆包真实我打假我 全网最稳CPU渲染之一,纯算法解密,全机型适配解密,不闪框不漏人不遁地 工艺卡密点我获取 点我获取算法解密安装包 多种纯算法算法并行,一条路和谐另有兜底,一直能玩,任何解密都能开 ✅ AI自动压枪(识别图层+传感器调整,比自瞄更好演戏) ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 网页雷达+局域网雷达双端协同 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 🌟🙃🌟➡️ @kuluomi886

👍72

Signed 437

14 Aug 2026, 16:27 UTC158 views3 reactionsread 15 August 2026
Forwarded from @wo117wo

https://t.me/kuluomi886

👍3

Signed 437

14 Aug 2026, 12:20 UTC83 views7 reactionsread 15 August 2026
Forwarded from @angel_kernelFile

🎮❗️❗️❗️❗️Angel(天使)王者公益算法解密内核[3.0版本] ✔️修复开启解密野怪倒计时刷新问题 ✔️修复绘制授权问题 💻支持CPU渲染后端 安卓16以下推荐使用 😁纯算法解密 无视任何检测 ❌如果内存解密作者死全家 ❌如果内置端口作者死全家 ⭐音量键控制UI隐藏 or 显示 ⚡️解密教程必须看 https://t.me/angeljlpd/4731 ⚡️解密教程必须看 ⭐卡密:@Angel_kernel ✉️作者 @Jinang_Hello 🔝更新频道 https://t.me/angel_kernel 🚨Angel声明: https://t.me/angel_kernel/6049 🤩换装教程:https://t.me/angeljlpd/22697 👽APK使用教程:https://t.me/angeljlpd/22595

👍7

Signed 437

14 Aug 2026, 10:59 UTC335 views4 reactionsread 15 August 2026
Forwarded from @fire88666File

Fireworks公益测试 功能: 绘制+物资+无模块陀螺仪自瞄+漏打自瞄随意裸奔+掩体变色 还有绘制那些反正大概的都有,文案不知道怎么写,随便写的 还有啥要的可以找@sj0127 有问题说清楚直接说不经常在线 问题说明白,说完整,后面可能更新子弹追踪,网页雷达,找的人多就加,没人用就不加了

👍31

Signed fi

13 Aug 2026, 20:02 UTC131 views4 reactionsread 14 August 2026
Forwarded from @kuluomi886Photo

不是,怎么有群友拿库洛米一局赚了 800 万呀?这就是用库洛米的人均水平吗?😨 心动不如行动 快来试试吧! 库洛米公益解密 不动任何内存 欢迎拆包打假 解密: 纯算法解密,两条解密链路,非断点解密,非外部模拟解密,已完成所有机型解密 算法解密一:实时坐标同步 游戏把人物位置处理好以后,程序同步读取最新坐标,再对应到具体人物身上 算法解密二:移动队列解析 持续解析人物的移动更新队列,根据人物标识匹配坐标,并同步到绘制信息 不动任何内存,搭配自研无痕针对三角洲的独家驱动,稳定奔放 自瞄: AI自动压枪(识别图层+传感器调整,比自瞄更好演戏) 内核陀螺仪+漏打自瞄随意裸奔 内核模型/掩体变色+自研驱动 网页雷达+局域网雷达双端协同 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 🌟🙃🌟➡️ @kuluomi886

👍4

Signed 437

13 Aug 2026, 13:00 UTC512 views3 reactionsread 14 August 2026

朋友项目公益解密没进的可以进去看看试试 https://t.me/kuluomi886

👍3

Signed 437

13 Aug 2026, 11:28 UTC535 views3 reactionsread 14 August 2026

⭐今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 enen内核频道 林羽内核频道 小雪内核频道 吴迪公益破解频道 库洛米公益解密频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+用户 参加联系 @didb431 (频道主联系) 参加互推要求:频道10k+日浏览800 ------------------------------------- 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️

👍21

Signed 437

12 Aug 2026, 14:32 UTC372 views1 reactionsread 13 August 2026

⭐今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 enen内核频道 林羽内核频道 小雪内核频道 吴迪公益破解频道 时间内核频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进百人 参加联系 @didb431 (频道主联系) 参加互推要求:频道10k+日浏览800 ------------------------------------- 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️

👍1

Signed 437

12 Aug 2026, 07:56 UTC185 views1 reactionsread 13 August 2026
Forwarded from @SakurayydaFile

三角洲KX追踪 三服云更新优化版本 最新更新时间8.12 推荐使用小窗注入 功能:✅追踪 ✅范围 ✅瞬击 ✅容器绘制✅第三方视角 ❗️❗️➡️ @Sakurayyda ❗️❗️➡️ @EngineHacker

1

Signed 437

11 Aug 2026, 20:39 UTC128 viewsread 12 August 2026
Photo

点我一键加入三角洲/王者/和平工艺项目 频道内每天不定时发放💰福利

Signed 437

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

Citation-graph rank

Citation-graph rank — 653,531 of 1,480,688entries 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

Republished by

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

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

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

“蛋蛋公益端(强势回归)” (@Nbomb914), 20,772 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Nbomb914.

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.