Telegram RegisterThe public register of Telegram
Telegram profile photo for W1R3L355

Channel

W1R3L355

@v01dch4nn3l

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,155subscribers

+225 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002594148727
TypeChannel
Username@v01dch4nn3l
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/v01dch4nn3l

Topic

Technology — 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 18 September 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 why it has no browse page of its own yet.

Growth

9301,1551,042.57 August 2026 — 930 subscribers8 August 2026 — 930 subscribers15 August 2026 — 946 subscribers24 August 2026 — 1,047 subscribers27 August 2026 — 1,059 subscribers30 August 2026 — 1,063 subscribers2 September 2026 — 1,071 subscribers6 September 2026 — 1,078 subscribers10 September 2026 — 1,128 subscribers14 September 2026 — 1,140 subscribers18 September 2026 — 1,155 subscribers7 August 202618 September 2026
11 measurements spanning 42 days, net +225. 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 896–1,189 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 05:371,155+15
14 Sept 2026, 09:391,140+12
10 Sept 2026, 21:571,128+50
6 Sept 2026, 03:371,078+7
2 Sept 2026, 04:521,071+8
30 Aug 2026, 15:181,063+4
27 Aug 2026, 07:141,059+12
24 Aug 2026, 06:531,047+101
15 Aug 2026, 20:42946+16
8 Aug 2026, 00:51930no change
7 Aug 2026, 12:07930first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

197 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 55.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💊10955.3%
3216.2%
👍115.58%
🔥105.08%
👎84.06%
😁84.06%
🥰84.06%
🤣63.05%
👀21.02%
💔10.508%
😭10.508%
🤨10.508%

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 20 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 197 reactions 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 10 July 2026 to 4 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

4 Aug 2026, 11:40 UTC240 views8 reactionsread 8 August 2026

Provisioning Packages – Purple Team https://ipurple.team/2026/08/04/provisioning-packages/

💊3🔥3👎1💔1

1 Aug 2026, 15:38 UTC508 views16 reactionsread 8 August 2026
Photo

Photo, posted without a caption

💊94🤣2👎1

1 Aug 2026, 15:37 UTC405 views11 reactionsread 8 August 2026
Photo

Photo, posted without a caption

💊7🥰2👎1😁1

30 Jul 2026, 06:38 UTC529 views13 reactionsread 8 August 2026
File

Binary Ninja 5.3.9757 (2026-06-09) https://binary.ninja/changelog/

💊6🔥32👎1🤣1

28 Jul 2026, 07:50 UTC592 views7 reactionsread 8 August 2026

vBulletin Runtime Template runMaths Preauth RCE - SSD Secure Disclosure https://ssd-disclosure.com/vbulletin-runtime-template-runmaths-preauth-rce/

💊41👎1🔥1

27 Jul 2026, 17:00 UTC611 views9 reactionsread 8 August 2026

Exploiting Volvo/Eicher’s fleet management platform to gain control over all users and vehicles https://eaton-works.com/2026/07/27/my-eicher-hack/

💊4👀2👍2👎1

23 Jul 2026, 04:24 UTC784 views5 reactionsread 8 August 2026

CVE-2026-50458: Finding a UAF in the Windows Brokering File System | Rotce's Blog https://rotcee.github.io/posts/CVE-2026-50458-finding-a-UAF-in-windows-brokering-file-system/

💊4🤨1

20 Jul 2026, 12:12 UTC867 views7 reactionsread 8 August 2026

бля тут искал чет связанное с тором наткнулся на такую хуйню, сайт на 4й позиции в гугле по запросу "tor search" как оказалось там был сюрприз которого не ждали https://www.torry.io/

💊6👍1

17 Jul 2026, 15:26 UTC922 views9 reactionsread 8 August 2026

Windows AppResolver LPE: From AppContainer to SYSTEM • David Carliez https://davidcarliez.github.io/blog/windows-appresolver-lpe-to-system/

💊8👍1

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

Forward network

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.

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

“W1R3L355” (@v01dch4nn3l), 1,155 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/v01dch4nn3l.

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.