Channel
@Termux_CS
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,228subscribers
-9 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001470183872 |
|---|---|
| Type | Channel |
| Username | @Termux_CS |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/Termux_CS |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 4 other registered channels. They sit inside a group of 6 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @NusurTech | 14 (8/8 hand-verifiable sample passed) | 1.00 | 13 minutes | @NusurTech (14–0) |
| @MasaLibrary0 | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (10–4) |
| @Programmer_Tech | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Programmer_Tech (11–3) |
| @CyberSecAM | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @CyberSecAM (10–4) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 3 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 14 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 6, the earliest publisher we hold is @Programmer_Tech. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 5 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 09:28 | 4,228 | -5 |
| 7 Aug 2026, 03:26 | 4,233 | -4 |
| 6 Aug 2026, 08:01 | 4,237 | first reading |
19 posts held, back to 14 July 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 5 pagesof Telegram’s post history, 20 posts per page.
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. It is computed over the 18 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (14 July 2026 – 6 August 2026) |
| Views total | 3,684 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:01 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.
17 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 94.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 94.1% | |
| 👍 | 1 | 5.88% |
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 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 18reactions 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 14 July 2026 to 6 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.
كيف تعرف أن هاتفك مخترق ؟ 12 علامة تدل على اختراق هاتفك هل تشك أن هاتفك مخترق؟ تعرّف على 12 علامة قد تشير إلى وجود اختراق، مثل استنزاف البطارية، بطء الأداء، ظهور تطبيقات مجهولة، وطرق التحقق من سلامة جهازك وحماية بياناتك. 🔴 رابط المقال كاملاً : 🔴🔴 https://www.nusurtech.ca/2026/08/how-to-know-if-your-phone-has-been-hacked.html
❤1
أخطاء يجب تجنبها عند #تطوير #مواقع_الويب يقع الكثير من #المطورين ، خاصة في بداية مسيرتهم، في #أخطاء تؤثر سلبًا على جودة #الموقع وتجربة المستخدم، مما يؤدي إلى انخفاض عدد الزوار أو زيادة معدل مغادرة الموقع. 🔴 رابط المقال كاملاً : 🔴🔴 https://www.nusurtech.ca/2026/08/mistakes-to-avoid-when-developing-websites.html
❤1
📱 تابع قناة #سما_منبج الاخبارية لحظة بلحظة على التلغرام👇 🕵️♂️🔗 https://t.me/samamanbig
❤1
أشهر طرق اختراق #الحسابات وكيف تحمي نفسك أصبحت #الحسابات_الرقمية هدفًا رئيسيًا للمهاجمين الإلكترونيين. وغالبًا لا يعتمد #نجاح_الاختراق على مهارات تقنية خارقة، بل على #استغلال_أخطاء_المستخدمين أو #ثغرات_أمنية بسيطة. 🔴 رابط المقال كاملاً : 🔴🔴 https://www.nusurtech.ca/2026/08/the-most-common-methods-for-hacking-accounts.html
❤1
نتائج البكالوريا في سوريا 2026 https://www.nusurtech.ca/2026/07/baccalaureate-results-in-syria-2026.html
❤1
الابتزاز الإلكتروني وانتهاك الخصوصية المخاطر وطرق الحماية في العصر الرقمي #الابتزاز_الإلكتروني هو استخدام الوسائل #الرقمية، مثل #مواقع_التواصل الاجتماعي وتطبيقات المحادثة والبريد الإلكتروني، لتهديد شخص أو #الضغط_عليه بهدف إجباره على تنفيذ طلب معين، وغالبًا ما يكون الطلب #الحصول_على_المال أو معلومات حساسة أو صور وملفات خاصة. 🔴 رابط المقال كاملاً : 🔴🔴 https://www.nusurtech.ca/2026/07/cyber-blackmail-and-violation-priv…
❤1👍1
هل محتاج تصميم يلفت النظر ويعكس هويتك بقوة؟ 🤩 أنا أوفر ليك خدمات تصميم مميزة تشمل: 🖌️ تصميم شعارات (Logo) احترافية 💳 تصميم كروت بنكك بشكل أنيق وجذاب 📢 تصميم إعلانات بمختلف المقاسات 📱 تصاميم سوشيال ميديا عصرية 🎯 أي أعمال خاصة بمجال التصميم ⭐ أفكار مبتكرة ⭐ دقة في التنفيذ ⭐ سرعة في التسليم ⭐ أسعار مناسبة رضاكم أولويتي 🤍✨ 📲 للتواصل المباشر عبر واتساب: 🔗 https://wa.me/966558240331
لطلاب الجامعات والبكالوريوس في السعودية والامارات والسودان وكافه الدول ، نسوي جميع انواع البحوث والمشاريع الجامعية و مشاريع الويب، بمقابل مادي يرضى الطرفين. 🌀حل واجبات وتكاليف 💬. 🌀تفريغ المحاضرات الصوتية والفيديوهات 🎤. 🌀اعداد بحوث ومشاريع تخرج 🎓. 🌀اعداد بحوث عاديه ✅. 🌀حل الإختبارات النهائية، الميد، الكوزات 🖋. 🌀اعداد تقارير وتكاليف 📄. 🌀صياغة سيرة ذاتية cv 👤. 🌀حل أنشطة وواجبات 🔰. 🌀تصميم بوربوينت احترافيه 🌌. 🌀تصميم اس…
أفضل #لغات_البرمجة للمبتدئين 2026: كيف تختار أول لغة برمجة؟ تعرف على أفضل مجالات #البرمجة للمبتدئين في 2026، واكتشف أشهر لغات البرمجة المطلوبة في سوق العمل، وكيف تختار #التخصص_المناسب لبناء مسيرة مهنية ناجحة. 🔴 رابط المقال كاملاً : 🔴🔴 https://www.nusurtech.ca/2021/10/programming-for-beginners.html
❤2
طلب حذف جميع البيانات المخزنة على الخادم يُعد حذف البيانات من الخادم (Server) إجراءً ضروريًا عندما لا تكون هناك حاجة لاستمرار تخزينها أو بناءً على طلب صاحبها. طلب حذف البيانات في هذه الحالة، يُقدَّم طلب رسمي إلى الجهة المسؤولة عن الخادم لحذف جميع البيانات المرتبطة بالشخص بشكل نهائي. ويشمل ذلك الملفات، وقواعد البيانات، وسجلات الاستخدام، وأي نسخ أخرى محفوظة ضمن أنظمة التخزين التابعة للخادم، وذلك وفقًا للسياسات والأنظمة…
❤1
دليل شهادة CompTIA Linux+ جميع الدروس وشرح كامل للتحضير للاختبار إذا كنت ترغب في احتراف إدارة أنظمة Linux والعمل في مجالات مثل إدارة الخوادم، والحوسبة السحابية، وDevOps، والأمن السيبراني، فإن شهادة CompTIA Linux+ تُعد واحدة من أفضل الشهادات العالمية التي تمنحك أساسًا قويًا في التعامل مع أنظمة لينكس. فهي تركز على المهارات العملية المطلوبة في بيئات العمل الحديثة، وتُعد خيارًا مثاليًا للمبتدئين والمحترفين على حد سواء. …
❤1
دليل شهادة CompTIA ITF+ جميع الدروس وشرح كامل للتحضير للاختبار إذا كنت ترغب في دخول عالم تقنية المعلومات (IT) من أوسع أبوابه، فإن شهادة CompTIA ITF+ (IT Fundamentals+) تُعد من أفضل الشهادات التأسيسية للمبتدئين. فهي تمنحك فهمًا شاملًا لأساسيات الحاسوب، وأنظمة التشغيل، والشبكات، وقواعد البيانات، وأمن المعلومات، والبرمجة، مما يجعلها نقطة انطلاق مثالية قبل الانتقال إلى شهادات احترافية مثل CompTIA A+ وNetwork+ وSecurity+.…
Showing the 12 most recent of 19 posts we hold for @Termux_CS. 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 — 954,598 of 1,151,006entries 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Termux CS” (@Termux_CS), 4,228 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Termux_CS.
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.