Channel
@YOM_announcements
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
2,189subscribers
-23 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001759569119 |
|---|---|
| Type | Channel |
| Username | @YOM_announcements |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/YOM_announcements |
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 94% 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 |
|---|---|---|
| 17 Sept 2026, 14:01 | 2,189 | -3 |
| 13 Sept 2026, 18:16 | 2,192 | -7 |
| 10 Sept 2026, 05:36 | 2,199 | -8 |
| 5 Sept 2026, 01:02 | 2,207 | -9 |
| 1 Sept 2026, 08:58 | 2,216 | -4 |
| 29 Aug 2026, 05:18 | 2,220 | -1 |
| 26 Aug 2026, 03:06 | 2,221 | -2 |
| 23 Aug 2026, 03:02 | 2,223 | +6 |
| 19 Aug 2026, 04:47 | 2,217 | +2 |
| 16 Aug 2026, 14:44 | 2,215 | +2 |
| 12 Aug 2026, 18:03 | 2,213 | +2 |
| 10 Aug 2026, 00:28 | 2,211 | -1 |
| 7 Aug 2026, 07:32 | 2,212 | no change |
| 7 Aug 2026, 01:46 | 2,212 | first reading |
21 posts held, back to 25 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 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
193 reactions across 21 posts, in 10 distinct kinds. The most used accounts for 68.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 133 | 68.9% | |
| 😁 | 22 | 11.4% | |
| 👍 | 16 | 8.29% | |
| 🎉 | 7 | 3.63% | |
| ❤ | 5 | 2.59% | |
| ⚡ | 4 | 2.07% | |
| 👌 | 2 | 1.04% | |
| 😍 | 2 | 1.04% | |
| ❤🔥 | 1 | 0.518% | |
| 🤝 | 1 | 0.518% |
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 21 of the 21 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 193 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 25 July 2026 to 7 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.
🔥 Utility That Scales With the Network $YOM settles compute between workload providers and GPU operators. A session runs. A node delivers. The transaction settles on-chain. With every settlement: • 5% is programmatically burned • Hardcoded • Automatic As network utilization grows, token supply contracts. Real compute. Real settlements. Real utility. 🖇️ Learn More: yom.net/token
🎉2
⚡ One GPU. Two Workloads. A GPU that streams a game at 7 PM can process an AI inference job at 3 AM. One machine. Two workload types. Zero idle time wasted. YOM's network routes the right workload to the right node at the right time, helping existing hardware stay productive throughout the day. Gaming today. AI compute on the same rails. 🖇️ Learn more: yom.net/nano
🔥5
Hey NANO Operators 🫡 Your nodes are currently being shipped. However, for those of you who have received your nodes, we'd love it if you left a quick review on Freshminers. The reviews will help future operators make the right call. 🖇️ YOM NANO: FreshMiners
🔥5
⚡ Edge Compute vs. Data Centers A data center costs $10M+ before a single workload runs. Cooling. Power. Land. Staff. Maintenance. A distributed GPU network takes a different approach. Operators plug in hardware they already own, while the network routes workloads to the nearest available node. Infrastructure that scales with demand, not with budgets. 🖇️ Learn More: yom.net
🔥6
📣 YOM Town Hall | Tomorrow Join us tomorrow for a live demo of Warframe on Walter.gg, streamed through YOM's decentralized infrastructure. We'll also be discussing the latest gaming industry and data center news, and what these developments mean for the future of cloud gaming. What we'll cover: • Live Warframe demo on Walter.gg • Streaming gameplay through YOM • Gaming industry news and updates • The latest data c…
🔥3
🎮 One Week of Walter It's been one week since Walter went live on fully decentralized infrastructure. Real players. Real sessions. Real compute settling on-chain. No centralized servers. No single cloud provider. Just distributed GPU nodes doing the work. This is what DePIN looks like in production. 🖇️ Learn More: walter.gg
🔥10❤2
🚚 YOM NANO Update The first batch of YOM NANO devices has now been delivered to Freshminers for fulfillment. If you ordered your NANO through Freshminers, your shipment is now being processed. Tracking information will be shared directly by Freshminers as orders are dispatched. If you have questions about your shipment or need your tracking code, please contact Freshminers directly. Thank you for your patience. W…
🔥13👍3❤2🤝1
The AI Compute Problem AI companies are locked in a GPU arms race. Billions are being poured into data centers that can take years to build, while millions of GPUs already sitting in homes and offices remain underused. The compute exists. The problem is distribution. YOM connects available GPU capacity to real demand, turning idle hardware into a distributed compute network for AI and gaming workloads. The hard…
🔥7
📣 YOM Weekly Roundup Another week of building, shipping, and putting decentralized compute to work. Here’s what happened across YOM: 🖥️ Connecting GPU Supply We explored the GPU scarcity problem and why the real bottleneck is distribution. YOM connects existing GPU capacity with real workloads across a decentralized network. 🦍 Walter Is Live Walter brought YOM infrastructure to the user side, letting players stre…
🔥5🎉2
🔥 YOM Is Building Beyond the Network YOM isn't building in isolation. The ecosystem around YOM continues to grow: • Backed by Avalanche Foundation, Outlier Ventures, Borderless Capital, and CV VC • MiCA-compliant from day one • Selected for the Discord × Techleap Gaming Founders Circle The ecosystem is live. The capital is committed. The infrastructure is operational. YOM is building the decentralized compute la…
🔥10🎉1
📣 YOM Season 2 Extended Season 2 was supposed to end today, but we're extending it by two more months. Simple reason: we want more people to have a fair shot at participating, earning their place, and climbing the leaderboard. If you've been grinding, your progress isn't going anywhere. If you haven't started yet, now is the time. The rules remain the same. 🏆 Season 2 now runs through October.
😁21👍2
📣 YOM Town Hall | Today Join us today as we wrap up July and look back at some of the biggest developments across YOM. What we'll cover: • July's tech updates and key developments • The latest update on NANO shipments • A recap of Wednesday's discussion on the 5 pillars for cloud gaming success • What these developments mean for YOM and what's ahead 📅 Date: Friday, July 31 ⏰ Time: 4:00 PM UTC 📍 Live on: X | YouTu…
🔥13⚡2
Showing the 12 most recent of 21 posts we hold for @YOM_announcements. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Announcements - YOM” (@YOM_announcements), 2,189 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/YOM_announcements.
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.