Telegram RegisterThe public register of Telegram

Channel

CARVILLE RACING

@carvilleracing

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

5,698subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001740947402
TypeChannel
Username@carvilleracing
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/carvilleracing

Growth

5,6895,6985,693.57 August 2026 — 5,697 subscribers7 August 2026 — 5,691 subscribers10 August 2026 — 5,689 subscribers13 August 2026 — 5,698 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net +1. 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 5,688–5,699 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:465,698+9
10 Aug 2026, 17:335,689-2
7 Aug 2026, 14:315,691-6
7 Aug 2026, 03:005,697first reading

Engagement

14 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
36.2%
avg views ÷ 5,698 subscribers
Avg views / post
2,060
14 posts measured
Reaction rate
0.907%
reactions ÷ views · ER floor
Posts in window
14
of 14 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 8 August 2026
Posts held14 (2 August 20268 August 2026)
Views total28,892
Reactions total262
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:57 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
7m 06s
Average length
1m 01s

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

262 reactions across 14 posts, in 12 distinct kinds. The most used accounts for 36.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9536.3%
6223.7%
👏2810.7%
134.96%
💔124.58%
😢114.20%
🏆93.44%
😭93.44%
custom 524017591436025077183.05%
🎉62.29%
😨51.91%
custom 523332218164297207141.53%

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

Measured over the 14 most recent posts we hold, published 2 August 2026 to 8 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

8 Aug 2026, 08:11 UTC469 views34 reactionsread 12 August 2026
Forwarded from @forsazh_youtubePhoto

Такие дела! Ждём в Минске 15-16 Августа 🚀

🔥2472custom 52333221816429720711

8 Aug 2026, 08:10 UTC≈21,700 views28 reactionsread 12 August 2026
Photo

В середине августа немного отступим от привычного гоночного календаря и отправимся в Минск на RDS Open 💫 15 и 16 августа за нашу команду на старт выйдет Ваня Пальмин, а компанию ему составит Антон Скрыпников. И это уже хороший повод внимательно следить за этапом, тем более что компания на трассе собирается серьёзная. В Минске встретятся пилоты из России и Беларуси, а также спортсмены из Японии 👀 Особенным будет и с

🔥155😨51😢1custom 52333221816429720711

6 Aug 2026, 08:33 UTC618 views19 reactionsread 12 August 2026
Photo

Жаааркий сибирский этап позади, но отпускать его пока совсем не хочется ☀️ Поэтому мы собрали всё самое яркое в одном месте: на сайте уже появился пресс-релиз, а в группе ВК загрузили большую подборку фотографий с «Красного Кольца». Можно ещё раз вернуться в этот уикенд, вспомнить плотные постановки, дымные проезды и ту самую внутрикомандную борьбу, которая в итоге привела нас к личному и командному подиуму 🏆 Загля

107custom 52401759143602507712

2 Aug 2026, 13:13 UTC≈1,000 views35 reactionsread 12 August 2026
Video

Финальное слово после этапа за директором команды. Ваня Пальмин подводит итоги уикенда на Красном Кольце ☀️ Ваня рассказал про выступление ребят, вспомнил самые яркие парные заезды, поделился своими эмоциями и признался, что, похоже, наконец-то расколдовал свою супру… А мы возвращаемся домой готовиться к финальному этапу на Moscow Raceway #CarvilleRacingTeam

🔥188👏6custom 52401759143602507712🏆1

2 Aug 2026, 11:31 UTC825 views18 reactionsread 12 August 2026
Video

Что решило исход полуфинала? И каково это бороться за место на пьедестале с сокомандником? Антон разбирает заезд с Владиславом Поповым и рассказывает о внутрикомандном дерби с Ваней 📣 #CarvilleRacingTeam

7👏5🏆4🔥2

2 Aug 2026, 10:53 UTC≈1,050 views26 reactionsread 12 August 2026
Video

🏁 Финишируем 5-й этап RDS GP на «Красном кольце» с двумя наградами! 🥉 Антон Козлов — бронзовый призёр этапа 🥈 Серебро командного зачёта — наше Спасибо всем, кто был с нами на трибунах и поддерживал у экранов. Впереди финальный этап сезона. Увидимся там🧡 #CarvilleRacingTeam

🔥154👏4🎉3

2 Aug 2026, 10:17 UTC551 views17 reactionsread 12 August 2026
Video message

Video message, posted without a caption

🔥86🎉3

2 Aug 2026, 09:35 UTC456 views17 reactionsread 12 August 2026
Forwarded from @russiandriftseriesPhoto

🥉🎉 Бронзовый призер 5 этапа Гран-при РДС 2026 — пилот команды Carville Racing Антон Козлов! Поздравляем! Не пропустите ФИНАЛ: rdstv.ru/catalog/140084/ 📊 Сетка и результаты 📝 Текстовая трансляция

👏106custom 52401759143602507711

2 Aug 2026, 09:34 UTC338 views14 reactionsread 12 August 2026
Forwarded from @rdsgp_live

Антон Козлов — 3-е место на пятом этапе Гран-При Российской Дрифт Серии сезона 2026 года на «Красном кольце»!

🔥85custom 52401759143602507711

2 Aug 2026, 09:32 UTC399 views1 reactionsread 12 August 2026
Video message

Video message, posted without a caption

1

2 Aug 2026, 09:32 UTC392 views9 reactionsread 12 August 2026
Video

Хит за третье место на предпоследнем 5 этапе RDS GP сезона 2026 в Красноярске🏆

👏3💔3custom 524017591436025077121

2 Aug 2026, 09:24 UTC316 views15 reactionsread 8 August 2026
Video

🔤🔤4️⃣ Ваня уступает Сергею Кузнецову и отправляется в заезд за третье место, где встретится с сокомандником Антоном 👀

💔7😢5🏆21

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

Citation-graph rank — 4,517 of 1,350,102entries 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.

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

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

“CARVILLE RACING” (@carvilleracing), 5,698 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/carvilleracing.

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.