🐄 Attention, Kobe Community! ‼️ Please join the New Kobe DAO Telegram! 🔔 Click the link to stay informed with the latest updates and essential information. ⚠️ Important Notice: Due to technical challenges in our existing group, we are transitioning to a new Telegram group. 👍 We appreciate your cooperation in moving to the new platform. ℹ️ The current group will stay active until the transition is complete for al…

Channel
Kobe Announcements
@kobeannouncements
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
6subscribers
-1 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 | -1001829502651 |
|---|---|
| Type | Channel |
| Username | @kobeannouncements |
| Created | 14 October 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 6 times, most recently 9 October 2026 |
| On Telegram | t.me/kobeannouncements |
Topic
Other / unclassifiable — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 89% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 18:24 | 6 | -1 |
| 12 Aug 2026, 19:02 | 7 | no change |
| 7 Aug 2026, 11:54 | 7 | first reading |
Engagement
12 posts held, back to 14 October 2023 — 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 12 posts for this entry, the most recent from 11 January 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
182 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 30.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 56 | 30.8% | |
| 👍 | 50 | 27.5% | |
| 👏 | 20 | 11.0% | |
| ❤ | 18 | 9.89% | |
| 🎉 | 12 | 6.59% | |
| ❤🔥 | 8 | 4.40% | |
| 👀 | 7 | 3.85% | |
| 🙏 | 4 | 2.20% | |
| 🍾 | 3 | 1.65% | |
| 👌 | 3 | 1.65% | |
| 🥰 | 1 | 0.549% |
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 9 of the 12 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 182 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 14 October 2023 to 11 January 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.
Recent posts
🐄 Attention, Kobe Community! ⚠️ Our Telegram group has been unexpectedly deleted for an unknown reason, most likely fake reports. ✔️ We're diligently working on recovery. ‼️ While it is temporarily unavailable please only refer to this Announcement Channel and our Twitter. 🚫Please be aware, there may be scam groups emerging during this time. ❌ We will never send direct messages. 🔔 Stay alert for our official up…
🙏4👌3👏1
📶Launch Countdown!📶 🔥The moment we've all been waiting for is almost here - our official launch is happening in less than 24 hours! ➡️Launch Information The chat will be unmuted 2 hours before the launch happening on Friday October 27th @ 5PM UTC! 🟢Liquidity Pools Details There will be 2 pools launched on Sushiswap Arbitrum: •BEEF/ETH •BEEF/USDT Contract addresses will be pinned in the chat as soon as they becom…
👍13👀7❤🔥3🔥2❤1👏1🥰1
📶Dear Kobe 🐂 Community, Our first audit results are in, check out the PDF in our group! ‼️It's important to note that the Contract Owner will be the DAO contract, so any changes to the protocol would require a proposal to go through the voting process successfully. 🔗Thank you for your unwavering support. Let's shape the future together! 📣2 Days Left! Stay tuned for more exciting updates as we count down to launch…
👍14🔥9🎉5👏1
📶Dear Kobe 🐂 Community, The big day is almost here! 🔥Official Launch Date: Friday October 27th @ 5PM UTC! 🔗Thank you for your unwavering support. Let's shape the future together! 📣Stay tuned for more exciting updates as we count down to launch! 🌐Website | ❓Documentation | ✉️Telegram | 📣 Announcement Channel
🔥11👏8❤7❤🔥4🍾3
🔥Dear Kobe 🐂 Community, 🛡Audit Countdown Begins We're excited to announce that we've already submitted our contracts for auditing and we should receive the report in the following days! 🗓️ Get Ready For the Launch! Exact date and time will be announced tomorrow, October 23rd. 🔼Thank you for your unwavering support. Let's shape the future together! 📣Stay tuned for more updates as we progress! 🌐Website | ❓Document…
🔥9👍8❤7👏2
📈Dear Kobe 🐂 community, Our Liquidity Offering has successfully COMPLETED! 🎉 Thank you to everyone who participated and believed in our vision. Stay tuned for the next exciting steps of our journey. 🥩 Together, we'll soar even higher! 🚀 📣Stay tuned for more updates as we progress! 🌐Website | ❓Documentation | ✉️Telegram | 📣 Announcement Channel
🔥10🎉7👍6👏6❤🔥1
🔥Dear Kobe 🐂 Community, We're thrilled to announce that our Liquidity Offering has officially STARTED! This is your chance to be a part of Kobe's journey. Dive in now and secure your spot. 🥩 Thank you for your unwavering support. Let's shape the future together! 📣Stay tuned for more updates as we progress! 🌐Website | ❓Documentation | ✉️Telegram | 📣 Announcement Channel
🔥8👍5
📶Fair Launch Details📶 The moment we've all been waiting for is almost here - our official launch is happening in less than 24 hours! ☄️Liquidity Offering Information Date: October 20th at 5PM UTC Chain: Arbitrum Hard-cap: 30 ETH Max Allocation per Wallet: 0.5 ETH No Pre-sale/Whitelist 🔥100% of proceeds will be used to create BEEF/ETH and BEEF/USDT LPs on Sushiswap. Trading will start some time after the Liquidity …
🔥5👍4❤3👏1
📶Exciting news: The website and documentation are now live!📶 ⚡️We encourage everyone to read all the information and ask questions if something is unclear. 📣Liquidity Offering details will be announced in the next 48 hours, stay tuned! 🌐Website | ❓Documentation | ✉️Telegram | 📣 Announcement Channel
🔥2
⚡️Welcome to Kobe - The First Truly Decentralized Community Bank on Arbitrum!📶 🔔We're thrilled to have you join us on this exciting journey. Embrace the future with $BEEF for value growth or $STEAK for unprecedented stable returns. Here you'll find groundbreaking features not available anywhere else, such as: ✔️Innovative DeFi mechanism ✔️Overcollateralized stablecoin - $STEAK ✔️Industry-leading stablecoin yield th…
Channel created
Showing the 12 most recent of 12 posts we hold for @kobeannouncements. 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.
Handles this channel named that no longer answer
- Dead references
- 2
- 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
- 2
- vacant every time we have ever looked
@kobeannouncements named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 9 posts, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Kobe Announcements” (@kobeannouncements), 6 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/kobeannouncements.
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.