Telegram RegisterThe public register of Telegram

Channel

«Зенит» Санкт-Петербург

@ZenitSaintPetersburg

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

1,038subscribers

-7 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001332115311
TypeChannel
Username@ZenitSaintPetersburg
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/ZenitSaintPetersburg

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 99% 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zenit_saintpeterburg/311430 Jul 2026, 06:05 UTC@ZenitSaintPetersburg/6864 · this entry30 Jul 2026, 06:10 UTC1.005 minutes
@zenit_saintpeterburg/311631 Jul 2026, 05:56 UTC@ZenitSaintPetersburg/6867 · this entry31 Jul 2026, 06:07 UTC1.0011 minutes
@zenit_saintpeterburg/311731 Jul 2026, 09:34 UTC@ZenitSaintPetersburg/6868 · this entry31 Jul 2026, 14:52 UTC1.005.3 hours
@zenit_saintpeterburg/31191 Aug 2026, 09:11 UTC@ZenitSaintPetersburg/6870 · this entry1 Aug 2026, 15:07 UTC1.005.9 hours
@zenit_saintpeterburg/31202 Aug 2026, 06:40 UTC@ZenitSaintPetersburg/6871 · this entry2 Aug 2026, 06:42 UTC1.002 minutes
@zenit_saintpeterburg/31223 Aug 2026, 05:54 UTC@ZenitSaintPetersburg/6875 · this entry3 Aug 2026, 06:00 UTC1.006 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@zenit_saintpeterburg11 (8/8 hand-verifiable sample passed)1.002.3 hours@zenit_saintpeterburg (110)

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 11 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 16 comparable posts for this entry, running 29 July 2026 to 6 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 @zenit_saintpeterburg. That is a statement about our reading window, not a claim of authorship.

Views per post sit far above this size band

1,900 average views per post against 1,038 subscribers — an engagement rate of 183.2%. Across the 54,164 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Russian — the middle half sit between 10.5% and 35.6%, with a median of 20.1%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured20 of 20 published in the window (0 exact, 20 rounded by Telegram)
Views totalled38,030
Mature posts only187.8% over 18 posts read at least 24h after publication
Subscribers1,038 measured 9 August 2026
Cohortb1000:rus · 54,164 channels · p10 5.33% · p25 10.5% · p50 20.1% · p75 35.6% · p90 57.1%
Position in cohort99.468th percentile · 9.1× the cohort median
Uncertainty±0.28% of the figure, from Telegram’s rounding
Post languageRussian · 100.0%of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_copy · err_high, last confirmed 12 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

1,0381,0451,041.56 August 2026 — 1,045 subscribers6 August 2026 — 1,045 subscribers9 August 2026 — 1,038 subscribers6 August 20269 August 2026
3 measurements spanning 3 days, net -7. 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 1,037–1,046 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 18:121,038-7
6 Aug 2026, 13:011,045no change
6 Aug 2026, 08:551,045first reading

Engagement

20 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
183.2%
avg views ÷ 1,038 subscribers
Avg views / post
1,900
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (29 July 20266 August 2026)
Views total38,030
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 13:01 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.

Recent posts

6 Aug 2026, 05:11 UTC≈1,080 viewsread 6 August 2026
Photo

⚡️Кондаков – в больнице, об этом рассказал Сергей Семак: по словам главного тренера «Зенита», его надо зашивать и смотреть, что случилось, насколько серьезная травма. Полузащитник «Зенита» получил удар локтем в лицо после которого у него выступила кровь на лице – 27-летний арбитр Никита Новиков не показал никакой карточки защитнику гостей Эдуардо Андерсону.

5 Aug 2026, 14:12 UTC≈1,860 viewsread 6 August 2026
Photo

⚡️🇧🇷 Ge Globo | Полузащитник «Флуминенсе» Эркулес может перейти в «Зенит» Клуб дал понять, что проявляет интерес к 25-летнему центральному полузащитнику. При этом контактов между клубами ещё не было. Эркулес может стать эдакой заменой Данило из «Ботафого», который отказался ехать в Россию.

5 Aug 2026, 05:33 UTC≈1,820 viewsread 6 August 2026
Photo

Fan ID введут в Кубке России начиная с весенней части сезона на матчах Пути РПЛ: изначально планировалось ввести паспорт болельщика начиная с группового этапа, но в итоге сроки внедрения перенесли на весну — прямо сейчас Fan ID для посещения матчей Кубка России не требуется, — Sport Baza Путь регионов безопаснее.

4 Aug 2026, 15:10 UTC≈2,030 viewsread 6 August 2026
Photo

Любимый соперник Безумного Макса 🔥

4 Aug 2026, 06:39 UTC≈1,890 viewsread 6 August 2026
Photo

#ЗенитБалтика: кубковый матч обслужит бригада Никиты Новикова 27-летний арбитр из Петрозаводска назначен на официальную игру с участием сине-бело-голубых впервые в карьере. Ассистенты — Максим Гаврилин из Владимира и Денис Петров из Астрахани Резервный арбитр — петербуржец Ефим Рубцов Главный судья ВАР — Артур Федоров из Петрозаводска, его помощник — москвич Роман Сафьян Первый матч группового этапа FONBET Кубка Р

3 Aug 2026, 13:14 UTC≈1,910 viewsread 6 August 2026
Photo

⚡️ Дмитрий Васильев продолжит карьеру в Оренбурге Футбольные клубы «Зенит» и «Оренбург» достигли договоренности о переходе полузащитника. Футбольный клуб «Зенит» благодарит Дмитрия Васильева за вклад в победы и титулы и желает удачи в дальнейшей карьере!

3 Aug 2026, 13:13 UTC≈1,900 viewsread 6 August 2026
Photo

⛔️ Mash на спорте | Густаво Мантуан насобирал 47 штрафов на 81,7 тысяч рублей. Бразилец также гонял на «Мерседесе». 30 раз превысил скорость, 14 раз не оплатил парковку, один раз остановился в неположенном месте и ещё разочек проехал на красный на Коломяжском проспекте. Иномарку Густаво купил в 2023-м, через год как переехал в Петербург. Стоимость автомобиля равна примерно 12-15 млн рублей. Ранее СМИ опубликовали

3 Aug 2026, 06:00 UTC≈1,890 viewsread 6 August 2026
Photo

💙 Сергей Семак — о матче: «Хорошая игра получилась в нашем исполнении. Хорошо вошли в игру, забили хороший мяч, были еще моменты для того, чтобы увеличить преимущество Во втором тайме, после второго забитого мяча, конечно, игра немножко подуспокоилась для нас с точки зрения того напряжения, которое было. «Оренбург» — команда, которая традиционно хорошо играет дома Синтетика, много движения, борьбы, единоборств, мн

2 Aug 2026, 15:00 UTC≈2,090 viewsread 6 August 2026
Photo

МАКСимальный результат! 🔥

2 Aug 2026, 12:57 UTC≈2,110 viewsread 6 August 2026
Photo

⚡️ СТАРТОВЫЕ СОСТАВЫ. Касаджиков в основе у «Оренбурга»!

2 Aug 2026, 11:04 UTC≈1,850 viewsread 6 August 2026
Photo

⚡️ ДЕНЬ МАТЧА ⚽️ «Оренбург» – «Зенит» 📅 2 августа, 16:00 🏆 РПЛ, 2-й тур 🏟 «Газовик»

2 Aug 2026, 06:42 UTC≈2,040 viewsread 6 August 2026
Photo

🗣🇧🇷 Главный тренер «Зенита» Сергей Семак ответил на вопрос, смогут ли Дуглас Сантос и Луис Энрике сыграть в матче с «Оренбургом»: «Оба будут в заявке. Правда, форму набирают по разному. Дугласу Сантосу делать это попроще ввиду его эмоционального состояния. Все же Луис Энрике ожидал на чемпионате мира другого. В общем, различия есть, но играть готовы оба»

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

Citation-graph rank — 1,118,315 of 1,151,006entries 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.

Mentions

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.

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

“«Зенит» Санкт-Петербург” (@ZenitSaintPetersburg), 1,038 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ZenitSaintPetersburg.

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.