Telegram RegisterThe public register of Telegram
Telegram profile photo for đҽѵíł Channel

Channel

đҽѵíł Channel

@Devil_tournament

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

145subscribers

+0 since we began measuring on 17 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002159171068
TypeChannel
Username@Devil_tournament
DescriptionGoodbye Rx¹
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live17 August 2026
Measurements held2
On Telegramt.me/Devil_tournament

Growth

14517 Aug 2026, 13:30 — 145 subscribers17 Aug 2026, 13:45 — 145 subscribers17 Aug 2026, 13:3017 Aug 2026, 13:45
2 measurements taken within a single day. 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 144–146 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 13:45145no change
17 Aug 2026, 13:30145first reading

Engagement

20 posts held, back to 11 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 14 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
64
Videos
37
Links
29

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

Video runtime
12m 55s
Average length
1m 37s

Measured directly from 8 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

69 reactions across 15 posts, in 11 distinct kinds. The most used accounts for 65.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4565.2%
🏆57.25%
🔥57.25%
❤‍🔥34.35%
👍22.90%
👎22.90%
🕊22.90%
😁22.90%
💔11.45%
💯11.45%
🤷11.45%

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 15 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 69reactions 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 11 September 2025 to 14 December 2025, 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

14 Dec 2025, 20:23 UTC275 views9 reactionsread 17 August 2026
Photo

خیلی دیر شروع کردم ولی خب

9

Signed MehdiF

5 Dec 2025, 06:13 UTC400 views2 reactionsread 17 August 2026
Video

Game Play : HardPoint EM8 | BABY Highlight : Scrim Dostane

🏆1🔥1

Signed MehdiF

3 Dec 2025, 22:57 UTC309 views8 reactionsread 17 August 2026
Video

Video, posted without a caption

6❤‍🔥1🔥1

Signed MehdiF

28 Nov 2025, 13:42 UTC452 viewsread 17 August 2026
Video

آقا متین نوک حسین تک تقدیم بهت 4U :@AqaMatiniCloudy ❤️

Signed MehdiF

24 Nov 2025, 08:33 UTC298 views4 reactionsread 17 August 2026
Video

Game Play : HardPoint EM8 | BABY Highlight RankUp

4

Signed MehdiF

9 Nov 2025, 15:14 UTC184 viewsread 17 August 2026

https://t.me/Rs_playlistmusic

Signed đҽѵíłᴬᴹᴼ--ᴹᴹᴰ

16 Oct 2025, 17:08 UTC426 views2 reactionsread 17 August 2026
Video

#Gameplay #Mp Gameplay: Snip EM8 | BaBY 🦋 Highlight RankUp

1🤷1

Signed MehdiF

4 Oct 2025, 09:00 UTC402 views1 reactionsread 17 August 2026
Video

Game Play : HardPoint Nuke: 4you Devil ❤️☢ EM8 | BABY Highlight RankUp

1

Signed MehdiF

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

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

کانال ماز منابع کنکور 1405
@filmjozvemaz · 179,266
Telegram ranks this channel #35 of 70 here — alongside 69 others — read 17 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“đҽѵíł Channel” (@Devil_tournament), 145 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/Devil_tournament.

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.