Channel
@Rabcelonaa
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
402subscribers
+37 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003853650564 |
|---|---|
| Type | Channel |
| Username | @Rabcelonaa |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/Rabcelonaa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 04:18 | 402 | +37 |
| 8 Aug 2026, 06:31 | 365 | no change |
| 7 Aug 2026, 19:03 | 365 | first reading |
16 posts held, back to 14 July 2026 — 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 16 (14 July 2026 – 5 August 2026) |
| Views total | 2,689 |
| Reactions total | 302 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:31 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.
686 reactions across 16 posts, in 23 distinct kinds. The most used accounts for 32.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5343687555361572095 | 220 | 32.1% | |
| 💊 | 65 | 9.48% | |
| custom 5233391644149058665 | 58 | 8.45% | |
| custom 5229113770822898162 | 46 | 6.71% | |
| custom 5199602453531627007 | 44 | 6.41% | |
| custom 5285093949357205206 | 40 | 5.83% | |
| custom 5400024727282553042 | 31 | 4.52% | |
| custom 5449836731484381624 | 26 | 3.79% | |
| custom 5467471059747894557 | 23 | 3.35% | |
| ❤🔥 | 21 | 3.06% | |
| 🤣 | 19 | 2.77% | |
| custom 5341304260829154511 | 18 | 2.62% | |
| 🔥 | 15 | 2.19% | |
| 😭 | 15 | 2.19% | |
| custom 5258195449650645384 | 14 | 2.04% | |
| 🏆 | 14 | 2.04% | |
| ❤ | 5 | 0.729% | |
| custom 5341509246733289717 | 4 | 0.583% | |
| custom 5386450496028448222 | 4 | 0.583% | |
| custom 5231266790683741046 | 1 | 0.146% | |
| 3 further kinds | 3 | 0.437% |
Custom emoji. 13 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 16 of the 16 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 686reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 14 July 2026 to 5 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.
😆 Топ-5 вратарей Варсы Ставь <<🏳️🌈>> Если все игроки варсы инвалиды
custom 519960245353162700744💊5custom 52333916441490586654🤣3custom 53436875553615720952🗿1custom 52312667906837410461
🏳️🌈🏳️🌈 Пидоры однажды - Пидоры навсегда! Ставь <<🏳️🌈>> если Барса клуб Геев
custom 534368755536157209560custom 52333916441490586657custom 52581954496506453847💊4🤣3
Альварес не перейдёт в клуб Пидорасов Ставьте <<🏳️🌈>> Если Альварес ебырь Гейселоны
custom 534368755536157209581💊10custom 52333916441490586656custom 52581954496506453844
Ебырь Рабселоны
custom 523339164414905866540💊8custom 53436875553615720956🤣3custom 52581954496506453843
Ожидается новый ебырь Варсы
custom 534368755536157209537custom 52291137708228981628🏆7💊5custom 53413042608291545113⚡1
Состав Варгентины
custom 522911377082289816237🏆7custom 53413042608291545114💊1
Ебырь Варсы прибыл
custom 534368755536157209526custom 53413042608291545119💊3custom 53415092467332897172
Вариспания еле еле как выигрывает
💊19custom 53436875553615720958🤣4custom 53413042608291545112custom 53415092467332897172
Франция вылетает с ЧМ. Сыграем матч за 3 место против Аргентины или Англии.
😭15🤣6custom 52291137708228981621
Разминка 🇫🇷
custom 546747105974789455713custom 52850939493572052064custom 54000247272825530422💊1
🇫🇷Тчуамени прибыл на стадион
custom 540002472728255304213custom 54674710597478945575custom 52850939493572052064❤1💊1
🇫🇷 СОСТАВ ФРАНЦИИ! Тчуамени - ✔️
custom 544983673148438162419custom 52850939493572052065custom 53864504960284482224💊2❤🔥1
Showing the 12 most recent of 16 posts we hold for @Rabcelonaa. 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.
Citation-graph rank — 1,385,223 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Все о Рабселоне” (@Rabcelonaa), 402 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Rabcelonaa.
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.