Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐—š๐—ฎ๐˜๐—ฒ๐—ซ

Channel

๐—š๐—ฎ๐˜๐—ฒ๐—ซ

@heroxslayera

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

481subscribers

-33 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-1003447284166
TypeChannel
Username@heroxslayera
Created4 December 2025 โ€” measured โ€” dated from the channelโ€™s first post
First recorded8 August 2026
Last confirmed live2 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/heroxslayera

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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

481514497.57 August 2026 โ€” 514 subscribers8 August 2026 โ€” 514 subscribers8 August 2026 โ€” 513 subscribers16 August 2026 โ€” 505 subscribers24 August 2026 โ€” 504 subscribers30 August 2026 โ€” 501 subscribers10 September 2026 โ€” 496 subscribers17 September 2026 โ€” 490 subscribers2 October 2026 โ€” 481 subscribers7 August 20262 October 2026
9 measurements spanning 56 days, net -33. 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 476โ€“519 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 16:21481-9
17 Sept 2026, 07:58490-6
10 Sept 2026, 01:56496-5
30 Aug 2026, 18:36501-3
24 Aug 2026, 10:16504-1
16 Aug 2026, 15:46505-8
8 Aug 2026, 16:24513-1
8 Aug 2026, 04:04514no change
7 Aug 2026, 17:32514first reading

Engagement

6 posts held, back to 4 December 2025 โ€” the 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 6 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1,023 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 18.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
๐Ÿ‘18418.0%
โค18017.6%
๐Ÿฅฐ16816.4%
๐Ÿ”ฅ16716.3%
๐Ÿคฉ16716.3%
๐Ÿ‘15515.2%
โคโ€๐Ÿ”ฅ10.098%
๐ŸŒš10.098%

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 4 of the 6 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 1,023 reactions in total: the kind of figure the paragraph above means by โ€œa reaction total printed elsewhere on the pageโ€.

Measured over the 6 most recent posts we hold, published 4 December 2025 to 27 June 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

6 Jun 2026, 19:17 UTCโ‰ˆ1,120 views2 reactionsread 8 August 2026

These are all our new projects Network ๐Ÿซถ @GTxnet Methodsโšก @methfix MMโšก @representativer Chats [market place]โšก @dudhupglu Services โšก @crossbonds Our botโšก @teamslyrsbot Join our entire community

โคโ€๐Ÿ”ฅ1๐Ÿฅฐ1

Signed HERO

3 Jun 2026, 11:13 UTC393 views2 reactionsread 8 August 2026
Forwarded from @representativerPhoto

Official @representativer Channel ๐Ÿ•ท Ensure a safe deal through one of our trusted middlemen. ๐Ÿš€Provided by @heroxslayera and @gtxnet

โค1๐Ÿฅฐ1

Signed HERO

16 Mar 2026, 10:22 UTCโ‰ˆ3,640 views1,014 reactionsread 8 August 2026
Photo

๐—ช๐—ฒ๐—น๐—ฐ๐—ผ๐—บ๐—ฒ ๐˜๐—ผ ๐—š๐—ฎ๐˜๐—ฒ๐—ซ ๐—ป๐—ฒ๐˜๐˜„๐—ผ๐—ฟ๐—ธ ๐—–๐—ฟ๐—ฒ๐—ฎ๐˜๐—ถ๐—ป๐—ด ๐˜€๐—ผ๐—บ๐—ฒ๐˜๐—ต๐—ถ๐—ป๐—ด ๐—ป๐—ฒ๐˜„ ๐Ÿ•ธโšก๏ธ click down given button to join the entire community. ๐Ÿ—กโšก๏ธ๐Ÿ’ซ

๐Ÿ‘184โค179๐Ÿคฉ167๐Ÿฅฐ166๐Ÿ”ฅ162๐Ÿ‘155๐ŸŒš1

Signed usernames

5 Mar 2026, 09:46 UTCโ‰ˆ4,950 views5 reactionsread 8 August 2026

#hero #hawk #slayer #harsh

๐Ÿ”ฅ5

Signed แŽปแŽฌแ’แŽพ

Showing the 6 most recent of 6 posts we hold for @heroxslayera. 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

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.

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

โ€œ๐—š๐—ฎ๐˜๐—ฒ๐—ซโ€ (@heroxslayera), 481 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/heroxslayera.

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.