Telegram RegisterThe public register of Telegram
Telegram profile photo for ВсОШ МЭ 02 23 24 47 69 77 РЕГИОН

Channel

ВсОШ МЭ 02 23 24 47 69 77 РЕГИОН

@OTVETY_NA_2026

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

63,269subscribers

+10,623 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001401881453
TypeChannel
Username@OTVETY_NA_2026
Description‼️ Только точные материалы, с проверенных источников ‼️ 🚀 Бот 1 - @otvetmvip_bot 🤖 Бот 2 - @otvety_na_247_bot 💬 Наши реальные отзывы: @ogeotziv
CreatedBetween 1 February 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/OTVETY_NA_2026

Topic

Education — 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 86% 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 the other topics.

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)
Posted firstThenOverlapGap
@OTVETY_NA_2026/6472 · this entry1 Jul 2026, 21:42 UTC@OTVETY_NA_7850/35941 Jul 2026, 21:43 UTC1.0072 seconds
@OTVETY_NA_7850/35982 Jul 2026, 07:30 UTC@OTVETY_NA_2026/6476 · this entry2 Jul 2026, 10:04 UTC1.002.6 hours
@OTVETY_NA_2026/6478 · this entry2 Jul 2026, 22:37 UTC@OTVETY_NA_7850/36065 Jul 2026, 19:13 UTC1.003 days
@OTVETY_NA_2026/6482 · this entry5 Jul 2026, 06:04 UTC@OTVETY_NA_7850/36025 Jul 2026, 06:33 UTC1.0029 minutes
@OTVETY_NA_2026/6484 · this entry5 Jul 2026, 12:12 UTC@OTVETY_NA_7850/36035 Jul 2026, 14:13 UTC1.002.0 hours
@OTVETY_NA_2026/6491 · this entry7 Jul 2026, 12:23 UTC@OTVETY_NA_7850/36117 Jul 2026, 13:25 UTC1.0061 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@OTVETY_NA_78506 (6/6 hand-verifiable sample passed)1.001.5 hoursthis entry (5–1)

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 1 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 19 comparable posts for this entry, running 1 July 2026 to 14 July 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 @OTVETY_NA_7850. That is a statement about our reading window, not a claim of authorship.

Views per post sit far below this size band

218 average views per post against 61,859 subscribers — an engagement rate of 0.353%. Across the 8,315 registered channels in the same cohort — 31,623–99,997 subscribers, posting mainly in Russian — the middle half sit between 5.08% and 20.8%, with a median of 10.5%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured121 of 139 published in the window (121 exact, 0 rounded by Telegram)
Views totalled26,407
Mature posts only0.356% over 119 posts read at least 24h after publication
Subscribers61,859 measured 5 November 2026
Cohortb31623:rus · 8,315 channels · p10 2.60% · p25 5.08% · p50 10.5% · p75 20.8% · p90 35.5%
Position in cohort0.890th percentile · 1/29 the cohort median
Uncertainty±0.047% 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 below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below 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_source · err_low, last confirmed 5 November 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.

Growth

44,98763,26954,1287 August 20268 November 2026
62 measurements spanning 93 days, net +10,623. 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 42,245–66,011 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
8 Nov 2026, 10:1663,269+5
7 Nov 2026, 03:4563,264+836
6 Nov 2026, 06:0762,428+569
5 Nov 2026, 06:0561,859-168
4 Nov 2026, 05:4962,027+661
3 Nov 2026, 06:5961,366-54
2 Nov 2026, 08:1561,420+561
1 Nov 2026, 04:4960,859-228
31 Oct 2026, 06:4561,087+540
30 Oct 2026, 08:1860,547-279
29 Oct 2026, 09:4660,826+7,157
28 Oct 2026, 10:0553,669-237
27 Oct 2026, 09:3653,906+247
26 Oct 2026, 07:0653,659+16
25 Oct 2026, 03:3053,643-333
24 Oct 2026, 02:2653,976+990
22 Oct 2026, 23:0452,986+54
21 Oct 2026, 21:4652,932+360
20 Oct 2026, 15:3552,572+489
19 Oct 2026, 17:2852,083first reading

Engagement

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

ERR · 30 days
0.332%
avg views ÷ 63,269 subscribers
Avg views / post
210
144 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
163
of 419 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 9 November 2026
Posts held419 (1 July 2026 – 9 November 2026)
Views total30,210
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Nov 2026, 13:57 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
≈2,640
Videos
≈2
Links
≈3,800

Lifetime counters from Telegram’s own channel header, read 9 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 102 of 163 posts held from the last 30 days (62.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

9 Nov 2026, 13:33 UTC36 viewsread 9 November 2026
Photo

⬆️ ВсОШ на 10 ноября 2026 г. ⬆️ ✅ Муниципальный Этап (МЭ) 🚀 Купить полные ответы + сами задания, отдельно через бота (регионы: 50, 77) 🚀 Купить полные ответы + сами задания, отдельно через бота (все остальные регионы) 🔗 Приобрести приватный канал можно в новом боте — моментальное добавление через СБП #1 и СБП #2 🔜 Задать вопрос и купить ответы на МЭ (нужный вам предмет и регион), можно ещё через администратора

9 Nov 2026, 12:10 UTC111 viewsread 9 November 2026

⬇️ Работы на 10 ноября 2026 г. ⬇️ ✅ Муниципальный Этап (МЭ) ⬇️ • ВсОШ (02 регион — Республика Башкортостан): 🛒РУССКИЙ ЯЗЫК • ВсОШ (05 регион — Республика Дагестан): 🛒ОБЗР 🛒МХК • ВсОШ (22 регион — Алтайский край): 🛒ОБЩЕСТВОЗНАНИЕ • ВсОШ (23 регион — Краснодарский край): 🛒БИОЛОГИЯ • ВсОШ (24 регион — Красноярский край): 🛒НЕМЕЦКИЙ ЯЗЫК • ВсОШ (27 регион — Хабаровский край): 🛒НЕМЕЦКИЙ ЯЗЫК • ВсОШ (35 регион — Вологодс…

9 Nov 2026, 10:21 UTC76 viewsread 9 November 2026

⬇️ ВсОШ Муниципальный Этап (МЭ) ⬇️ ✅ ВсОШ МЭ (78 регион — г. Санкт-Петербург): 🛒 РУССКИЙ ЯЗЫК 🚀 Купить задания + полные ответы на ВсОШ МЭ (регион 78), отдельно через бота

9 Nov 2026, 06:19 UTC133 viewsread 9 November 2026
Photo

⚡️ ВсОШ МЭ (Муниципальный Этап): Обществознание (47 регион - Ленинградская область) 🚀 Купить полные ответы + сами задания, отдельно через бота

9 Nov 2026, 06:16 UTC125 viewsread 9 November 2026
File

✅ ВсОШ МЭ (Муниципальный Этап): АСТРОНОМИЯ (23 регион - Краснодарский край) 🚀 Купить полные ответы + сами задания, отдельно через бота

9 Nov 2026, 05:42 UTC149 viewsread 9 November 2026
Photo

✅ ВcОШ МЭ (Муниципальный Этап): ЭКОЛОГИЯ, 9–11 классы (02 регион - Республика Башкортостан) 🚀 Купить полные ответы + сами задания, отдельно через бота

9 Nov 2026, 05:00 UTC107 viewsread 9 November 2026
Photo

✅ МОШ - Предпрофессиональная олимпиада: Математика 8-11 класс 🚀 Купить полные ответы + сами задания, отдельно через бота

9 Nov 2026, 04:45 UTC97 viewsread 9 November 2026
Photo

🛡 СтатГрад: Тренировочная работа №2 по биологии 9 класс (по РФ) 🚀 Купить полные ответы + сами задания, отдельно через бота

9 Nov 2026, 04:33 UTC101 viewsread 9 November 2026
Photo

✅ ВсОШ МЭ (Муниципальный Этап): Экология (69 регион - Тверская область) 🚀 Купить полные ответы + сами задания, отдельно через бота

9 Nov 2026, 04:33 UTC93 viewsread 9 November 2026
Photo

✅ ВсОШ МЭ (Муниципальный Этап): Русский язык (35 регион - Вологодская область) 🚀 Купить полные ответы + сами задания, отдельно через бота

9 Nov 2026, 04:30 UTC100 viewsread 9 November 2026
Photo

✅ ВсОШ МЭ (Муниципальный Этап): Русский язык (35 регион - Вологодская область) 🚀 Купить полные ответы + сами задания, отдельно через бота

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

@OTVETY_NA_2026 edited 32 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
19 August 2026
Most recent edit
9 November 2026

Posts recorded as deleted after publishing

We recorded 4 posts on @OTVETY_NA_2026 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
3 September 2026
Most recent seen missing
5 November 2026
Median time before seen missing
22 hours
Seen missing in the last 30 days
2

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Aug 2026, 12:10 UTCAnonymous Poll137 voters

Кому-нибудь ещё нужна наша помощь? 👇

  1. 👍 Да, нужны материалы64%
  2. 👎 Нет, уже не актуально24%
  3. ❓ Нужны другие работы — МЦКО, олимпиады и т.д.12%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 419 most recent posts we hold, published 1 July 2026 to 9 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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.

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

“ВсОШ МЭ 02 23 24 47 69 77 РЕГИОН” (@OTVETY_NA_2026), 63,269 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/OTVETY_NA_2026.

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.