Channel
@eduvtatarstan
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
40,267subscribers
+71 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001132874616 |
|---|---|
| Type | Channel |
| Username | @eduvtatarstan |
| Description | Наши сплетни - наша отрада. Новости Татарстана. Новости Казани. Мемы про Татарстан. Реестр РКН: https://clck.ru/3GWofx Наш бот для обратной связи @EduvTatarstanNews_bot Канал с лонгридами: @et_longread Рейтинги: @toptatarstan #LF1WA |
| Created | 30 September 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 | 9 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/eduvtatarstan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:33 | 40,267 | -6 |
| 11 Aug 2026, 10:32 | 40,273 | +76 |
| 10 Aug 2026, 07:11 | 40,197 | -12 |
| 9 Aug 2026, 06:43 | 40,209 | +7 |
| 8 Aug 2026, 04:35 | 40,202 | +17 |
| 7 Aug 2026, 07:39 | 40,185 | -4 |
| 6 Aug 2026, 06:50 | 40,189 | -7 |
| 6 Aug 2026, 01:48 | 40,196 | no change |
| 5 Aug 2026, 23:03 | 40,196 | first reading |
153 posts held, back to 31 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 18 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 142 of 153 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 153 (31 July 2026 – 13 August 2026) |
| Views total | 387,483 |
| Reactions total | 1,325 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 09:03 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.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 21 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.
1,200 reactions across 121 posts, in 8 distinct kinds. The most used accounts for 31.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 372 | 31.0% | |
| 😱 | 265 | 22.1% | |
| ❤ | 193 | 16.1% | |
| 👍 | 139 | 11.6% | |
| 💩 | 113 | 9.42% | |
| 👎 | 61 | 5.08% | |
| custom 5220113606724557083 | 42 | 3.50% | |
| custom 5316825730380733425 | 15 | 1.25% |
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 142 of the 153 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 1,325reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 153 most recent posts we hold, published 31 July 2026 to 13 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.
Пожилая женщина в Уфе попыталась столкнуть промышленного альпиниста. 🔸Альпинисты Рафаэль и его напарник приехали утеплять фасад. Обычно люди благодарны за работу и угощают чаем с печеньем, но в этот раз женщина проявила агрессию. «Я вас не нанимала!» — заявила она. Мы в MАХ
😱7👍1
Posted without readable text
наконец-то нормальные услуги пошли Мы в MАХ
😁9
В Башкортостане после атаки БПЛА загорелся объект Wildberries 🔸В промзоне Салавата после падения обломков беспилотника произошло возгорание. На объекте хранения товаров не было. Заблаговременная эвакуация прошла в соответствии с требованиями безопасности. На месте работают пожарные расчёты. Возгорание локализуют. Мы в MАХ
👍3
Финансовую помощь семьям погибших и пострадавшим в Нижнекамске удвоят 🔸Мэр Нижнекамска Радмир Беляев сообщил, что предприятия Нижнекамска, где работали семьи жертв и пострадавших, дополнительно поддержат: Семьи погибших — по 2 млн рублей Пострадавшим — по 600 тыс. рублей (при тяжёлом/среднем вреде здоровья) и по 300 тыс. рублей (при лёгком вреде) Предприятие, где работала мама погибшей девочки, выделит 2 млн рубле…
custom 53168257303807334252
Беспилотная опасность в РТ отменена. Придется на работу ехать Мы в MАХ
😁3👍1
Министерство обороны РФ: В течение прошедшей ночи с 20.00 мск 12 августа до 8.00 мск 13 августа дежурными средствами ПВО перехвачены и уничтожены 362 украинских беспилотных летательных аппарата самолетного типа над территориями Белгородской, Брянской, Воронежской, Калужской, Курской, Оренбургской, Орловской, Пензенской, Ростовской, Рязанской, Самарской, Тульской, Ульяновской областей, Московского региона, Республики…
❤2
Угроза атаки на Альметьевск, Заинск, Лениногорск отменена. Беспилотный режим в Татарстане сохраняется. Мы в MАХ
😁1😱1
Объявлена угроза атаки бпла на города республики Мы в МАХ
😁1😱1
Редакция «Еду в Татарстан» выбралась сегодня за город на охоту за метеорным потоком Персеиды и рада вам представить результаты охоты. Зажигается и падает прям много, Млечный Путь за городом тоже видно, фотографии не врут. Мы в MАХ
👍19❤9custom 52201136067245570837😁1
друзья, это видео для вас, если вы пропустили солнечное затмение Мы в МАХ
😁40❤4😱1custom 52201136067245570831
это смешно, субханаЛлах Дети ворвались в комментаторскую кабинку во время футбольного матча второй лиги Казахстана. Мы в МАХ
😁11❤2custom 52201136067245570831
Showing the 12 most recent of 153 posts we hold for @eduvtatarstan. 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.
@eduvtatarstan edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 26,686 of 1,160,990entries 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 18 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Еду в Татарстан” (@eduvtatarstan), 40,267 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/eduvtatarstan.
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.