Telegram RegisterThe public register of Telegram
Telegram profile photo for (RR) Rodeo Racing Game

Channel

(RR) Rodeo Racing Game

@RodeoRacing

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

112subscribers

+8 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-1003997267106
TypeChannel
Username@RodeoRacing
Created8 July 2026 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/RodeoRacing

Topic

Gaming — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

104117110.57 August 2026 — 104 subscribers9 August 2026 — 104 subscribers16 August 2026 — 105 subscribers23 August 2026 — 111 subscribers30 August 2026 — 117 subscribers16 September 2026 — 112 subscribers1127 August 202616 September 2026
6 measurements spanning 40 days, net +8. 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 102–119 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 14:40112-5
30 Aug 2026, 01:52117+6
23 Aug 2026, 15:03111+6
16 Aug 2026, 21:33105+1
9 Aug 2026, 09:31104no change
7 Aug 2026, 22:02104first reading

Engagement

5 posts held, back to 8 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 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 5 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

17 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤17100.0%

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 5 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 8 July 2026 to 4 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

4 Aug 2026, 09:26 UTC109 views6 reactionsread 9 August 2026
Photo

🔧 Обновление баланса: турель Теперь даже если на протяжении всей игры вам выпадают в основном карточки ремонта, их можно использовать для атаки. Соберите любые три зелёные карточки из карточек ремонта: «Ремонт тормозов» «Ремонт подвески» «Ремонт двигателя» «Ремонт КПП» «Замена колес» Обменяйте их на три детали турели: основание, поворотный механизм и пушку. После сборки турель автоматически начинает атаковать сопе…

❤6

30 Jul 2026, 08:30 UTC234 views6 reactionsread 9 August 2026
Photo

🏁 ОБНОВЛЕНИЕ — ЧЕМПИОНАТ НЕДЕЛИ! Теперь каждую неделю среди гонщиков Racing Rodeo проходит новый чемпионат! Участвуйте в кольцевых гонках, зарабатывайте очки и поднимайтесь в таблице лидеров. Победителем станет гонщик, который к концу недели наберёт больше всего очков. 🏆 Награда чемпиону недели: - 500 золотых монет - Эксклюзивная карта автомобиля редкости Racing или Racing Sport Новая неделя — новый чемпионат и но…

❤6

14 Jul 2026, 19:15 UTC≈1,010 views0 reactionsread 9 August 2026
Photo

🐞 Racing Rodeo только запустилась! Сейчас игра находится на раннем этапе. Мы специально не добавляли монетизацию, потому что сначала хотим получить честную обратную связь и понять, насколько игра интересная, понятная и стабильная. Будем благодарны, если вы расскажете: — какие баги или ошибки заметили; — что показалось непонятным или неудобным; — понравились ли гонки и карточная механика; — чего, по вашему мнению, н…

14 Jul 2026, 06:30 UTC899 views5 reactionsread 9 August 2026
Photo

🏁 Добро пожаловать в Racing Rodeo Мы создаём автомобильную карточную игру прямо внутри Telegram. Здесь побеждает не просто самая быстрая машина. Важно учитывать её характеристики, погоду, состояние автомобиля и правильно использовать карты во время гонки. В Racing Rodeo вас ждут: 🏎 коллекционирование автомобилей 🛠 тюнинг и установка запчастей 🃏 карточная система боя ⚔️ гонки против других игроков 🏆 рейтинги, сезон…

❤5

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

Mentions

Named by 2 registered channels — 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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“(RR) Rodeo Racing Game” (@RodeoRacing), 112 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/RodeoRacing.

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.