❗️ Продажа Оригинал Цена : 1.3к rub (успейте купить, в будущем цена будет больше!) По поводу покупки писать : @Fruitelo
custom 53549025095403707982custom 51792608055179365931

Channel
@reteX1337
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
420subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002567701585 |
|---|---|
| Type | Channel |
| Username | @reteX1337 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/reteX1337 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 07:24 | 420 | no change |
| 13 Aug 2026, 18:04 | 420 | first reading |
17 posts held, back to 2 April 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 15 April 2026. An engagement rate over an empty window would be a number about nothing.
78 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 26.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5370800197842531315 | 21 | 26.9% | |
| custom 5354902509540370798 | 17 | 21.8% | |
| custom 5179260805517936593 | 14 | 17.9% | |
| custom 5332534212488600921 | 12 | 15.4% | |
| custom 5319309548622722932 | 6 | 7.69% | |
| custom 5280518782689762328 | 5 | 6.41% | |
| custom 5292226786229236118 | 2 | 2.56% | |
| custom 5253499779085783568 | 1 | 1.28% |
Custom emoji. Every row above is a 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 17 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 78reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 2 April 2026 to 15 April 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.
❗️ Продажа Оригинал Цена : 1.3к rub (успейте купить, в будущем цена будет больше!) По поводу покупки писать : @Fruitelo
custom 53549025095403707982custom 51792608055179365931
Мы в поисках +2 игроков в основной состав на ближайшие турниры ( от дабл леги 10 сезон ) писать в лс @russiagods
custom 52805187826897623283custom 53193095486227229321
Турнир от Pahan Organisation На 16 команд Регистрации отправлять в лс: @PahanTyrik Что должно быть в регистрации: 1. Тег клана 2. Основной состав и замена (айди+ники) 3. Юз капитана Обезательно 5 игрокам команды нужно быть подписаным на: https://t.me/PahanORG https://t.me/reteX1337 иначе не приму на турнир! Игры на турнире будут стримиться на твиче: https://www.twitch.tv/pahanorg
custom 53708001978425313155custom 51792608055179365931
❗️В наличии имеется интересный фан тег "tgGOD" 10 мест Что вы получаете после его приобретения : • Узнаваемость • Красивый тег с возможностью его развития Цена : 900G / 700р (могут быть исключения) ЛС @solinoyk
custom 53325342124886009213custom 52534997790857835681custom 53549025095403707981
Передумали, тгк не продается
custom 53549025095403707985
Приз за финал нам выдали ❗ Организатору респект за быстрый вывод приза, + ждём оформление для тгк на сумму 300г. Советую принимать участие у него на турнирах, его юз : @Confeety Ждём инвайт на следующий турнир)
custom 53708001978425313156
🥳 Нам ровно год ❗️ Сегодня ровно 1 год и 1 день как существует клан BlackSpaces eSports [ reteX ]. За такой большой промежуток времени в клане очень многое поменялось, у нас побывало очень много людей, как на долговременном присутствии так и те кто был у нас лишь пару дней. На данный момент у нас есть минимум 10 человек которые с нами уже более 5 месяцев, стали друг другу очень хорошими друзьями, это те люди на ко…
custom 51792608055179365935
Победа ❗ Выигрываем финал Royal Tournament ! На карте Провинция ребята поставили не правильный формат и пришлось играть до 10 раундов, мы эту карту давненько не играли поэтому было немного трудновато. Но не смотря на то что это далеко не наша любимая карта мы ее забираем со счетом 10:8 и переходим на наш пик : Раст Играя карту раст мы абсолютно все держали под контролем, уходили на т сторону со счетом 11:1 в нашу п…
custom 53708001978425313156custom 51792608055179365934custom 53549025095403707982custom 53325342124886009211
Сегодня в 18:30 играем финал турнира Royal Tournament в 18:30 МСК Оппонент : NLL77 Время : 18:30 Формат : Мр12 БО3 Карты : Province | KT, Rust | KT, Dune | KT Желаем противникам удачи, победит сильнейший !
custom 53325342124886009213
Финальная игра уже совсем скоро, мы готовы побеждать. Ставьте "🔥" под постом организаторов турнира. Поддержите нашу команду ! Спасибо!
custom 53325342124886009214custom 53193095486227229322
🏆ФИНАЛ турнира Royale Tournament S2 Финальная точка сезона будет поставлена уже совсем скоро. 🔴 reteX vs NLL77 Один матч. Один чемпион. Главный поединок всего Royale Tournament ❤️ — NLL77 🔥 — reteX 💬 — кто станет чемпионом?
custom 53708001978425313154custom 51792608055179365932custom 53549025095403707981
Как вам новое обновление в нашей игре? Напишите в комментариях ваше впечатление. ❤️
custom 53549025095403707983
Showing the 12 most recent of 17 posts we hold for @reteX1337. 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,184,053 of 1,340,412entries 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.
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.
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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“reteX I BlackSpaces eSports” (@reteX1337), 420 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/reteX1337.
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.