Channel
@topor
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,295,579subscribers
+858 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001288489154 |
|---|---|
| Type | Channel |
| Username | @topor |
| Description | Новости присылать сюда: @Toporchan_Bot Наш канал без цензуры 18+: https://t.me/joinchat/ScL1FOCgJCbFNJK1 Live канал: https://t.me/+n0B2XbLYjbMwMDEy По всем вопросам @toporch |
| Created | 20 November 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/topor |
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 69% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 4 other registered channels. They sit inside a group of 377 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @topor/51649 · this entry6 Aug 2026, 09:06 UTC | @nasrat_news/397716 Aug 2026, 09:06 UTC | 1.00 | under a minute |
| @topor/51650 · this entry6 Aug 2026, 10:01 UTC | @nasrat_news/397726 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @topor/51656 · this entry6 Aug 2026, 16:11 UTC | @nasrat_news/397786 Aug 2026, 16:12 UTC | 1.00 | 2 minutes |
| @topor/51663 · this entry7 Aug 2026, 07:32 UTC | @nasrat_news/397857 Aug 2026, 07:34 UTC | 1.00 | 72 seconds |
| @topor/51664 · this entry7 Aug 2026, 08:51 UTC | @nasrat_news/397867 Aug 2026, 08:53 UTC | 1.00 | 2 minutes |
| @topor/51665 · this entry7 Aug 2026, 10:09 UTC | @nasrat_news/397877 Aug 2026, 10:10 UTC | 1.00 | 72 seconds |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @nasrat_news | 27 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (27–0) |
| @toporlive | 11 (8/8 hand-verifiable sample passed) | 1.00 | 8 minutes | @toporlive (6–5) |
| @chto_pro1shodit | 11 (8/8 hand-verifiable sample passed) | 1.00 | 16 hours | this entry (11–0) |
| @novostniklaif | 9 (8/8 hand-verifiable sample passed) | 1.00 | 71 minutes | this entry (9–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 2,751 comparable posts for this entry, running 29 October 2025 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 376 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.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 07:41 | 1,295,579 | -31 |
| 4 Sept 2026, 02:16 | 1,295,610 | -4 |
| 2 Sept 2026, 16:24 | 1,295,614 | +88 |
| 1 Sept 2026, 18:34 | 1,295,526 | -93 |
| 31 Aug 2026, 19:57 | 1,295,619 | -12 |
| 30 Aug 2026, 20:24 | 1,295,631 | +3 |
| 29 Aug 2026, 23:14 | 1,295,628 | +80 |
| 29 Aug 2026, 02:16 | 1,295,548 | -131 |
| 28 Aug 2026, 00:24 | 1,295,679 | +80 |
| 27 Aug 2026, 01:54 | 1,295,599 | +20 |
| 26 Aug 2026, 05:27 | 1,295,579 | -78 |
| 25 Aug 2026, 04:13 | 1,295,657 | -279 |
| 24 Aug 2026, 01:17 | 1,295,936 | +261 |
| 22 Aug 2026, 09:47 | 1,295,675 | +496 |
| 21 Aug 2026, 00:37 | 1,295,179 | +472 |
| 20 Aug 2026, 02:02 | 1,294,707 | +142 |
| 18 Aug 2026, 23:35 | 1,294,565 | -114 |
| 17 Aug 2026, 21:34 | 1,294,679 | -342 |
| 16 Aug 2026, 19:23 | 1,295,021 | -40 |
| 15 Aug 2026, 06:36 | 1,295,061 | first reading |
3,941 posts held, back to 29 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 312 pages of 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.
| Window | Rolling 30 days · latest post in window 7 September 2026 |
|---|---|
| Posts held | 3,941 (29 October 2025 – 7 September 2026) |
| Views total | 49,602,500 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Sept 2026, 20:45 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 7 September 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 156 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 417 of this channel’s own posts over the last 30 days (5 of the 24-hour readings behind this are interpolated, not measured directly): across 371 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 6.1 hours of being posted; a typical post has already reached 23.3% of its 24-hour view count within the first hour, and 65.5% within the first six; the median 24-hour reach across those posts is 99,600 views — 7.69% of this channel’s own subscriber count (90th percentile 108,000).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /522827 Sept 2026, 19:57 UTC | 218 minutes – 48 minutes old | 18,000 views ~no reaction reading | no checkpoint reading yet | not yet at 24h | 18 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /522797 Sept 2026, 19:17 UTC | 324 minutes – 88 minutes old | 28,300 views ~no reaction reading | 60 minutes: 22,400still climbing at last reading | not yet at 24h | 30 minutesprovisional — final view count still climbing |
| /522787 Sept 2026, 18:20 UTC | 516 minutes – 2.4 hours old | 39,100 views ~no reaction reading | 60 minutes: 22,654 interp.still climbing at last reading | not yet at 24h | 49 minutesprovisional — final view count still climbing |
| /522777 Sept 2026, 17:30 UTC | 75 minutes – 3.3 hours old | 45,500 views ~no reaction reading | 60 minutes: 23,681 interp. → 3.0 hours: 43,727 interp.still climbing at last reading | not yet at 24h | 57 minutesprovisional — final view count still climbing |
| /522767 Sept 2026, 17:04 UTC | 731 minutes – 3.7 hours old | 50,900 views ~no reaction reading | 60 minutes: 28,300 → 3.0 hours: 46,849 interp.still climbing at last reading | not yet at 24h | 51 minutesprovisional — final view count still climbing |
| /522757 Sept 2026, 15:45 UTC | 1010 minutes – 5.0 hours old | 59,400 views ~no reaction reading | 60 minutes: 20,176 interp. → 3.0 hours: 47,661 interp.still climbing at last reading | not yet at 24h | 1.5 hoursprovisional — final view count still climbing |
| /522747 Sept 2026, 15:18 UTC | 118 minutes – 5.5 hours old | 61,000 views ~no reaction reading | 60 minutes: 24,741 interp. → 3.0 hours: 47,482 interp.still climbing at last reading | not yet at 24h | 1.6 hoursprovisional — final view count still climbing |
| /522737 Sept 2026, 14:29 UTC | 1222 minutes – 6.3 hours old | 64,800 views ~no reaction reading | 60 minutes: 25,431 interp. → 3.0 hours: 48,500 → 6.0 hours: 63,300still climbing at last reading | not yet at 24h | 85 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 23 June 2026 to 7 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Пара из Питера заказала фотографа для атмосферной съёмки в городе, но местная жительница решила, что кадрам не бывать. Охранная система: баба Зина — ваша дверь всегда будет в безопасности.
В Подмосковье прошёл турнир RAF Moscow с россиянами и американцами на одном ковре. На арену приехали Садулаев, Снайдер, Барроуз, Браунагель, Чимаев, Вудли, Шара Буллет, Бо Никал и другие спортсмены, которых обычно проще увидеть в хайлайтах, чем в одном зале. Умар Кремлёв собрал под этот турнир полный зал и сильный международный состав. Отдельного символизма добавило то, что RAF Moscow прошёл в день переговоров Росс…
Молодая семья из четырёх человек живёт в студии площадью 20 квадратных метров — и считает это нормой. Семья приехала в Москву из региона, у них один шкаф на всех, а отдыхать приходится в туалете. Сейчас в семье ждут третьего ребёнка. Жизнь которой я боюсь.
Фанаты Спартака захватили караоке-будку. Красно-белых заметили в желтой караоке-будке, установленной по случаю 20-летнего юбилея Т-Банка на ВДНХ. Репертуар неизменен: «Знаешь ли ты» МакSим, которая считается неофициальным гимном московского клуба — фанаты поют ее до, после и во время матча.
Отец троих детей, отдыхавший в Турции, погиб, сломав шею после прыжка с пирса в море глубиной всего 40 сантиметров. 39-летний мужчина не обратил внимания на запрещающие знаки и нырнул в воду, которая оказалась буквально по колено. Его доставили в больницу, но спасти не смогли.
Заплыв на гигантских тыквах пройдёт на ВДНХ в сентябре. Ждем заплывы на кабачках.
В московском метро заметили лавочки, похожие на гробы. Необычные сиденья заметили на новой станции «Народное ополчение». Приляг, отдохни.
В высокий спрос на такси можно будет получить скидку, если подождать машину дольше В высокий спрос Яндекс Go будет предлагать опцию «Позже»: можно подождать машину в среднем 30–40 минут и уехать дешевле. Обычно скидка составит около 30%, иногда — до 50%. Цена и время ожидания будут известны заранее.
Первое ДТП с участием Tesla Cybercab внезапно случилось с грузовым самолётом. Boeing 767 компании Amazon выкатился за пределы взлётно-посадочной полосы при посадке в аэропорту Майами и врезался в несколько автомобилей на парковке. Реация людей убила.
Магнитные бури накроют Землю завтра-послезавтра. F метеозависимым.
АКИТ: атаки на логистику не повлияют на динамику роста маркетплейсов Российский рынок электронной коммерции продолжит расти, несмотря на недавние атаки на логистическую инфраструктуру маркетплейсов, заявил президент Ассоциации компаний интернет-торговли (АКИТ) Артем Соколов в ходе Восточного экономического форума. Согласно оценкам ассоциации, доступный покупателям ассортимент пострадал лишь на 2%. Площадки успешно …
GPT-6 Astra прошла все 48 уровней игры с капчей «Я не робот». Ушла эпоха.
Showing the 12 most recent of 3,941 posts we hold for @topor. 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.
@topor edited 2 posts 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.
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 20 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 279 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
18 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“ТОПОР - Горячие новости” (@topor), 1,295,579 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/topor.
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.