Telegram RegisterThe public register of Telegram
Telegram profile photo for Meshkatnet

Channel

Meshkatnet

@meshkatnet

On this record: Growth · Engagement · Reactions · Advertising · Posts · Telegram's recommendations · Cite this entry

643subscribers

+3 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-1001003835549
TypeChannel
Username@meshkatnet
CreatedBetween 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/meshkatnet

Growth

640643641.57 August 2026 — 640 subscribers7 August 2026 — 640 subscribers14 August 2026 — 641 subscribers21 August 2026 — 642 subscribers28 August 2026 — 643 subscribers7 August 202628 August 2026
5 measurements spanning 21 days, net +3. 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 640–643 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 08:11643+1
21 Aug 2026, 05:38642+1
14 Aug 2026, 21:28641+1
7 Aug 2026, 08:48640no change
7 Aug 2026, 08:24640first reading

Engagement

20 posts held, back to 30 March 2025the 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.

ERR · 30 days
11.4%
avg views ÷ 643 subscribers
Avg views / post
73.5
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 20 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 31 July 2026
Posts held20 (30 March 202531 July 2026)
Views total147
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 08:48 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.

Reaction mix

10 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍550.0%
440.0%
🙏110.0%

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 6 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 10reactions 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 30 March 2025 to 31 July 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.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
257
over 1 measured post
Median views · rest
289
over 19 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 20 most recent posts we hold, published 30 March 2025 to 31 July 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

31 Jul 2026, 18:09 UTC71 viewsread 7 August 2026
Photo

⭕️ آسیب پذیری Unauthenticated File Upload RCE یک آسیب‌پذیری بحرانی در کامپوننت RSFiles! (com_rsfiles) برای Joomla با شناسه CVE-2026-57827 منتشر شده است. این نقص از نوع Unauthenticated File Upload بوده و به مهاجم اجازه می‌دهد بدون نیاز به احراز هویت , فایل دلخواه خود را روی سرور آپلود کند. ریشه آسیب‌پذیری، Split-Controller Upload Bypass است که منجر به دور زدن کنترل‌های امنیتی فرآیند آپلود شده و در نهایت امکان نوشتن

31 Jul 2026, 17:52 UTC76 viewsread 7 August 2026

⭕️ هشدار | بهره‌برداری فعال از آسیب‌پذیری 0day در Cisco FMC مهاجمان در حال سوءاستفاده از آسیب‌پذیری Zero-Day با شناسه CVE-2026-20316 در Cisco Firepower Management Center (FMC) هستند. این آسیب‌پذیری به مهاجمان از راه دور و بدون نیاز به احراز هویت اجازه می‌دهد با استفاده از اعتبارنامه‌های ثابت (Static Credentials) به یک حساب کاربری با سطح دسترسی پایین وارد شده و به اطلاعات حساس سیستم دسترسی پیدا کنند. شرکت Cisco هشد

23 Jul 2026, 07:54 UTC144 viewsread 7 August 2026

⭕️ آسیب‌پذیری جدید و پرخطر در 7-Zip امکان اجرای کد مخرب را فراهم می‌کند. یک آسیب‌پذیری تازه با شناسه CVE-2026-14266 در نرم‌افزار 7-Zip افشا شده است که می‌تواند به هکرها اجازه دهد با فریب کاربر برای باز کردن یک فایل XZ دستکاری‌شده، کد دلخواه خود را روی سیستم اجرا کنند. این نقص امنیتی از نوع Heap Overflow در ماژول پردازش فایل‌های XZ است و شدت آن بالا (High Severity) ارزیابی شده است. در صورت موفقیت حمله، کد مخرب با همان

15 Jul 2026, 13:29 UTC205 viewsread 7 August 2026

⭕️ در جریان یک پروژه تحقیقاتی روی آسیب‌پذیری‌های 0day در SharePoint، تیم Rapid7 Labs دو آسیب‌پذیری جدید را کشف کرد که با chain آن‌ها می‌توان روی یک سرور آسیب‌پذیر، RCE به دست آورد. امروز Rapid7 و Microsoft نخستین آسیب‌پذیری این زنجیره را با شناسه CVE-2026-55040 منتشر کردند. این نقص، امکان دور زدن احراز هویت مبتنی بر توکن JWT در Microsoft SharePoint را فراهم می‌کند. https://www.rapid7.com/blog/post/ve-cve-2026-55040-

11 Jul 2026, 18:25 UTC210 viewsread 7 August 2026

⭕️ ‏CVE-2026-47291 یک باگ بحرانی در درایور HTTP.sys ویندوز است که به مهاجم اجازه اجرای کد از راه دور در سطح کرنل را می‌دهد. مشکل اصلی در تابع UlpParseHeader() است: وقتی سرور هدرهای HTTP زیادی (حدود ۶۵ هزار خط) را در قالب پکت‌های TLS جداگانه دریافت می‌کند، یک متغیر ۱۶-بیتی که اندازه بافر را مدیریت می‌کند سرریز (overflow) شده و به اعداد کوچک برمی‌گردد. نتیجه این است که درایور حافظه کمتری از آنچه نیاز است اختصاص می‌دهد

27 Jun 2026, 07:30 UTC257 viewsread 7 August 2026
Advertisement

⭕️ ‏آسیب‌پذیری Onelogon که توسط تیم RUB-SoftSec در مقاله USENIX WOOT’26 مستند شده، یک نقص امنیتی ناشی از پیاده‌سازی ناقص پچ Zerologon است؛ مایکروسافت برای حفظ سازگاری با سیستم‌های قدیمی، سازوکار استثنای VulnerableChannelAllowList را در پروتکل Netlogon اضافه کرد که همین لیست به مهاجم اجازه می‌دهد با حمله Meet-in-the-Middle و بدون نیاز به credential معتبر، کنترل کامل Domain Controller و کل دامنه را به دست آورد. برخلاف

27 Jun 2026, 05:30 UTC232 viewsread 7 August 2026

🎥 فکر می‌کنی مانیتورت واقعاً روی 60Hz یا 120Hz کار می‌کنه؟ 🌀 خیلی از کاربرا بعد از خرید مانیتورهای 120Hz، 144Hz یا حتی 165Hz متوجه میشن که ویندوز هنوز روی 60Hz تنظیم شده و از تمام توان نمایشگر استفاده نمی‌کنن! 🌐 سایت TestUFO بهت نشون میده نرخ نوسازی واقعی نمایشگرت چقدره، فریم‌دراپ داری یا نه، Motion Blur چطوره و آیا تنظیمات نمایشگر درست انجام شده یا نه. 🔗 testufo.com ✅ اگه عدد نمایش داده شده با مشخصات مانیتورت یک

26 Jun 2026, 07:29 UTC220 views2 reactionsread 7 August 2026
Photo

یک ایده ساده برای سیم ها در شبکه با این روش می توانید سیم ها و کابل های نامنظم را به صورت زیبا و منظم در کنار یکدیگر آرایش دهید و از کار خود لذت ببرید . 🆔 @meshkatnet ✉️ [email protected] 🌍 www.meshkatnet.ir 🆔 @meshkatnet

👍2

23 Jun 2026, 05:30 UTC255 viewsread 7 August 2026

⭕️ اکستنشن APIReaper برای ساده‌تر کردن تست API داخل Burp Suite طراحی شده است. با این ابزار می‌تونید Swagger یا Postman Collection رو لود کنید، endpointها رو به‌صورت دسته‌بندی‌شده ببینید و بدون نیاز به وارد کردن دستی، درخواست‌ها رو مستقیم به Repeater بفرستید. همچنین امکان تنظیم Base URL و Authorization توکن‌های مختلف هم به‌صورت یکجا روی همه درخواست‌ها وجود داره. مناسب برای Pentester و Bug Hunter ها. لینک پروژه: https:

6 Jun 2026, 06:29 UTC360 views2 reactionsread 7 August 2026

⭕️ در تحلیل آسیب‌پذیری بحرانی CVE-2026-20182 در پشته شبکه Cisco Catalyst SD-WAN، یک نقص منطقی (Logic Bug) قابل توجه در تابع vbond_proc_challenge_ack شناسایی شد . این حفره امنیتی در لایه DTLS (پورت ۱۲۳۶) و سرویس vdaemon واقع شده است؛ جایی که برخلاف سایر تجهیزات مانند vSmart یا vEdge، برای دستگاه‌های نوع ۲ یعنی vHub، هیچ مکانیزم راستی‌آزمایی (Verification) تعریف نشده است. به محض دریافت پیام CHALLENGE_ACK با هویت جعلی،

2

15 Oct 2025, 10:15 UTC549 viewsread 7 August 2026

Security Update – Microsoft October 2025 Patch Tuesday Vulnerabilities: Multiple Critical and Zero-Day Vulnerabilities Across Microsoft Products CVEs: CVE-2025-0033 – AMD Restricted Memory Page Corruption (Zero-Day / Critical) CVE-2025-24052 – Agere Modem Driver Elevation of Privilege (Zero-Day) CVE-2025-24990 – Agere Modem Driver Elevation of Privilege (Zero-Day) CVE-2025-2884 – TPM 2.0 Out-of-Bounds Read (Zero-Day)

26 Sept 2025, 05:45 UTC452 viewsread 7 August 2026

Security Update – Cisco Secure Firewall ASA & FTD VPN Web Server Vulnerability: Remote Code Execution – VPN Web Server Input Validation Flaw CVE: CVE-2025-20333 Severity: 9.9 (Critical) Summary: A critical remote code execution (RCE) vulnerability exists in the VPN web server of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software. The issue stems fr

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

Appears in Telegram’s recommendations for other channels

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.

آیلتس تافل/ IELTS
@ielts_990 · 46,111
Telegram ranks this channel #52 of 70 here — alongside 69 others — read 27 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Meshkatnet” (@meshkatnet), 643 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/meshkatnet.

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.