🍳荷包蛋 Rust失控进化内核 pinned «🔤🔤🔤 失控卡网已补卡 卡密以及任何售后联系 @Lixi1010 🍳卡网:https://816.zidianidc.com/shop/egggggggg»

Channel
eggggg6666
@eggggg6666
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
6subscribers
-17,107 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003717672285 |
|---|---|
| Type | Channel |
| Username | @eggggg6666 |
| Created | Between 1 February 2026 and 22 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/eggggg6666 |
Topic
Software piracy — 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 67% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 13:50 | 6 | -16,889 |
| 1 Oct 2026, 19:55 | 16,895 | -276 |
| 18 Sept 2026, 12:42 | 17,171 | -18 |
| 16 Sept 2026, 08:57 | 17,189 | -4 |
| 14 Sept 2026, 11:20 | 17,193 | +4 |
| 12 Sept 2026, 19:40 | 17,189 | -15 |
| 10 Sept 2026, 23:02 | 17,204 | -23 |
| 7 Sept 2026, 21:16 | 17,227 | -11 |
| 4 Sept 2026, 23:16 | 17,238 | -8 |
| 3 Sept 2026, 10:24 | 17,246 | +3 |
| 2 Sept 2026, 03:37 | 17,243 | -4 |
| 1 Sept 2026, 02:46 | 17,247 | -4 |
| 31 Aug 2026, 01:28 | 17,251 | -5 |
| 30 Aug 2026, 03:25 | 17,256 | -1 |
| 29 Aug 2026, 00:48 | 17,257 | -2 |
| 27 Aug 2026, 22:14 | 17,259 | +1 |
| 26 Aug 2026, 22:34 | 17,258 | +7 |
| 26 Aug 2026, 01:32 | 17,251 | +1 |
| 25 Aug 2026, 03:56 | 17,250 | -1 |
| 23 Aug 2026, 22:15 | 17,251 | first reading |
Engagement
32 posts held, back to 22 July 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 53 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 32 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 15s
- Average length
- 38s
Measured directly from 2 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
154 reactions across 24 posts, in 13 distinct kinds. The most used accounts for 42.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 65 | 42.2% | |
| 👎 | 40 | 26.0% | |
| 👍 | 28 | 18.2% | |
| 😡 | 6 | 3.90% | |
| 🤯 | 4 | 2.60% | |
| 🤨 | 3 | 1.95% | |
| 🔥 | 2 | 1.30% | |
| 👏 | 1 | 0.649% | |
| 💩 | 1 | 0.649% | |
| 🤡 | 1 | 0.649% | |
| 🤪 | 1 | 0.649% | |
| 🤬 | 1 | 0.649% | |
| 🤮 | 1 | 0.649% |
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 24 of the 32 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 154 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 22 July 2026 to 1 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
🔤🔤🔤 失控卡网已补卡 卡密以及任何售后联系 @Lixi1010 🍳卡网:https://816.zidianidc.com/shop/egggggggg
👎1
🍳荷包蛋 Rust失控进化内核 pinned «https://816.zidianidc.com/shop/egggggggg 购买先使用备用卡网 目前主卡网正在修护 单透已修复部分手机没有效果的问题 售后联系: @lixi1010»
https://816.zidianidc.com/shop/egggggggg 购买先使用备用卡网 目前主卡网正在修护 单透已修复部分手机没有效果的问题 售后联系: @lixi1010
❤1👍1🤮1🤯1
失控进化实名账号 已上架 卡网购买链接:https://egg.rtlufw.cn/shop/egg 售后联系: @lixi1010
👍3🤯3
七夕活动: 8月21日起至9月1日 每日反馈高质量图到 @lixi1010 即可获取天卡或周卡一张 看反馈质量领取 卡网购买链接:https://egg.rtlufw.cn/shop/egg 售后联系: @lixi1010
👍1
网页雷达效果 网页雷达地址: rader.rtlufw.cn/login.html 可以共享给队友查看敌人位置 达到类似dma的效果 稳定奔放
❤8
🔤🔤🔤雷达版已上线! 网盘更新下载哦
👍4❤1
📩💵卡网:https://egg.rtlufw.cn/shop/egg 售后联系方式: @Lixi1010 双向联系: @iozzsxbot
❤1👍1
自瞄版更换了全新源码哦😙 推荐大家试试
👎8❤2
🔤🔤🔤自瞄 追踪版更新完毕 修复掉效果 ‼️‼️ (新版本100%稳定不掉效果)
❤5👍2
🔤🔤🔤: 追踪天卡 实名成品账号已补货 (🍳雷达以及预计今晚全项目上线) 📩💵卡网:https://egg.rtlufw.cn/shop/egg
Showing the 12 most recent of 32 posts we hold for @eggggg6666. 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.
Posts recorded as deleted after publishing
We recorded 1 post on @eggggg6666 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 1 September 2026
- Most recent seen missing
- 1 September 2026
- Median time before seen missing
- 6 days
- Seen missing in the last 30 days
- 0
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“eggggg6666” (@eggggg6666), 6 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/eggggg6666.
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.