Channel
@r2d2sakh
On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,642subscribers
+20 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001201908516 |
|---|---|
| Type | Channel |
| Username | @r2d2sakh |
| Created | 23 November 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/r2d2sakh |
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 20:48 | 3,642 | +16 |
| 9 Aug 2026, 19:31 | 3,626 | +3 |
| 6 Aug 2026, 12:40 | 3,623 | +1 |
| 6 Aug 2026, 06:01 | 3,622 | no change |
| 6 Aug 2026, 05:55 | 3,622 | first reading |
25 posts held, back to 4 August 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 3 pagesof 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. It is computed over the 3 of 25 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 25 (4 August 2026 – 7 August 2026) |
| Views total | 5,270 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 22:59 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.
Measured directly from 3 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.
6 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 100.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 3 of the 25 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 18reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 4 August 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.
А там ехать нормально по полосе невозможно. Раньше корсаковская трасса была "образцом", однако после объявления её реконструкции на содержание забили огромный болт и латают только любимые трещинки. И получается так, что люди, проехавшие всю страну, отзываются о её качестве грубо и с матами, т.к. не помнят дороги хуже, чем в одной из богатых областей России... И все это, видимо, тоже благодаря губернатору Сахалинской …
👍6
#вточкупишут, что на въезде в Корсаков жёстко столкнулись два внедорожника. ДТП произошло днём 7 августа, оба автомобиля получили механические повреждения. "У одного морды нет, у второго правый бок разбит. Судя по всему, "Лэнд Крузер 80" выезжал и попал под удар "Прадика", - предположил информатор. О пострадавших не сообщается. ✉️ Прислать новость 😄 Подписывайся на нас: МАХ | Telegram | WhatsApp | ВК
👮♀️Госавтоинспекция продолжает профилактические мероприятия по пресечению нарушений в области средств индивидуальной мобильности. Сотрудники Госавтоинспекции активно осуществляют профилактические мероприятия, направленные на предотвращение нарушений правил дорожного движения, связанных с использованием средств индивидуальной мобильности (СИМ). В ходе рейдов особое внимание уделяется таким нарушениям, как движение п…
👮♀️Сводка Госавтоинспекции за 06 августа 2026 года 🏳За прошедшие сутки в Сахалинской области зарегистрировано 1 ДТП с пострадавшими. 👮♂️Сотрудниками Госавтоинспекции при проведении профилактических мероприятий пресечено 141 нарушение ПДД РФ: 🗣Задержаны и отстранены от управления ТС 5 водителей, которые сели за руль в состоянии опьянения. 👮♂️Кроме этого, задержаны 11 водителей, которые не имеют права управления…
@ysakhalinsk Может хотя бы ямочный? До осени как раз развалится и можно будет еще пару раз закатать осенью и весной.
https://t.me/avt0chat/418957
🛑🛑🛑 в Поронайском районе 06 августа 2026 года в 04 часа 50 минут на автодороге "Южно-Сахалинск-Оха" км324+900 произошло дорожно-транспортное происшествие. По предварительным данным, 54-летний водитель "Toyota Caldina", двигаясь в южном направлении, совершил столкновение со стоящим на обочине прицепом, с последующим опрокидываем. В результате ДТП 54-х летний водитель и 65-летний пассажир скончались на месте происше…
@ysakhalinsk А остаток Буюклы когда? От Мира до Дзержинского все в дырах.
⛔️ В эти выходные на участке пр. Мира частично ограничат движение транспорта Это связано с продолжением работ по обновлению улично-дорожной сети. Ремонт затронет участок от ул. Тихоокеанской до ул. Буюклы. Работы будут проводиться поэтапно: 🔘в первой половине дня (8 и 9 августа) будет перекрыта правая сторона проезжей части; 🔘во второй половине дня (8 и 9 августа) будет перекрыта левая сторона проезжей части. На …
🛑🛑🛑 в Холмском районе 05 августа 2026 года в 23 часа в районе дома N1 ,по улице Обрывной, села Правда произошло дорожно-транспортное происшествие. По предварительным данным, 41-летний водитель "Toyota Probox", двигаясь в южном направлении, совершил наезд на препятствие, в виде бордюрного камня, с последующим опрокидыванием транспортного средства. В момент опрокидывания, водитель выпал из автомобиля и его придавило …
⚡️"Жёстко влетел в бочину": автомобилист попал в ДТП, уходя от полицейской погони в Южно-Сахалинске В Дальнем Toyota Chaser попал в жёсткое ДТП, пытаясь уйти от полицейской погони, сообщил “Точке отсчёта” очевидец. По предварительным данным, водитель иномарки влетел в машину, которая в этот момент совершала поворот. Местные жители передают, что за Toyota Chaser по Холмскому шоссе ехали два экипажа ГАИ. "Белая ином…
🛑🛑🛑 в Южно-Сахалинске 05 августа 2026 года в 14 часов 00 минут в районе дома N12 по улице Вокзальной произошло дорожно-транспортное происшествие. По предварительным данным, 55-летний водитель "Nissan March", двигаясь в южном направлении, совершил наезд на двух несовершеннолетних пользователей средств индивидуальной мобильности, которые пересекали проезжую часть не спешившись, по нерегулируемому пешеходному переход…
Showing the 12 most recent of 25 posts we hold for @r2d2sakh. 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 — 891,846 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Автомобильный Сахалин” (@r2d2sakh), 3,642 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/r2d2sakh.
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.