Channel
@sniffnet
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
174subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002347529918 |
|---|---|
| Type | Channel |
| Username | @sniffnet |
| Created | Between 1 September 2024 and 19 February 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/sniffnet |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 14:39 | 174 | +1 |
| 30 Aug 2026, 23:28 | 173 | -1 |
| 23 Aug 2026, 20:25 | 174 | -1 |
| 16 Aug 2026, 21:33 | 175 | +2 |
| 8 Aug 2026, 14:31 | 173 | no change |
| 7 Aug 2026, 23:35 | 173 | first reading |
19 posts held, back to 19 February 2025 — 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 19 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
121 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 31.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 38 | 31.4% | |
| 🎉 | 32 | 26.4% | |
| 👍 | 19 | 15.7% | |
| 🔥 | 15 | 12.4% | |
| 👏 | 13 | 10.7% | |
| 💯 | 2 | 1.65% | |
| 🆒 | 1 | 0.826% | |
| 🤯 | 1 | 0.826% |
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 19 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 121 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 19 February 2025 to 1 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.
It’s been 4 years since Sniffnet’s first line of code 🥳 Since then, the project has grown enormously: we’ve gone from “the temptation to make a GUI is strong” to the most popular network monitoring app on GitHub. To celebrate the anniversary, we’ve shared part of the journey on our blog: ➡️ https://sniffnet.app/news/fourth-anniversary
🎉8👏3
Sniffnet v1.5.1 was just published 🎉️️️️️️ Measure connections latency, support CIDR ranges in IP blacklists, new translations of the app, and other improvements. Release page
❤8
Sniffnet hits the newsstand! 🗞️ LinuxUser, a popular German tech magazine, featured Sniffnet on the cover of their July issue, with a 3-page deep dive inside. It's lowkey exciting to see Sniffnet make the jump from screens to paper!
🎉11👏4
Sniffnet just reached 500k downloads! 🎉 What started almost for fun nearly 4 years ago is now installed half a million times worldwide. Huge thanks to everyone who has used Sniffnet and shared feedback over time helping to get here. 🫶 Sniffnet won’t stop and we already can’t wait for the 1 million mark! Let’s keep the snowball rolling and make network monitoring comfortable for even more people! 🚀 Blog post.
🎉5❤2👏2
New domain name and official emails for Sniffnet 📨 The old domain (sniffnet.net) was chosen in a hurry, didn't include mail services, and as time passed we grew more and more dissatisfied with it, especially because of the "net" repeating in the app name and TLD. We could've just updated the old plan to add emails, but we took the opportunity to also change the domain name to sniffnet.app, which is more fitting for…
👍9👏1
Sniffnet 1.5 is out 🎉 This is a remarkable milestone as Sniffnet is now finally able to show the applications and programs that are using your network bandwidth! Read the blog post to know more about this and other new major features.
🎉6❤2👏2🔥1
One of the most annoying programming challenges we've ever faced 🤦♂️ In today's blog post, we go through the challenges and implementation details of supporting process identification in Sniffnet. If implementing this feature seems like a no-brainer to you, well… read the post because it turned out to be a much more complex task than one could imagine, and this is the reason why the related GitHub issue has been o…
🎉2🔥2❤1👍1
Did you know that the source code behind Sniffnet is written using RustRover? 🦀 RustRover is an IDE by JetBrains that makes Rust programming more productive thanks to features like context-aware code completion, on-the-fly quick-fixes, and smart refactorings. Today we’re proud and excited to share that Sniffnet is included in the latest blog post by JetBrains itself, as part of the series “Open Source in Focus”.
❤5
Monitoring a remote machine's network activity can be challenging 😫 But, hey — the latest version of Sniffnet introduced webhook notifications as a possible way to address this problem. Today's blog post will show you how to use Sniffnet to monitor your machine’s Internet traffic from afar, and you’ll learn how to get the most out of built-in notifications by setting up advanced packet filter programs. We wish you…
❤3👍1💯1
Sniffnet 1.4.2 is here 🥳️️️️ The most relevant additions are the ability to forward in-app notifications to a custom webhook URL, and the possibility to freeze packet captures. Moreover, from now on the app is also built and shipped for Windows ARM64 architectures. You can find more information in the release page.
👍3💯1
Sniffnet version 1.4.1 is out 🎉 Enhanced filtering capabilities with support for BPF syntax, support for monitoring the 'any' interface on Linux, and extended configurations persistence are just some of the new features introduced with this release. This is also the first version to be shipped as an AppImage for Linux, and to have a digitally signed installer for Windows. See the GitHub release for more info, and t…
❤2🔥2
Sniffnet is 3 years old today 🥳 This is the perfect moment to glance back at the past year, have a look at what the future holds, and reflect on the importance of sustainable open source when it comes to a project’s longevity. There is also a little spoiler in the blog post, so make sure to give it a read!
❤6
Showing the 12 most recent of 19 posts we hold for @sniffnet. 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Sniffnet” (@sniffnet), 174 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/sniffnet.
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.