Telegram RegisterThe public register of Telegram

Channel

SHISHKOIL Racing Team

@shishkoil

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

547subscribers

+0 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-1002352285827
TypeChannel
Username@shishkoil
DescriptionРоссийская гоночная команда SHISHKOIL Racing Team 🏆 Чемпионы Кубка России 2024 года 🏅 Победы в GT Pro и GT Pro Touring | REC | СМП РСКГ VK: https://vk.com/shishkoilracingteam Inst: @shishkoil_rt
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/shishkoil

Growth

5477 Aug 2026, 17:37 — 547 subscribers8 Aug 2026, 03:46 — 547 subscribers7 Aug 2026, 17:378 Aug 2026, 03:46
2 measurements taken within a single day. 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 546–548 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 03:46547no change
7 Aug 2026, 17:37547first reading

Engagement

10 posts held, back to 24 June 2026the 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 · 30 days
37.2%
avg views ÷ 547 subscribers
Avg views / post
204
6 posts measured
Reaction rate
6.80%
reactions ÷ views · ER floor
Posts in window
6
of 10 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 7 August 2026
Posts held10 (24 June 20267 August 2026)
Views total1,221
Reactions total83
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:46 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

Photos
284
Videos
39
Links
76

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

159 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 32.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5132.1%
👍4125.8%
🔥3924.5%
❤‍🔥138.18%
🍾63.77%
custom 546998629138065775931.89%
custom 528073585892682298721.26%
💘21.26%
🤩21.26%

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

Measured over the 10 most recent posts we hold, published 24 June 2026 to 7 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

7 Aug 2026, 05:21 UTC106 views13 reactionsread 8 August 2026
Photo

Как и обещали – делимся расписанием! Уже 8 и 9 августа на «Игора Драйв» пройдёт III этап SMP GT4 Russia. Нас ждут два дня борьбы: сегодня состоятся две квалификации, а в субботу и воскресенье – по одной гонке. Наш экипаж SHISHKOIL by CapitalRT №12: 🏎 Mercedes AMG GT4 • Дмитрий Шишко • Пётр Плотников РАСПИСАНИЕ ГОНОЧНОГО УИКЕНДА: 📅 8 августа • 14:00 - 14:35 – Прогулка зрителей по пит-лейну • 14:45 - 14:55 – Про

7👍3🔥3

6 Aug 2026, 09:05 UTC128 views16 reactionsread 8 August 2026
Photo

Несмотря ни на что продолжаем бороться! В субботу, 1 августа, на Moscow Raceway прошёл IV этап REC Гран-При Авторадио. Для SHISHKOIL RT этот гоночный день получился непростым, но насыщенным на события. Технические сложности начались ещё в квалификации. А в середине четырёхчасовой гонки наш Mercedes AMG GT4 был вынужден заехать в боксы из-за поломки ступицы. Команда оперативно устранила неисправность, и экипаж верну

👍9❤‍🔥52

30 Jul 2026, 07:31 UTC222 views9 reactionsread 8 August 2026
Photo

⏳Обратный отсчёт пошёл! До IV этапа REC Гран-При Авторадио остаётся всего два дня. Уже 1 августа SHISHKOIL RT вновь выйдет на старт на автодроме «Moscow Raceway». 🔥 Класс GT | Mercedes AMG GT4 Наш состав на гонку: ❤️Дмитрий Шишко ❤️Алексей Савин ❤️Артём Слуцкий Старт 4-часовой гонки – в 17:00. Полное расписание гоночного дня смотрите на фото🧡 А ещё организаторы подготовили приятный сюрприз для зрителей. Росс

3custom 54699862913806577593❤‍🔥2🤩1

29 Jul 2026, 12:05 UTC212 views12 reactionsread 8 August 2026
Photo

Финишировали на диске 🛞 Пока мы готовимся к IV этапу REC Гран-При Авторадио, вспомним, как прошла гонка «1000 км Игора Драйв», которая состоялась 18 июля в рамках Garage Fest. Эта гонка стала настоящей проверкой на прочность... Наш экипаж — Дмитрий Шишко, Алексей Савин, Пётр Бирюков и Артём Слуцкий — уверенно начал гоночный день. Несмотря на небольшие технические сложности в первой части дистанции, команда не потер

4👍3🔥3❤‍🔥2

18 Jul 2026, 08:10 UTC298 views23 reactionsread 8 August 2026
Photo

Борьба только начинается 👊🏻 На «Игора Драйв» уже стартовала первая часть гонки «1000 км Игора Драйв» в рамках Garage Fest 2026. ⏱️Наш экипаж отлично начал гоночный день, показав лучшее время в квалификации класса Туринг. Теперь впереди самое главное — длинная дистанция и борьба за результат. Для тех, кто сейчас на автодроме: с 11:40 можно будет прогуляться по пит-лейну, заглянуть в боксы и пообщаться с нашими пило

🔥107❤‍🔥4👍2

16 Jul 2026, 13:33 UTC255 views10 reactionsread 8 August 2026
Photo

Встречаемся на GARAGE FEST! 🔥 18 и 19 июля автодром «Игора Драйв» вновь станет центром большого автомобильного праздника. ГАРАЖ ФЕСТ – это два дня скорости, музыки и атмосферы, где каждый найдёт что-то для себя. И, конечно, наша команда SHISHKOIL RT не останется в стороне 😉 Главным событием первого дня станет уникальная гонка на выносливость «1000 км Игора Драйв». Впервые в истории российского автоспорта пилотам пр

👍43🔥3

13 Jul 2026, 11:31 UTC279 views19 reactionsread 8 August 2026
Photo

Гран-При Санкт-Петербурга: как это было 🏎 В субботу на автодроме «Игора Драйв» состоялся III этап REC Гран-При Санкт-Петербурга. Гонка выдалась насыщенной: частые режимы жёлтых флагов, плотная борьба и даже возгорание автомобиля одного из участников (никто не пострадал!). К счастью, гроза, которая накрыла Санкт-Петербург, обошла трассу стороной, и гонку удалось провести без погодных сюрпризов⛅️ По итогам квалификац

8👍6🔥2custom 52807358589268229872💘1

9 Jul 2026, 14:20 UTC310 views17 reactionsread 8 August 2026
Photo

Встречаемся на «Игора Драйв»! 11 июля SHISHKOIL RT выходит на старт III этапа REC Гран-При Санкт-Петербурга. И, судя по прогнозу, жарко будет не только на улице, но и на трассе 🔥 После успешного дебюта в классе TCE на прошлом этапе REC мы выходим на старт в привычном для нас классе GT! Экипаж №1 – Дмитрий Шишко и Алексей Савин – снова сядет за руль Mercedes AMG GT4 и продолжит борьбу в чемпионате. ⏰ Старт 4-часово

7👍6🔥3💘1

1 Jul 2026, 18:00 UTC364 views25 reactionsread 8 August 2026
Photo

Новый класс — и сразу победа!🥇 Второй этап REC Гран‑При Спортса" стал по‑настоящему запоминающимся для SHISHKOIL RT. Дебют в классе TCE получился ярким: наш экипаж показал лучшее время в квалификации и стартовал с первой позиции 😎 Напоминаем, за рулём Audi RS3 LMS в этот день выступали Дмитрий Шишко, Артём и Захар Слуцкие, а также Пётр Бирюков. Начало гонки выдалось непростым. Из‑за скользкого асфальта и ещё не пр

🔥117🍾6👍1

24 Jun 2026, 10:35 UTC349 views15 reactionsread 8 August 2026
Photo

27 июня. Moscow Raceway. II этап REC. Уже в эту субботу Дмитрий Шишко, Артём и Захар Слуцкие выйдут на старт второго этапа гонок на выносливость – Гран-При Спортса" Russian Endurance Challenge. 📌 Знакомимся с расписанием на день: 🧳11:30 - 14:30 – Тренировки-квалификации 🧳14:30 – Открытие входа для зрителей 🧳14:45 - 16:45 – Прогулка по пит-лейн 🧳17:00 - 17:50 – Предстартовая процедура 🧳18:00 - 22:00 – Гонка Гран-Пр

👍7🔥43🤩1

Showing the 10 most recent of 10 posts we hold for @shishkoil. 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 — 500,508 of 1,189,255entries 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.

Mentions

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.

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

“SHISHKOIL Racing Team” (@shishkoil), 547 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/shishkoil.

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.