Channel
@broxus
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
586subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001587781633 |
|---|---|
| Type | Channel |
| Username | @broxus |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/broxus |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 06:05 | 586 | -2 |
| 6 Aug 2026, 18:02 | 588 | no change |
| 6 Aug 2026, 01:31 | 588 | first reading |
20 posts held, back to 27 November 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 pageof 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 15 June 2026. An engagement rate over an empty window would be a number about nothing.
452 reactions across 18 posts, in 16 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 144 | 31.9% | |
| 🔥 | 114 | 25.2% | |
| 🎉 | 71 | 15.7% | |
| ❤ | 64 | 14.2% | |
| ⚡ | 24 | 5.31% | |
| 🌚 | 6 | 1.33% | |
| 💯 | 5 | 1.11% | |
| 🤩 | 5 | 1.11% | |
| 🆒 | 4 | 0.885% | |
| 🏆 | 3 | 0.664% | |
| 👌 | 3 | 0.664% | |
| 🥰 | 3 | 0.664% | |
| 👎 | 2 | 0.442% | |
| 🤗 | 2 | 0.442% | |
| ❤🔥 | 1 | 0.221% | |
| 🐳 | 1 | 0.221% |
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 18 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 452reactions 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 27 November 2024 to 15 June 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.
✨ Get Ready for a Massive SparX Upgrade! A major new SparX Wallet update is just around the corner, packed with improvements to make your TVM ecosystem experience smoother than ever. 🔐 Important Security Notice: As part of this upgrade, we are optimizing how the app handles account and seed phrase storage. Please make sure that your seed phrases are securely backed up OUTSIDE of the SparX app. Don't wait until the…
🔥6
⚙️ New T-Sol Release: 0.80.0 This update brings TVM Solidity Compiler 0.80.0 under the hood and includes a wide range of improvements for smarter, safer, and more efficient contract development. What’s new: • TON-oriented improvements, including support for a controlled bounce format • Better gas efficiency thanks to denser message packing • Upgrade to Solidity 0.8.30 from 0.8.24 • More helpful compile-time checks …
🔥6👌1👍1
🌐 Tycho Wallet API Is Live We’ve refactored the wallet API and published a new repo: tycho-wallet-api. What’s new: ⚡ A dedicated API built specifically for Tycho networks, designed to fully leverage their capabilities. 🛠 Easier onboarding and integration for new projects 🧹 Refactored codebase and updated README. Visit the repository to learn more! Future Tycho-focused development will continue there. 🟢
🔥6🎉4❤1
📰 New Blog Post: Inside the Latest T-Sol & Locklift Upgrades Threaded Solidity (T-Sol) powers smart contracts in the Tycho protocol, while Locklift is the toolkit for building, testing, and managing them. Over the past months, Broxus engineers shipped a series of major updates to both. In this deep-dive, we take you behind the scenes, covering the compatibility challenges, the solutions we shipped, and the new capa…
👍9🔥4⚡1🏆1
📎 New IntelliJ T-Sol Plugin Release Developers, it’s update time! A fresh version of the IntelliJ T-Sol plugin is now live with multiple improvements and fixes designed to make your smart contract development smoother and more reliable than ever. 🔗 Download the latest version and see what’s new: JetBrains After updating, please take a moment to rate the plugin and leave feedback. Your input helps shape future upd…
👍9🎉1
⬆️ Explore Venom Network with SparX! SparX has officially landed on the Venom Network Quests - giving its participants the perfect excuse to try out the most powerful wallet for TVM ecosystems. What makes it so powerful? Well, with SparX you: 🤹 No longer need separate wallets for TON, Venom, Everscale, Hamster Network and others. 🏦 Keep your assets safe. Private keys stay encrypted on your device. No personal dat…
⚡5🌚3❤2🏆1
🛡 SparX + Ledger = Maximum Security Big news, SparX fam! The latest mobile update brings Ledger device pairing. That’s right: you can now enjoy the sleek experience of SparX Wallet while keeping your tokens locked down with the industry’s most trusted hardware wallet. Ready to try it? 👉 Here's how
👍8🔥3🏆1
🛰️ TON Center-Compatible API Now Live on Tycho Testnet We’ve integrated partial support for the TON Center API into Tycho — making it easier than ever to build on our high-performance, TVM-compatible network. 🧰 Supported Methods • Block info • Jetton wallet queries • runGetMethod calls • …and more If you’ve already built products using the TON Center API, you can now test them on Tycho with zero integration overhe…
🔥9❤7👍4🌚2
🪩 SparX Wallet Just Got Even Sparxier! Meet the all-new in-app browser — rebuilt from the ground up for silky-smooth feel, turbo performance, and a look that pops. That’s not all! Recent updates also include: ✨ New onboarding flow 🔍 Smarter seed phrase scanning 📸 Built-in QR code scanner 🧲 TON Connect integration 🪙 Full support for TON Wallet V3R1, and V3R2 Plus, we’ve packed in tons of other performance and stabi…
🎉12❤8⚡4👍2
⚙️ Scheduled ChainConnect Maintenance Today we will perform a planned update on ChainConnect. During the update window, ChainConnect services may be temporarily unavailable. Thank you for your patience and understanding.
🔥10❤5👍4👌2
🐹 New Guide: How to Decide the Future of Hamster Network with Hamster DAO Decentralized governance is at the heart of the Hamster Network — and now there’s a complete guide to help you navigate it. Here’s what you’ll learn: → How to connect your wallet and join the DAO → How to lock HMSTR tokens and vote on proposals → Where to track governance stats and decisions → What it takes for proposals to pass 📚 Check out …
👍9❤3🔥2🎉1🤩1
📤 Big SparX Wallet Update Available — Upgrade Now! We’ve just rolled out a major update for SparX Wallet, packed with numerous improvements and optimizations that make your experience smoother, faster, and better than ever. Plus, SparX now supports importing seed phrases from other TON wallets, making it even easier to switch. ⬇️ Update your app and extension now to get the best SparX experience!
❤22👍15🎉10🔥4🆒2
Showing the 12 most recent of 20 posts we hold for @broxus. 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.
Citation-graph rank — 34,203 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 7 registered channels — 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Broxus” (@broxus), 586 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/broxus.
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.