Channel
@AWEAnnouncements
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,736subscribers
-306 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001423743050 |
|---|---|
| Type | Channel |
| Username | @AWEAnnouncements |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/AWEAnnouncements |
Crypto & trading — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 01:20 | 1,736 | -5 |
| 5 Oct 2026, 03:35 | 1,741 | -20 |
| 26 Sept 2026, 21:00 | 1,761 | -51 |
| 18 Sept 2026, 02:18 | 1,812 | -28 |
| 13 Sept 2026, 19:40 | 1,840 | -16 |
| 10 Sept 2026, 00:19 | 1,856 | -27 |
| 5 Sept 2026, 02:37 | 1,883 | -42 |
| 1 Sept 2026, 03:58 | 1,925 | -61 |
| 29 Aug 2026, 09:06 | 1,986 | -32 |
| 26 Aug 2026, 01:33 | 2,018 | -8 |
| 23 Aug 2026, 06:56 | 2,026 | -4 |
| 19 Aug 2026, 10:54 | 2,030 | -1 |
| 16 Aug 2026, 17:58 | 2,031 | -4 |
| 13 Aug 2026, 02:47 | 2,035 | -1 |
| 9 Aug 2026, 23:36 | 2,036 | -3 |
| 7 Aug 2026, 08:53 | 2,039 | -3 |
| 6 Aug 2026, 11:22 | 2,042 | no change |
| 6 Aug 2026, 11:06 | 2,042 | first reading |
20 posts held, back to 30 April 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 2 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
4 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 50.0% | |
| 👏 | 2 | 50.0% |
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 4 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 4 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 30 April 2026 to 5 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.
July was all about building beyond the World Cup at AWE. Together with Polyvaults, we: → Launched the Referral System and Potential Return display → Wrapped up the $10,000 Football Manager World Cup campaign and distributed rewards → Reached the Top 100 Polymarket Builders leaderboard with $150K+ in monthly volume → Continued exploring new index strategies and structured products → Expanded visibility across the pr…
AWE Weekly Update (July W5) Over the past week, we continued advancing Polyvaults’ product development, exploring new product directions, and expanding AWE’s visibility across the Base AI ecosystem: - @polyvaults_ai continued exploring new product features, including new index-related products, to provide users with more flexible ways to express their views and participate in prediction markets. - The Polyvaults F…
AWE Weekly Update (July W4) Over the past week, we continued advancing Polyvaults’ product development, expanding ecosystem visibility, and strengthening our presence across the AI and prediction market ecosystems: - @polyvaults_ai continued improving its product experience and preparing for upcoming product upgrades and new features. - The Polyvaults Football Manager World Cup campaign officially concluded, with …
AWE Weekly Update (July W3) Over the past week, we continued expanding visibility across the AI and prediction market ecosystems, while supporting ecosystem growth through product development, community campaigns, and ecosystem exposure: - @polyvaults_ai continued exploring new possibilities around index creation and strategy composition, with early testing underway for its next major product update. - The Polyvau…
AWE Weekly Update (July W2) Over the past week, we continued exploring new possibilities for Polyvaults, expanded its visibility across the prediction market community, and maintained strong momentum for $AWE within the Base AI ecosystem. – @polyvaults_ai is exploring more possibilities around index creation and strategy composition, with early testing now underway. – Joined the Prediction Hour AMA hosted by @pred…
AWE Weekly Update (July W1) Over the past week, we continued improving the Polyvaults product experience, expanded the World Cup campaign, and maintained strong visibility across the Base and prediction market ecosystems: - Polyvaults introduced several product updates, including the Referral System and Potential Return display, improving user experience and sharing efficiency. - The Polyvaults Football Manager Wo…
June was all about World Cup strategy execution at AWE. ⚽️ Together with Polyvaults, we: → Launched the 2026 World Cup Index → Introduced the Football Manager World Cup campaign with a $10,000 prize pool → Continued improving the Polyvaults World Cup experience → Expanded visibility across the prediction market and Base ecosystems → Strengthened treasury security through Coinbase Custody In July, the focus continu…
AWE Weekly Update (June W4) Over the past week, we continued expanding the @polyvaults_ai World Cup campaign and maintained strong visibility across the Base ecosystem: - The Polyvaults World Cup campaign advanced to the knockout stage, continuing to bring more users into prediction markets through World Cup strategies and leaderboard competitions. - $AWE was highlighted as a top gainer by AI on Base, reflecting co…
AWE Weekly Update (June W3) Over the past week, we continued optimizing the World Cup experience on Polyvaults, drove campaign participation, and gained further visibility across the prediction market ecosystem: - Continued maintaining and optimizing the Polyvaults World Cup 2026 Index experience, ensuring stable performance for World Cup-related index strategies. - Promoted the Polyvaults Football Manager World C…
👏1
AWE Weekly Update (June W2) Over the past week, we continued advancing prediction market initiatives, expanded Polyvaults around the World Cup, and strengthened the AWE ecosystem infrastructure: - The AWE Foundation successfully transferred a portion of its onchain holdings to Coinbase Custody, further enhancing treasury security and institutional-grade asset management. • @polyvaults_ai announced the launch of it…
👍1
AWE Weekly Update (June W1) Over the past week, we continued advancing Polyvaults strategy development, expanded its community presence, and maintained visibility across the Base ecosystem: - Developed Polyvaults index strategies around major global events, including the 2026 FIFA World Cup. - Expanded the @polyvaults_ai community through engagement initiatives and strategy-related content. - Published the AWE Ma…
AWE Weekly Update (May W4) Over the past week, we continued advancing Polyvaults strategy development, expanded its independent community presence, and stayed active across the Base ecosystem: - Continued designing Polyvaults index strategies, exploring prediction market index directions for major global events such as the World Cup. - Created a dedicated X account for polyvaults_ai as a focused channel for produc…
Showing the 12 most recent of 20 posts we hold for @AWEAnnouncements. 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.
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.
@AWEAnnouncements named 3 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“AWE Announcement Channel” (@AWEAnnouncements), 1,736 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/AWEAnnouncements.
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.