Telegram RegisterThe public register of Telegram
Telegram profile photo for ʀᴀᴘᴛᴏʀ ᴡʀᴇsᴛʟɪɴɢ | رپتور رسلینگ

Channel

ʀᴀᴘᴛᴏʀ ᴡʀᴇsᴛʟɪɴɢ | رپتور رسلینگ

@RAPTOR_WRESTLING

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,299subscribers

-4 since we began measuring on 2 September 2026

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

Register entry

Telegram ID-1001457679155
TypeChannel
Username@RAPTOR_WRESTLING
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live7 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/RAPTOR_WRESTLING

Growth

1,2991,3031,3012 September 2026 — 1,303 subscribers2 September 2026 — 1,303 subscribers7 September 2026 — 1,299 subscribers2 September 20267 September 2026
3 measurements spanning 5 days, net -4. 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 1,298–1,304 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 12:201,299-4
2 Sept 2026, 11:241,303no change
2 Sept 2026, 07:151,303first reading

Engagement

20 posts held, back to 15 December 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
37.0%
avg views ÷ 1,299 subscribers
Avg views / post
481
5 posts measured
Reaction rate
3.24%
reactions ÷ views · ER floor
Posts in window
5
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 30 August 2026
Posts held20 (15 December 202530 August 2026)
Views total2,406
Reactions total78
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 07:15 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

Video runtime
1m 00s
Average length
12s

Measured directly from 5 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

596 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 32.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
19532.7%
🤣14324.0%
👍10718.0%
🔥6210.4%
💔386.38%
🥰315.20%
👎81.34%
🤔40.671%
👏30.503%
🤯20.336%
🎉10.168%
🕊10.168%
😱10.168%

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 596 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 15 December 2025 to 30 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

27 Aug 2026, 19:06 UTC333 views17 reactionsread 2 September 2026

خب فدای تونی خان بشم ولی متاسفانه رود تو آل اینت که از دور دیدم بسی بسیار ریدمان بود ( ببخشید نفسِ پاکستانی ) ببینیم خود آل این می‌نوازی یا نه

11🤣6

18 Aug 2026, 20:53 UTC671 views11 reactionsread 2 September 2026

یکسال پیش در چنین روزی 🫣 منم یکسال پیش راجب نظم نوین جهانی کد دادم

💔72🤔2

18 Aug 2026, 20:32 UTC542 views7 reactionsread 2 September 2026
Forwarded from @thoroush_clubPhoto

آرش بس کن

🥰3🤯2🤣1😱1

21 Jul 2026, 11:27 UTC≈1,220 views9 reactionsread 2 September 2026
Voice message

Voice message, posted without a caption

🔥6🥰2👍1

21 Jul 2026, 11:23 UTC≈1,180 views14 reactionsread 2 September 2026
Voice message

وینس ممکن ناجی دوباره پرو رسلینگ میشه ؟ 😏🔥😘😁😃

🥰10🔥4

20 Jun 2026, 17:33 UTC≈1,910 views31 reactionsread 2 September 2026

تعارف چیه اصلا دین عرب تو کون خر

20🥰6👏3👍2

20 Jun 2026, 17:31 UTC≈1,930 views35 reactionsread 2 September 2026

هوا گرمه سفید بپوشید روشن قرمز هم بد نیست

👍276🤔2

28 May 2026, 22:25 UTC≈2,440 views26 reactionsread 2 September 2026
Video

بدترین رسلر جهان ❤️ خ مرد و تو هنوز آدم نشدی

22👍4

15 Feb 2026, 20:14 UTC≈2,800 views37 reactionsread 2 September 2026
Video

Video, posted without a caption

36🔥1

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

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.

WrestlingCity | رسلینگ سیتی
@wcityir · 35,695
Telegram ranks this channel #19 of 68 here — alongside 67 others — read 2 September 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“ʀᴀᴘᴛᴏʀ ᴡʀᴇsᴛʟɪɴɢ | رپتور رسلینگ” (@RAPTOR_WRESTLING), 1,299 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/RAPTOR_WRESTLING.

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.