Telegram RegisterThe public register of Telegram

Channel

Global Red Team

@GlobalRedTeam

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

12,422subscribers

-18 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001787474866
TypeChannel
Username@GlobalRedTeam
Descriptionستصبح هذه القناة دليلك إلى عالم أمن المعلومات والقرصنة. bot : @hackers54_bot
CreatedBetween 1 December 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/GlobalRedTeam

Growth

12,42112,44012,430.57 August 2026 — 12,440 subscribers7 August 2026 — 12,440 subscribers8 August 2026 — 12,436 subscribers9 August 2026 — 12,427 subscribers10 August 2026 — 12,426 subscribers11 August 2026 — 12,421 subscribers12 August 2026 — 12,422 subscribers12,4227 August 202612 August 2026
7 measurements spanning 5 days, net -18. 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 12,418–12,443 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 18:0312,422+1
11 Aug 2026, 15:0312,421-5
10 Aug 2026, 13:3312,426-1
9 Aug 2026, 15:1412,427-9
8 Aug 2026, 13:1712,436-4
7 Aug 2026, 15:0312,440no change
7 Aug 2026, 14:3212,440first reading

Engagement

20 posts held, back to 16 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
4.68%
avg views ÷ 12,422 subscribers
Avg views / post
581
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
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 3 August 2026
Posts held20 (16 March 20263 August 2026)
Views total2,325
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:24 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
107
Videos
124
Links
193

Lifetime counters from Telegram’s own channel header, read 13 August 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

43 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 76.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3376.7%
🤣36.98%
❤‍🔥24.65%
👍24.65%
🐳12.33%
🔥12.33%
😎12.33%

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 9 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 43reactions 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 16 March 2026 to 3 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.

Recent posts

3 Aug 2026, 18:00 UTC357 viewsread 13 August 2026
Forwarded from @nanvaluePhoto

cloudflary v1.0.0 — your Cloudflare Quick Tunnel, on autopilot. Just python cloudflared.py --url http://localhost:3000 and it runs forever: auto-restarts on crash, health-checks the URL, and exports every new trycloudflare.com link to files, Telegram, Slack, Discord, and webhooks — deduplicated so you never get the same URL twice. By @s4rrar ( GitHub ) | Open source

31 Jul 2026, 14:41 UTC705 viewsread 13 August 2026

Hello, World! This is a collection of our channels that may be useful to you during your journey in the technical field, especially in cybersecurity. https://t.me/addlist/nD70sWRf83U4ZTA0 أهلاً وسهلاً بكم جميعاً، هذه مجموعة من القنوات الخاصة بنا والتي قد تفيدكم خلال رحلتكم في المجال التقني وخاصةً في الأمن السيبراني. https://t.me/addlist/nD70sWRf83U4ZTA0

28 May 2026, 00:02 UTC≈2,400 views9 reactionsread 13 August 2026
Forwarded from @nanvaluePhoto

مؤخراً اشتغلت على سوفتوير لشركة ناشئة بيشتغل بنظام SaaS و Desktop App، قدرت أعملّه Reverse Engineering بأقل من 5 دقائق، اكتشفت كمية ثغرات كبيرة خلتني أقدر أحول السوفتوير لنسخة مجانية بالكامل وأخترق سيرفر الترخيص وأوصل لكل بيانات المستخدمين بكل سهولة. برضو الكود كان مليان ثغرات بتسمح بتنفيذ أوامر برمجية مباشرة على أجهزة المستخدمين، يعني اختراق أجهزتهم صار متاح وبسيط جداً، ووصلت لـ API Keys حساسة زي Gemini API Key، و

9

22 May 2026, 14:35 UTC≈2,110 views3 reactionsread 13 August 2026
Forwarded from @nanvaluePhoto

حوّل هاتفك لماسح باركود متّصل بالكمبيوتر عبر الوايفاي! عملت مشروع جديد مفتوح المصدر بمكّن المستخدم من استعمال الهاتف كماسح باركود مربوط بالكمبيوتر. نشرت الكود والإصدار الأول للتثبيت والتجربة على GitHub: https://github.com/s4rrar/link-scan

❤‍🔥2🔥1

22 May 2026, 07:51 UTC≈2,040 views1 reactionsread 13 August 2026

Hello, World! This is a collection of our channels that may be useful to you during your journey in the technical field, especially in cybersecurity. https://t.me/addlist/nD70sWRf83U4ZTA0 أهلاً وسهلاً بكم جميعاً، هذه مجموعة من القنوات الخاصة بنا والتي قد تفيدكم خلال رحلتكم في المجال التقني وخاصةً في الأمن السيبراني. https://t.me/addlist/nD70sWRf83U4ZTA0

1

18 Apr 2026, 16:58 UTC≈3,690 views7 reactionsread 13 August 2026

🔎 Pentest Mindmap — Your Visual Pentesting Companion 🔎 Dear members, We’re proud to introduce Pentest Mindmap, an interactive platform designed for pentesters and cybersecurity learners who want fast access to commands, workflows, and methodologies. 📊 PLATFORM HIGHLIGHTS 📊 🟢 VISUAL MINDMAP ACCESS ▪️ Structured and interactive navigation ▪️ Explore categories faster ▪️ Clear and efficient organization 🔎 SEARCH CAP

7

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

Citation-graph rank — 878,505 of 1,169,250entries 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.

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 1 registered channel — 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.

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.

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

“Global Red Team” (@GlobalRedTeam), 12,422 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/GlobalRedTeam.

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.