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 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
13 measurements spanning 43 days, net -34. 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 1,310–1,354 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
19 Sept 2026, 02:17
1,315
-3
14 Sept 2026, 20:38
1,318
-4
11 Sept 2026, 04:58
1,322
-7
5 Sept 2026, 23:41
1,329
-6
1 Sept 2026, 14:13
1,335
-3
29 Aug 2026, 19:06
1,338
-2
26 Aug 2026, 09:04
1,340
-2
20 Aug 2026, 00:59
1,342
-2
17 Aug 2026, 11:34
1,344
-1
14 Aug 2026, 05:59
1,345
-3
11 Aug 2026, 03:48
1,348
-1
7 Aug 2026, 22:21
1,349
no change
7 Aug 2026, 12:35
1,349
first reading
Engagement
20 posts held, back to 23 April 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 May 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
7s
Average length
7s
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
597 reactions across 19 posts, in 23 distinct kinds. The most used accounts for 37.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
223
37.4%
❤
151
25.3%
🔥
60
10.1%
🥴
38
6.37%
🤨
27
4.52%
👏
17
2.85%
🎃
15
2.51%
😨
10
1.68%
😁
8
1.34%
🤔
8
1.34%
🗿
6
1.01%
🙏
6
1.01%
👾
4
0.67%
🤷
4
0.67%
🦄
4
0.67%
☃
3
0.503%
🫡
3
0.503%
🎉
2
0.335%
👌
2
0.335%
🙊
2
0.335%
3 further kinds
4
0.67%
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 19 of the 20 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 597 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 23 April 2024 to 1 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
💎Yesterday there was a glitch in the technical part of the game
📱Today: we will return eggs to all players, add the ability to change the order price, view your orders, and delete orders
🚀We apologize for any inconvenience caused. Have a great game everyone!
We've officially launched 🥳
🚀 Today we made our official launch. Prior to this, we were testing our game and giving early players the opportunity to earn eggs
⚡️ As of today, we have, as part of our development strategy, raised the entry to the game to 100,000 eggs 📈
🏆 There are many more updates ahead of us.
🔠🔠🔠🔠 team
New updates in 🔠🔠🔠🔠
🚀 We are pleased to inform you that we are finalizing the preparations for the official launch of our project and getting ready for the official start of the project
Already tomorrow will be the results of the contest and the accrual of prizes 🚀
✅ You can still take part in it. You can read the terms and conditions in this post
In a soon update we will add the following features:
- Deleting …
We've increased the cost of boosts 🙌
✅ In recent posts, we've said that as part of our development path, we would increase the cost of boosts.
And we did 🤝
The cost of boosts will now be as follows:
😘 Autoplay 600K
😘 X2 350K
😘 X5 550K
😘 X10 900K
😘 X100 8 million
🔝 Follow our updates. A massive advertising campaign will be launched very soon along with the official launch 🚀 🚀🚀
🤩 Dear players. We check each case separately.
Someone has already received eggs on their account. And someone else is waiting. It will take longer than we thought. A little patience.
Everyone will receive eggs on their account before the official launch of the game
🤩 Dear players, our support team has received more than 1,500 messages in the last 24 hours
✅Many repeated the same questions. Some players have not yet been credited with eggs. We see everything and remember about everyone
✅There are also difficulties with placing orders for some players
🗝Our technical team solves each task step by step
✨We see everything. Don't worry. It is not necessary to ask the same questio…
✅ Dear players: all operations in the game must be carried out from the wallet from which the pre-mine was paid and it is this wallet that must be linked to the account.
Otherwise, the funds will go to the game development fund. This is the last warning.
🚀 The contest with cool prizes has started.
We have launched a contest with a grand prize of 1,000,000 eggs 💎
The conditions are simple:
• invite as many partners as possible to the game and get your rewards.
✔️ The contest will run until the official launch of the project.
You can get the following rewards:
😘 1st place autoplay and boost X10
😘 2nd place boost 10X
😘 3rd place autoplay
😘 4th place 5X
😘 5th place …
BOOSTERS PRICE INCREASE
✔️ All applications for lost eggs have been collected and our team is engaged in the accrual of eggs to the players' balances. How was posted before all eggs will be credited until 25.04 15:00 UTC
Also the amount of pre-mining bonuses has been reduced to 30K
🚀 Boosters price will be increased on 26.04 at 17:00 UTC
⚡️ We are finalizing preparations for the official launch, which will be on …
✅ Those applications that were sent in the correct form: one message ID + number of eggs; sent to the technical department. Other messages will be processed later. If you have not submitted your application in the correct form (not add any other info! Just ID TELEGRAM and number of eggs) please submit it again to speed up processing.
✅One message! ID and number of EGGS. Not two or more🙏🏻
❤11
Showing the 12 most recent of 20 posts we hold for @Eggs_p2e. 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
Names
Channels on the register whose handles appear in this channel's posts.
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
@Eggs_p2e 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.
@eggs_support_bot named in 1 post, 8 August 2026 – 8 August 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 19 September 2026 — this
entry's latest reading, not the date you are reading this.
“EGGS” (@Eggs_p2e), 1,315 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Eggs_p2e.
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.