Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐—ฅ๐—ฒ๐—ฑ ๐—•๐—น๐—ผ๐—ฐ๐—ธ ๐—ฆ๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ โ„ข

Supergroup

๐—ฅ๐—ฒ๐—ฑ ๐—•๐—น๐—ผ๐—ฐ๐—ธ ๐—ฆ๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ โ„ข

@redblockservices

On this record: Topic ยท Growth ยท Engagement ยท Citations ยท Cite this entry

8,579members

+938 since we began measuring on 6 August 2026

352 online right now

Risers and fallers across the register ยท movement among entries of 3,162โ€“10,000.

Register entry

Telegram ID-1002682001187
TypeSupergroup
Username@redblockservices
CreatedBetween 1 March 2025 and 31 July 2025 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live21 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 21 October 2026
On Telegramt.me/redblockservices

Topic

Other / unclassifiable โ€” a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channelโ€™s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

7,6418,5798,1106 August 2026 โ€” 7,641 members6 August 2026 โ€” 7,648 members9 August 2026 โ€” 7,702 members12 August 2026 โ€” 7,744 members15 August 2026 โ€” 7,796 members18 August 2026 โ€” 7,836 members22 August 2026 โ€” 7,909 members25 August 2026 โ€” 7,967 members25 August 2026 โ€” 7,967 members28 August 2026 โ€” 7,990 members31 August 2026 โ€” 8,025 members4 September 2026 โ€” 8,068 members9 September 2026 โ€” 8,134 members13 September 2026 โ€” 8,183 members17 September 2026 โ€” 8,230 members25 September 2026 โ€” 8,319 members5 October 2026 โ€” 8,411 members11 October 2026 โ€” 8,494 members15 October 2026 โ€” 8,529 members18 October 2026 โ€” 8,549 members21 October 2026 โ€” 8,579 members6 August 202621 October 2026
21 measurements spanning 76 days, net +938. 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 7,500โ€“8,720 and does not start at zero.
Measurement log โ€” every members count we have recorded, most recent 20 of 21
Measured (UTC)MembersChange
21 Oct 2026, 01:488,579+30
18 Oct 2026, 08:288,549+20
15 Oct 2026, 07:498,529+35
11 Oct 2026, 23:558,494+83
5 Oct 2026, 01:178,411+92
25 Sept 2026, 20:578,319+89
17 Sept 2026, 08:558,230+47
13 Sept 2026, 16:188,183+49
9 Sept 2026, 21:188,134+66
4 Sept 2026, 11:368,068+43
31 Aug 2026, 20:238,025+35
28 Aug 2026, 18:147,990+23
25 Aug 2026, 20:377,967no change
25 Aug 2026, 15:437,967+58
22 Aug 2026, 07:367,909+73
18 Aug 2026, 15:377,836+40
15 Aug 2026, 09:447,796+52
12 Aug 2026, 09:457,744+42
9 Aug 2026, 19:547,702+54
6 Aug 2026, 18:407,648first reading

Engagement

No public post preview. We read this entry on 25 August 2026 and Telegram serves no public post stream for it โ€” the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Forward network

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 14 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.

Named by

Channels on the register whose posts name this channel's handle.

๐—›๐—ฎ๐—ฐ๐—ธ ๐—ง๐—ต๐—ฒ ๐—•๐—ผ๐˜… | ๐—–๐—ฃ๐—ง๐—ฆ | ๐—–๐—•๐—•๐—› | ๐—–๐——๐—ฆ๐—” | ๐—–๐—ช๐—˜๐—˜ | ๐—–๐—”๐—ฃ๐—˜ | ๐—–๐—ช๐—ฃ๐—˜ โ„ข
@htb_exams ยท 8,553
48 posts
๐—•๐˜‚๐—ด ๐—•๐—ผ๐˜‚๐—ป๐˜๐˜† ๐—˜๐˜…๐—ฝ๐—ฒ๐—ฟ๐˜๐˜€ โ„ข
@bug_bounty_experts ยท 8,587
46 posts
๐—”๐—น๐˜๐—ฒ๐—ฟ๐—ฒ๐—ฑ ๐—ฆ๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ถ๐˜๐˜† | ๐—–๐—ฅ๐—ง๐—ฃ | ๐—–๐—ฅ๐—ง๐—˜ | ๐—–๐—ฅ๐—ง๐—  | ๐—–๐—˜๐—ง๐—ฃ | ๐—–๐—”๐—ฅ๐—ง๐—ฃ | ๐—–๐—”๐—ฅ๐—ง๐—˜ โ„ข
@altered_security ยท 8,344
42 posts
๐—–๐˜†๐—ฏ๐—ฒ๐—ฟ๐—ช๐—ฎ๐—ฟ๐—™๐—ฎ๐—ฟ๐—ฒ ๐—Ÿ๐—ฎ๐—ฏ๐˜€ | ๐—–๐—ฅ๐—ง๐—” | ๐—–๐—ฅ๐—ง๐—ฆ ๐—ฉ๐Ÿฎ | ๐—ช๐—˜๐—•-๐—ฅ๐—ง๐—” | ๐—”๐—ฃ๐—œ-๐—ฅ๐—ง๐—” โ„ข
@cyberwarfare_exams ยท 8,280
41 posts
๐—ฅ๐—ฒ๐—ฑ ๐—ง๐—ฒ๐—ฎ๐—บ ๐—˜๐˜…๐—ฝ๐—ฒ๐—ฟ๐˜๐˜€ โ„ข ๏ธ
@red_team_experts ยท 8,696
31 posts
๐—˜๐—–-๐—–๐—ข๐—จ๐—ก๐—–๐—œ๐—Ÿ | ๐—–๐—˜๐—› | ๐—–๐—˜๐—› ๐—ฃ๐—ฟ๐—ฎ๐—ฐ๐˜๐—ถ๐—ฐ๐—ฎ๐—น | ๐—–๐—›๐—™๐—œ | ๐—–๐—˜๐—› ๐— ๐—ฎ๐˜€๐˜๐—ฒ๐—ฟ | ๐—–๐—ก๐—— | ๐—Ÿ๐—ฃ๐—ง - ๐—–๐—ฃ๐—˜๐—ก๐—ง โ„ข
@eccouncil_exams ยท 6,579
28 posts
๐—ญ๐—ฒ๐—ฟ๐—ผ ๐—ฃ๐—ผ๐—ถ๐—ป๐˜ ๐—ฆ๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ถ๐˜๐˜† | ๐—ฅ๐—ฒ๐—ฑ ๐—ง๐—ฒ๐—ฎ๐—บ ๐—ข๐—ฝ๐˜€ | ๐—ฅ๐—ฒ๐—ฑ ๐—ง๐—ฒ๐—ฎ๐—บ ๐—ข๐—ฝ๐˜€ ๐Ÿฎ | ๐—–๐—ฅ๐—ง๐—ข | ๐—–๐—ฅ๐—ง๐—Ÿ โ„ข
@zeropoint_security ยท 8,445
25 posts
๐—ข๐—ณ๐—ณ๐—ฆ๐—ฒ๐—ฐ | ๐—ข๐—ฆ๐—–๐—ฃ | ๐—ข๐—ฆ๐—ช๐—ฃ | ๐—ข๐—ฆ๐—˜๐—ฃ | ๐—ข๐—ฆ๐—˜๐—— | ๐—ข๐—ฆ๐—˜๐—˜ | ๐—ข๐—ฆ๐—ช๐—˜ | ๐—ข๐—ฆ๐——๐—” | ๐—ข๐—ฆ๐—ช๐—” โ„ข
@offsec_exams ยท 9,267
21 posts
๐—œ๐—ก๐—˜ | ๐—ฒ๐—๐—ฃ๐—ง | ๐—ฒ๐—–๐—ฃ๐—ฃ๐—ง | ๐—ฒ๐—ช๐—ฃ๐—ง | ๐—ฒ๐—ช๐—ฃ๐—ง๐—ซ | ๐—ฒ๐—–๐—œ๐—ฅ | ๐—ฒ๐—–๐—ง๐—›๐—ฃ โ„ข
@ine_exams ยท 8,827
15 posts
๐€๐ˆ ๐‚๐จ๐ฎ๐ซ๐ฌ๐ž๐ฌ, ๐“๐จ๐จ๐ฅ๐ฌ, ๐€๐ ๐ž๐ง๐ญ๐ฌ & ๐๐ž๐ฐ๐ฌ โ„ข
@aicoursesdaily ยท 1,670
12 posts
๐—ง๐—ต๐—ฒ ๐—ฆ๐—ฒ๐—ฐ๐—ข๐—ฝ๐˜€ ๐—š๐—ฟ๐—ผ๐˜‚๐—ฝ | ๐—–๐—–๐—ฃ๐—ฒ๐—ป๐—ซ-๐—”๐—ช๐—ฆ | ๐—–-๐—”๐——๐—ฃ๐—ฒ๐—ป๐—ซ | ๐—–๐—•๐—ง๐—ฒ๐—ฎ๐—บ๐—ฒ๐—ฟ โ„ข
@secops_exams ยท 8,044
7 posts
๐—ง๐—ฟ๐˜†๐—›๐—ฎ๐—ฐ๐—ธ๐— ๐—ฒ | ๐—ฆ๐—”๐—Ÿ๐Ÿญ | ๐—ฃ๐—ง๐Ÿญ | ๐—ฆ๐—˜๐—–๐Ÿญ โ„ข
@tryhackme_exams ยท 8,292
7 posts
๐—ฃ๐—ผ๐—ฟ๐˜๐—ฆ๐˜„๐—ถ๐—ด๐—ด๐—ฒ๐—ฟ | ๐—•๐—ฆ๐—–๐—ฃ โ„ข
@burpsuite_exams ยท 8,194
5 posts
๐—ฅ๐—ฒ๐—ฑ ๐—•๐—น๐—ผ๐—ฐ๐—ธ ๐—Ÿ๐—ถ๐—ป๐—ธ๐˜€ โ„ข
@certs_help ยท 10,534
1 post

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 21 October 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐—ฅ๐—ฒ๐—ฑ ๐—•๐—น๐—ผ๐—ฐ๐—ธ ๐—ฆ๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ โ„ขโ€ (@redblockservices), 8,579 members as measured 21 October 2026. Telegram Register, tgregister.com/channel/redblockservices.

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.