Telegram RegisterThe public register of Telegram
Telegram profile photo for ЧЕМПИОНАТ РПЛ

Channel

ЧЕМПИОНАТ РПЛ

@championat_rpl

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

853subscribers

-322 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-1001381030503
TypeChannel
Username@championat_rpl
Created9 January 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/championat_rpl

Topic

Sports — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. 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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@championat_rpl/3316 · this entry28 Jul 2026, 05:55 UTC@futbolrpl_2020/398328 Jul 2026, 05:55 UTC1.00under a minute
@championat_rpl/3318 · this entry29 Jul 2026, 05:17 UTC@futbolrpl_2020/398529 Jul 2026, 05:18 UTC1.00under a minute
@championat_rpl/3324 · this entry1 Aug 2026, 13:58 UTC@futbolrpl_2020/39911 Aug 2026, 13:58 UTC1.00under a minute
@futbolrpl_2020/39922 Aug 2026, 06:42 UTC@championat_rpl/3325 · this entry2 Aug 2026, 06:42 UTC1.00under a minute
@championat_rpl/3328 · this entry5 Aug 2026, 05:33 UTC@futbolrpl_2020/39975 Aug 2026, 05:33 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@futbolrpl_20205 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (3–2)

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 2 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 13 comparable posts for this entry, running 26 July 2026 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @championat_rpl — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.

Growth

8531,1751,0147 August 2026 — 1,175 subscribers7 August 2026 — 1,175 subscribers8 August 2026 — 1,171 subscribers10 August 2026 — 1,150 subscribers14 August 2026 — 1,128 subscribers17 August 2026 — 1,099 subscribers21 August 2026 — 1,089 subscribers24 August 2026 — 1,066 subscribers27 August 2026 — 1,054 subscribers31 August 2026 — 1,051 subscribers2 September 2026 — 1,045 subscribers7 September 2026 — 1,028 subscribers11 September 2026 — 1,010 subscribers15 September 2026 — 1,098 subscribers19 September 2026 — 853 subscribers7 August 202619 September 2026
15 measurements spanning 43 days, net -322. 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 805–1,223 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 16:37853-245
15 Sept 2026, 04:191,098+88
11 Sept 2026, 23:211,010-18
7 Sept 2026, 21:391,028-17
2 Sept 2026, 21:241,045-6
31 Aug 2026, 00:561,051-3
27 Aug 2026, 15:541,054-12
24 Aug 2026, 13:571,066-23
21 Aug 2026, 04:471,089-10
17 Aug 2026, 18:381,099-29
14 Aug 2026, 14:131,128-22
10 Aug 2026, 22:181,150-21
8 Aug 2026, 08:441,171-4
7 Aug 2026, 23:321,175no change
7 Aug 2026, 19:481,175first reading

Engagement

20 posts held, back to 26 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 06:11 UTC567 viewsread 7 August 2026
Photo

🇷🇺«Динамо» может купить форварда «Лацио» и Сербии Раткова за 15 млн евро — Джанлука Ди Марцио 😎🇮🇹 У него 0+0 в 8 играх Серии А

6 Aug 2026, 12:09 UTC707 viewsread 7 August 2026
Photo

❗️❗️❗️❗️❗️❗️ Мирлинд Даку стал игроком «Спартака»

6 Aug 2026, 05:50 UTC716 viewsread 7 August 2026
Photo

🔴 Raisa Simplicio: «Фламенго» должен сделать официальное предложение «Зениту» по Луису Энрике сегодня или завтра. В руководстве «Фламенго» считают, что разумнее сделать ставку на Луиса Энрике, а не продолжать повышать предложение по Альмаде.

6 Aug 2026, 04:58 UTC652 viewsread 7 August 2026
Photo

😍🔴 Крутейший перфоманс болельщиков «Спартака» на домашней игре против «Оренбурга»

5 Aug 2026, 05:33 UTC721 viewsread 7 August 2026
Photo

🇷🇺ЦСКА хочет подписать защитника «Расинга» Мартирену и включить в сделку ди Лусиано — Анар Ибрагимов Теперь мы поняли, зачем в армейский клуб приходил Рамиро ди Лусиано 🤷‍♂️

4 Aug 2026, 04:39 UTC754 viewsread 7 August 2026
Photo

❗️❗️❗️❗️❗️❗️ «Рубин» объявил о переходе Жахонгира Урузова, игравшего на ЧМ-2026 за сборную Узбекистана

3 Aug 2026, 04:31 UTC760 viewsread 7 August 2026
Photo

🇷🇺 «Зенит» громит соперников второй тур подряд – сегодня за команду из Петербурга забивал только Максим Глушенков

2 Aug 2026, 06:42 UTC838 viewsread 7 August 2026
Photo

📝 Хуан Карседо — о продлении контракта с Барко: «Нам нужно идти вперед и доказывать, что мы способны одержать победу в Грозном. Это будет непросто. Для нас сейчас самое главное — сохранить футболистов, которые есть в составе. Барко? Мы довольны его вкладом в результат. Он работает хорошо. Надеюсь, что он останется с нами»

1 Aug 2026, 13:58 UTC882 viewsread 7 August 2026
Photo

👋 Похоже, «Рубин» прощается с Даку – игроки казанцев подхватили Мирлинда на руки и качали его после победы над «Акроном»

1 Aug 2026, 06:42 UTC697 viewsread 7 August 2026
Photo

🇹🇷 «Галатасарай» ведет переговоры по Батракову – игрок «Локо» приоритетнее для турок, чем Энсисо из Парагвая (Sportcell)

31 Jul 2026, 14:06 UTC714 viewsread 7 August 2026
Photo

⚡️«Локомотив» объявил об уходе Мампасси. Марк за 4 года провел 21 матч за «железнодорожников»

31 Jul 2026, 07:17 UTC821 viewsread 7 August 2026
Photo

😅 Бразильский полузащитник «Динамо» Бителло рассказал, звали ли бразильские игроки «Зенит» его в клуб: — «Не секрет, что ты хорошо общаешься с бразильцами «Зенита». Они пытались переманить тебя в Петербург?» — «Мы отлично общаемся с Венделом, Энрике, Мантуаном — они мои друзья, я всегда на связи с ними. Все, что мы обсуждаем, останется между нами. Я вам ничего не расскажу!»

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

Forward network

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.

Mentions

Named by 2 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.

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

“ЧЕМПИОНАТ РПЛ” (@championat_rpl), 853 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/championat_rpl.

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.