Telegram RegisterThe public register of Telegram
Telegram profile photo for SlipNet

Channel

SlipNet

@SlipNet_app

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

51,928subscribers

-3,189 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003728285619
TypeChannel
Username@SlipNet_app
Descriptionhttps://github.com/anonvector/SlipNet
CreatedBetween 1 February 2026 and 5 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/SlipNet_app

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 81% 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 the other topics.

Growth

51,85355,11753,48551,9285 August 202610 November 2026
66 measurements spanning 97 days, net -3,189. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 51,363–55,607 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
10 Nov 2026, 15:4551,928-32
9 Nov 2026, 03:1051,960-25
7 Nov 2026, 21:0051,985+13
6 Nov 2026, 20:3151,972-6
5 Nov 2026, 21:5451,978+22
4 Nov 2026, 19:2751,956+103
3 Nov 2026, 18:4951,853-103
2 Nov 2026, 20:5751,956-11
1 Nov 2026, 23:4751,967-21
31 Oct 2026, 21:5551,988-26
31 Oct 2026, 00:3652,014-22
30 Oct 2026, 03:5152,036-24
29 Oct 2026, 04:4952,060-18
28 Oct 2026, 04:3752,078-12
27 Oct 2026, 07:5952,090-10
26 Oct 2026, 10:3852,100-1
25 Oct 2026, 13:0652,101+5
24 Oct 2026, 11:1652,096+43
23 Oct 2026, 08:4552,053+70
22 Oct 2026, 11:2751,983first reading

Engagement

15 posts held, back to 5 May 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 194 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
29.5%
avg views ÷ 51,928 subscribers
Avg views / post
15,300
3 posts measured
Reaction rate
2.26%
reactions ÷ views · ER floor
Posts in window
3
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held15 (5 May 2026 – 3 November 2026)
Views total46,000
Reactions total1,040
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 00:03 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
23
Videos
3
Links
33

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

10,918 reactions across 15 posts, in 38 distinct kinds. The most used accounts for 80.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8,78780.5%
😭8287.58%
👍3192.92%
👏1971.80%
❤‍🔥1241.14%
🫡1191.09%
🔥1161.06%
🙏930.852%
😢560.513%
🍓300.275%
💯270.247%
🤔260.238%
🤷‍♂250.229%
🥰190.174%
😁180.165%
🍾120.11%
🕊110.101%
😘110.101%
🤷‍♀110.101%
👀100.092%
18 further kinds790.724%

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 15 of the 15 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 10,918 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 5 May 2026 to 3 November 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.

Telegram Stars

Stars received
401
across the posts below
Posts paid on
15
of 15 we hold a reading for · 100%
Most on one post
142
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @SlipNet_app. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 15 most recent posts we hold for this entry, published 5 May 2026 to 3 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 10:28 UTC≈10,000 views287 reactions5 Starsread 11 November 2026
Forwarded from @Break_The_BarriersFile

آموزش گام‌به‌گام راه‌اندازی سرور شخصی با متد Soar، با اسکریپت Slipgate و کلاینت SlipNet پیش‌نیازها: برای اجرای این متد، به یک سرور خارج VPS و یک دامنه Domain نیاز دارید. گام ١: ایجاد رکوردهای DNS ١-١. در داشبورد اکانت کلاودفلر(یا هر میزبان دیگری)، یک رکورد A بسازید و آن را به آی‌پی سرور متصل کنید. مثال: dns.example.com ١-٢. دو عدد رکورد NS بسازید و آن‌ها را به رکورد A متصل کنید. مثال: r.example.com, rs.example.c…

❤228💯11🤷‍♀11🤷‍♂10👍6🔥6😁5🍓4

3 Nov 2026, 06:45 UTC≈18,200 views452 reactions6 Starsread 11 November 2026
File

@SlipNet_app

❤376🔥24🙏14👍11🫡7❤‍🔥5🥰5🍓4

3 Nov 2026, 06:44 UTC≈17,800 views301 reactions7 Starsread 11 November 2026

## SlipNet 2.5.6 ### New: Soar tunnel - Soar and Soar + SSH profiles, using Soar. Soar sends through all of your resolvers at once (over UDP, TCP/53, or both) and recovers quickly from packet loss. - Resolver discovery: Soar can find more working resolvers by itself. Each one is checked against the server's signed handshake, so hijacked or blocking resolvers are skipped. - Discovery list: choose where discovery loo…

❤252🔥22🙏9❤‍🔥5👍4💋3🤷2🆒2

26 Aug 2026, 03:40 UTC≈42,800 views841 reactions8 Starsread 11 November 2026

🌱 خبر خوب: لایسنس SlipNet به AGPLv3 تغییر پیدا کرد و الان دیگه کاملاً اوپن‌سورس محسوب میشه. این به این معنیه که هر کسی می‌تونه طبق شرایط این لایسنس از کدها استفاده کنه، تغییری ایجاد کنه و دوباره منتشرش کنه. ​امیدوارم این تصمیم راه رو برای خلاقیت، ایده‌های جدید و پروژه‌های مستقل بیشتر باز کنه. ⚠️ یک نکته: لایسنس اوپن‌سورس شامل اسم و لوگوی SlipNet نمی‌شه. اگه فورک یا برنامه جدیدی با این کد می‌سازید، لطفاً با اسم و ب…

❤700👏60👍39❤‍🔥10🔥7🍓6💯5😁5

29 May 2026, 06:48 UTC≈88,400 views777 reactions5 Starsread 11 November 2026

اگر به اینترنت بین‌الملل دسترسی دارید (یعنی سایت‌های خارجی براتون باز میشن)، و قصد دارید کانفیگ اختصاصی داشته باشید (غیر از روش‌های رایگان Tor و DoH) می‌تونید از پروتکل‌های دیگه SlipNet هم استفاده کنید. پروتکل‌های در دسترس شما این موارد هستن: ❇️ SSH ❇️ VLESS (فقط حالت WS) ❇️ ​NaiveProxy ❇️ ​Socks برای ساخت تمامی این پروتکل‌ها روی سرورتون می‌تونید از SlipGate استفاده کنید. اگر فقط خودتون می‌خواید از SSH استفاده ک…

❤650👍57🤔24🤷‍♂15🍓10👏7😘7🙏3

28 May 2026, 11:13 UTC≈99,900 views639 reactions5 Starsread 11 November 2026
Photo

اگر هنوز دسترسی به اینترنت جهانی براتون باز نشده و مجبورید از DNS Tunelling استفاده کنید: با قابلیت جدید DNS Pool دیگه نیازی نیست دستی دنبال DNS بگردید یا اسکن کنید. می‌تونید تا ۱۰۰۰ تا DNS به برنامه بدید تا خودش قبل اتصال تستشون کنه و ۱۰ تا از بهترین‌ها رو خودکار براتون انتخاب کنه. 🕊@slipnet_app

❤560👏48👍23😈3👻2👾1🔥1😱1

26 May 2026, 22:22 UTC≈69,600 views1,862 reactions142 Starsread 11 November 2026

من هم از حامد عزیز و تمامی دوستانی که این مدت با ساخت کانفیگ SlipNet به‌صورت رایگان به مردم کمک کردند، صمیمانه تشکر می‌کنم. همچنین از تیم net2share بابت توسعه VayDNS و DNSTM که کمک شایانی به پیشبرد پروژه SlipNet کرد. و تمامی دوستانی که با روش‌‌های دیگر کمک به حفظ دسترسی مردم به اینترنت آزاد کمک کردند.

❤1,680👏69👍46🙏24🫡16❤‍🔥8🍾6🍓5

26 May 2026, 17:04 UTC≈63,800 views402 reactions2 Starsread 11 November 2026

برای اینکه بدونید کدوم نسخه رو دانلود کنید این راهنما رو بخونید. اگر باز هم شک داشتید نسخه full universal رو دانلود کنید.

❤373👍23👏6

26 May 2026, 16:58 UTC≈88,000 views741 reactions5 Starsread 11 November 2026

درود و تشکر از همراهان همیشگی SlipNet که در دوره قطع و اختلال اینترنت همراهی کردند با توجه به وضعیت فعلی شبکه، می‌تونید از روش‌های زیر برای برقراری اتصال پایدار استفاده کنید: 🟢 ۱. اتصال از طریق Tor (نسخه Full - رایگان) (ویژه کاربران دارای دسترسی به اینترنت) ۱. روی علامت + (پایین سمت راست) بزنید و گزینه Tor را انتخاب کنید. ۲. یک نام دلخواه برای پروفایل وارد کنید. ۳. در بخش متدها، گزینه Manual selection را انتخاب …

❤688👍28🔥10🙏6💘3🥰3❤‍🔥2👏1

26 May 2026, 16:57 UTC≈123,000 views547 reactions12 Starsread 11 November 2026
File

🕊 @SlipNet_app

❤470❤‍🔥38🔥17👍13🍾5👏2😁2

26 May 2026, 16:57 UTC≈62,300 views314 reactions1 Starread 2 November 2026

v2.5.5 Changelog 🌐 DNS Pool (New) • Auto-Scan: Automatically picks the top 10 lowest-latency resolvers at connect. • Verification Toggle: Faster scans by default (10s timeout); optional full HTTP/SSH verification (18s timeout). ⚡️ DNS Auto-Tune (New) • Auto-tunes query length and rate limits for DNSTT, NoizDNS, and VayDNS profiles at connect. 🔍 DNS Scanner • Save working IPs as named pools and load them instantly …

❤265❤‍🔥28🔥11👍9😘1

26 May 2026, 13:13 UTC≈34,600 views257 reactions2 Starsread 2 November 2026
Forwarded from @netblocksPhoto

📈 Confirmed: Live metrics show a partial restoration to internet connectivity in #Iran on day 88, after 2093 hours of near-total isolation from international networks, the longest nationwide internet shutdown in modern history. It is unclear if the restoration will be sustained.

❤177😭31👍19🕊11👻6😢6👌2🤔2

Showing the 12 most recent of 15 posts we hold for @SlipNet_app. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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.

Mentions

Named by 21 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.

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.

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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“SlipNet” (@SlipNet_app), 51,928 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/SlipNet_app.

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.