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 10 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. They sit inside a group of 3 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.
Matching posts — open both and compare (6 of the pairs behind the counts below)
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 0 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 30 comparable posts for this entry, running 3 August 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 3, the earliest publisher we hold is @ilyevserg — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key 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.
Also posting the same content
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.
28 measurements spanning 33 days, net +296. 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 33,452–33,850 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)
Subscribers
Change
8 Sept 2026, 01:37
33,794
-10
4 Sept 2026, 22:19
33,804
+206
3 Sept 2026, 06:18
33,598
+13
2 Sept 2026, 03:17
33,585
+2
1 Sept 2026, 05:14
33,583
+3
31 Aug 2026, 06:34
33,580
+5
30 Aug 2026, 08:13
33,575
-11
29 Aug 2026, 09:02
33,586
-8
28 Aug 2026, 05:27
33,594
-2
27 Aug 2026, 04:37
33,596
-10
26 Aug 2026, 02:55
33,606
+1
25 Aug 2026, 02:42
33,605
-5
23 Aug 2026, 17:09
33,610
+14
21 Aug 2026, 23:54
33,596
+30
20 Aug 2026, 16:47
33,566
+14
19 Aug 2026, 14:22
33,552
+3
18 Aug 2026, 15:28
33,549
-32
17 Aug 2026, 12:07
33,581
+16
16 Aug 2026, 04:07
33,565
+12
14 Aug 2026, 12:37
33,553
first reading
Engagement
301 posts held, back to 3 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 69 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
31.5%
avg views ÷ 33,794 subscribers
Avg views / post
10,700
233 posts measured
Reaction rate
0.864%
reactions ÷ views · ER floor
Posts in window
236
of 301 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
Window
Rolling 30 days · latest post in window 9 September 2026
Posts held
301 (3 August 2026 – 9 September 2026)
Views total
2,481,880
Reactions total
21,451
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Sept 2026, 14:06 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
≈4,790
Videos
≈3,210
Links
≈10,300
Lifetime counters from Telegram’s own channel header, read 9 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.
Video runtime
52m 57s
Average length
33s
Measured directly from 96 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.
Reaction mix
26,872 reactions across 285 posts, in 23 distinct kinds. The most used accounts for 27.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
7,323
27.3%
👍
6,102
22.7%
🔥
3,239
12.1%
😁
3,232
12.0%
👎
1,642
6.11%
👏
1,318
4.90%
💯
668
2.49%
🤯
600
2.23%
🤬
523
1.95%
😢
497
1.85%
😱
352
1.31%
🙏
339
1.26%
🤷♂
318
1.18%
🐳
240
0.893%
❤🔥
176
0.655%
🕊
161
0.599%
🤩
43
0.16%
🍾
25
0.093%
🎄
25
0.093%
🎉
18
0.067%
3 further kinds
31
0.115%
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 296 of the 301 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 27,921 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 301 most recent posts we hold, published 3 August 2026 to 9 September 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.
"Факел" отзаявил Магомедова и Гиоргобиани, а потом дозаявил снова
Акция устрашения? 🤔
Как ранее сообщал, Николая Гиоргобиани и Бутту Магомедова хочет "Сочи", последнего еще и "Урал". Но пока никаких договоренностей. Вообще.
Магомедов готов перейти в "Сочи" только на полноценный двухлетний контракт, а "барсы" ему предлагают аренду. При этом с сохранением заработной платы.
Пока ясно, что ничего не ясно, и по Мераби…
⚡️ "Шинник" определился со сменщиком Митрова
По моим данным, ярославцы определились со сменщиком Тимофея Митрова. "Шинник" на два года подпишет воспитанника "Рубина" Никиту Яновича. Он переходит из "Тюмени" свободным агентом.
Янович ранее мелькал по отношению к "Шиннику" .
На флажке волжане еще рассматривали Андрея Ходановича из "Оренбурга", но там только аренда. А черно-синие хотели голкипера на полноценный контр…
Максимов подписал со СКА. Жиров, скорее всего, перейдет туда же, а не в "Урал"
Максим Максимов, по моим данным, стал игроком хабаровского СКА. Контракт до конца сезона.
Кроме того, дальневосточники умасливают Александра Жирова, которого также рассматривает "Урал". Анар пишет, что у "шмелей" есть на повестке и кандидатура Заурбека Плиева в случае ухода Итало. Однако инфы, что бразильца продадут, пока нет. Это все в…
Гунько покинул "Арсенал"
Дмитрий Гунько освобожден с поста главного тренера туляков. Читалось.
А как там с Александром Денисовым?
По кривым рельсам в Туле поехали еще в межсезонье, когда губернатору запудрили голову. И сейчас, на мой взгляд, должно быть не половинчатое решение, а комплексное.
"Волга" до конца недели определится с главным тренером
Он либо будет уже руководить командой в календарном матче с "Уфой", либо просто присутствовать на этой игре и консультировать. Сейчас ульяновцы без тренировочного процесса. Сегодня у них кубковый поединок в Астрахани, а уже в воскресенье - встреча в столице Башкирии.
Движение началось. Я слышал о пяти кандидатах. В шорт-листе - Андрей Тихонов, Хасанби Биджиев, …
⚡️ Жиров может перейти в "Урал"
Ух, как рынок перед дедлайном взрывается.
По моим данным, Александр Жиров, уже дебютировавший за ростовский СКА в Медиалиге, может перейти в "Урал".
Связано ли с возможной продажей Итало? Узнаем завтра. Оба - левые центральные защитники.
На самом деле, ничего удивительного. Жиров в тройке центральных с такими же ветеранчиками Бегичем и Тихим сыграет спокойно.
Кроме того, "Урал" ос…
🤒 Для кого-кого, а для "Арсенала" в нынешней ситуации Кубок был важен
И отсюда вылетели.
Игру с Хабарой Дмитрию Гунько, наверное, еще дадут, но поплавок уже почти скрылся под водой. Очевидно: второй сезон - и не получается. Долго в таком режиме, когда каждый следующий матч может стать последним, существовать невозможно. Для Дмитрия Ивановича крайней должна была стать игра 4-го тура с "Торпедо", но там чудом выиграл…
🎤❗️ Дмитрий Хотимский - о Мохаммади, гиганте Спахиче, стадионе в Костроме и своем участие в разминках "Спартака"
Небольшое, но конкретное интервью с совладельцем костромского "Спартака".
Фанам красно-белым - знаю, они меня читают в дороге - респект. Приятные ребята! Больше, чем со мной, совместных фоток они сделали только с Мохаммади 😉
"Сочи" сделал предложения Магомедову и Гиоргобиани
Черноморцы включились гиперактивно.
По моим данным, "Сочи" заинтересован не только в Бутте Магомедове, но и в Николае Гиоргобиани. "Барсы" сделали предложения обоим хавбекам "Факела". Те думают. Если переходы состоятся, то это будет аренда. Кого-то, наверное, отхватят.
По Максу Дзиову. Вокруг него кружат "Волга" и "Арсенал". Туляки также наводили справки по еще од…
🙌 Мохаммади на разрыв
Вот это игрочка привезли в Россию из Ирана.
После матча немного пообщался с бигбоссом костромского "Спартака" Дмитрием Хотимским. Попозже выложу.
Легенда
Третий ассист.. Тут еще и по ветру бросать удобно.
❤53👍39👎10🔥6🐳1😁1
Showing the 12 most recent of 301 posts we hold for @ilyevserg. 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.
Posts edited after publishing
@ilyevserg edited 5 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.
First edit seen
13 August 2026
Most recent edit
6 September 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 66 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Channels Telegram recommends alongside this one
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.
Инсайды от Карпа || Иван Карпов @karpinside · 143,652#1
Read from Telegram’s recommendation API, most recently 4 September 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.
Appears in Telegram’s recommendations for other channels
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.
Лига PARI @liga_pari · 51,430 Telegram ranks this channel #3 of 99 here — alongside 98 others — read 25 August 2026
ФК «Балтика» @fc_baltika · 45,210 Telegram ranks this channel #9 of 91 here — alongside 90 others — read 27 August 2026
ФК «Урал» @fc_uralEkb · 29,316 Telegram ranks this channel #11 of 95 here — alongside 94 others — read 8 September 2026
МЕЛБЕТ @melbet_official_russia · 55,122 Telegram ranks this channel #21 of 94 here — alongside 93 others — read 23 August 2026
Это футбол, брат! @etofootballbro · 66,322 Telegram ranks this channel #22 of 100 here — alongside 99 others — read 21 August 2026
Инсайды от Карпа || Иван Карпов @karpinside · 143,652 Telegram ranks this channel #25 of 100 here — alongside 99 others — read 13 August 2026
Альфа-Банк Российская Премьер-Лига @premierliga · 191,011 Telegram ranks this channel #26 of 98 here — alongside 97 others — read 11 August 2026
Metaratings @Metaratings · 28,931 Telegram ranks this channel #27 of 99 here — alongside 98 others — read 9 September 2026
Панк инсайд @punkinside · 39,315 Telegram ranks this channel #27 of 100 here — alongside 99 others — read 31 August 2026
БЕТСИТИ @betcity · 129,013 Telegram ranks this channel #28 of 79 here — alongside 78 others — read 13 August 2026
ФК «Факел» Воронеж @pfcfakel · 40,096 Telegram ranks this channel #30 of 97 here — alongside 96 others — read 31 August 2026
Алё, рэф! @aloref · 35,330 Telegram ranks this channel #31 of 100 here — alongside 99 others — read 2 September 2026
Nobel @nobel_arustamyan · 39,554 Telegram ranks this channel #32 of 100 here — alongside 99 others — read 30 August 2026
ФК «Локомотив» Москва @fclokomotiv · 80,455 Telegram ranks this channel #33 of 97 here — alongside 96 others — read 18 August 2026
FONBET Кубок России @russiancup_official · 127,743 Telegram ranks this channel #34 of 97 here — alongside 96 others — read 13 August 2026
Коммент.Шоу @comment_show · 55,239 Telegram ranks this channel #35 of 100 here — alongside 99 others — read 23 August 2026
ВГИК @vgik_of · 37,853 Telegram ranks this channel #38 of 98 here — alongside 97 others — read 31 August 2026
РБ Спорт @rbsportrb · 50,736 Telegram ranks this channel #38 of 100 here — alongside 99 others — read 25 August 2026
РФС @rfsruofficial · 45,778 Telegram ranks this channel #41 of 100 here — alongside 99 others — read 27 August 2026
Советский спорт @sovsport · 43,561 Telegram ranks this channel #42 of 97 here — alongside 96 others — read 28 August 2026
ФК «Ростов» | Футбольный клуб «Ростов» @fcrostov_official · 45,704 Telegram ranks this channel #42 of 98 here — alongside 97 others — read 27 August 2026
ФК «Динамо» Махачкала @dinmx · 31,925 Telegram ranks this channel #45 of 97 here — alongside 96 others — read 5 September 2026
ЭкСпорт Клипина @xsport24 · 37,954 Telegram ranks this channel #45 of 99 here — alongside 98 others — read 1 September 2026
⚡️Мини Дуров @MiniDurovv · 128,784 Telegram ranks this channel #49 of 60 here — alongside 59 others — read 22 August 2026
This channel appears in 44 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.
Referenced elsewhere
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
21 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
Атабаев, Эрбол Канатбекович(ru.wikipedia.org) “…business-gazeta.ru/news/284471|url-status=live}}{{cite web|url=https://t.me/ilyevserg/6592|title=По ситуации с Атабаевым|website=t.me|publisher=ФНЛ с…” read 23 August 2026
Ведерников, Данила Владимирович(ru.wikipedia.org) “…новости»|date=2024-01-17|lang=ru}}{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/8873|title=«Пари НН» отозвал Ведерникова из аренды в «Муроме»|website=t…” read 23 August 2026
Гаранин, Вадим Вячеславович(ru.wikipedia.org) “…командой после шестиматчевой безвыигрышной серии{{cite web|url=https://t.me/ilyevserg/6568|title=Гаранин больше не вернется к управлению «Енисеем»|website=t…” read 23 August 2026
Гвишиани, Гиорги(ru.wikipedia.org) “…Тбилиси)|Динамо-2 (Тбилиси)]]{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/9008|title=В КАМАЗ прибыл вингер тбилисского…” read 23 August 2026
Герасименко, Алексей Петрович(ru.wikipedia.org) “…web|title=Хромыков вернулся к управлению «Краснодаром-2»|url=https://t.me/ilyevserg/5368|website=[[Telegram|t.me]]|publisher=ФНЛ с…” read 23 August 2026
Иванов, Егор Олегович(ru.wikipedia.org) “…премьер-лиге (2018/19) пропустил из-за травмы{{cite web|url=https://t.me/ilyevserg/6583|title=С капитаном «Енисея», трижды рвавшим кресты, все…” read 23 August 2026
Исик, Артём Сергеевич(ru.wikipedia.org) “…Виктор Владимирович|Свежов]]{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/4170|title=КАМАЗ нашел опорника во второй лиге|website=t.me|publisher=ФНЛ…” read 23 August 2026
КАМАЗ (футбольный клуб)(ru.wikipedia.org) “…html|url-status=live}}{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/8254|title=У Бояринцева есть кредит доверия на ближайшие матчи|website=t…” read 23 August 2026
Кубок России по футболу 2022/2023(ru.wikipedia.org) “…Липецке соответственно{{cite web|url=https://t.me/ilyevserg/4056|title=Фёдор Щербаченко: «Надеемся, что Измайлов защитит права…” read 23 August 2026
Мамтов, Хасан Инальбекович(ru.wikipedia.org) “…отзаявлен{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/7895|title=Уридия отказался переходить в «Нефтехимик» и…” read 23 August 2026
Норчаев, Хусаин Туракул оглы(ru.wikipedia.org) “…финала. В 6 матчах забил 2 мяча{{Cite web|url=https://t.me/ilyevserg/5719|title=Станет ли Норчаев для «Алании» вторым Шомуродовым или…” read 23 August 2026
Первая лига России по футболу(ru.wikipedia.org) “…class="wikitable sortable"
|+ 10 самых посещаемых матчей{{cite web|url=https://t.me/ilyevserg/6683|title=Матч «Балтика» — «Рубин» собрал наибольшее число зрителей…” read 23 August 2026
Первая лига России по футболу 2022/2023(ru.wikipedia.org) “…/t.me/ilyevserg/6530|url-status=live}} Гаранин фактически был отстранён от управления командой{{cite web|url=https://t.me/…” read 23 August 2026
Первая лига России по футболу 2024/2025(ru.wikipedia.org) “…тренером считаться не мог{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/10358|title=Главным тренером «Алании» станет Тазабаев. Бетеева…” read 23 August 2026
Первая лига России по футболу 2026/2027(ru.wikipedia.org) “…2019/2020|сезона 2019/20]]{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/16929|title=Тренды предстоящего сезона|publisher=ФНЛ с…” read 23 August 2026
Салтыков, Никита Андреевич(ru.wikipedia.org) “…арендовал до конца сезона без дополнительных опций{{cite web|url=https://t.me/ilyevserg/6144|title=Салтыков мог оказаться не в «Акроне», а в Хабаровске…” read 23 August 2026
Свинов, Илья Евгеньевич(ru.wikipedia.org) “…s-date=2022-06-14}}{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/2213|title=2:2 в квадрате. Огненная суббота в ФНЛ|lang=ru|website=[[Телеграм|t…” read 23 August 2026
Чичинадзе, Анри(ru.wikipedia.org) “…сыграл в двух неофициальных{{cite web|author=Сергей Ильёв|url=https://t.me/ilyevserg/8714|title=«Черноморец» уламывал Чичинадзе с лета|lang=ru|website=t…” read 23 August 2026
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 September 2026 — this
entry's latest reading, not the date you are reading this.
“ФНЛ с Ильёвым” (@ilyevserg), 33,794 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/ilyevserg.
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.