I beg your pardon
- Беги скорее4%
- Мы пропали6%
- Прошу прощения90%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
⚡6

Channel
@EnglishByEar
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
41,230subscribers
-1,208 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001747707130 |
|---|---|
| Type | Channel |
| Username | @EnglishByEar |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/EnglishByEar |
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 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 the other topics.
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 in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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 |
|---|---|---|---|
| @EngWithSongs/659827 Jul 2026, 15:20 UTC | @EnglishByEar/9501 · this entry27 Jul 2026, 15:20 UTC | 1.00 | under a minute |
| @EngWithSongs/659927 Jul 2026, 16:20 UTC | @EnglishByEar/9502 · this entry27 Jul 2026, 16:20 UTC | 1.00 | under a minute |
| @EngWithSongs/66071 Aug 2026, 10:40 UTC | @EnglishByEar/9510 · this entry1 Aug 2026, 10:40 UTC | 1.00 | under a minute |
| @EngWithSongs/66112 Aug 2026, 16:30 UTC | @EnglishByEar/9514 · this entry2 Aug 2026, 16:30 UTC | 1.00 | under a minute |
| @EngWithSongs/66196 Aug 2026, 06:00 UTC | @EnglishByEar/9521 · this entry6 Aug 2026, 06:00 UTC | 1.00 | under a minute |
| @EnglishByEar/9501 · this entry27 Jul 2026, 15:20 UTC | @English_Books_TG/591827 Jul 2026, 15:20 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @EngWithSongs | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–0) |
| @English_Books_TG | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @English_Books_TG (5–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. 1 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 6 comparable posts for this entry, running 27 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.
Of the group of 3 channels, the one whose matching posts we hold earliest is @EnglishByEar — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 7 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 is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 00:16 | 41,230 | +8 |
| 9 Nov 2026, 12:59 | 41,222 | -12 |
| 8 Nov 2026, 05:58 | 41,234 | -13 |
| 7 Nov 2026, 03:01 | 41,247 | +11 |
| 6 Nov 2026, 02:39 | 41,236 | -17 |
| 4 Nov 2026, 23:27 | 41,253 | -12 |
| 3 Nov 2026, 23:09 | 41,265 | -12 |
| 3 Nov 2026, 02:27 | 41,277 | -5 |
| 2 Nov 2026, 00:00 | 41,282 | -19 |
| 1 Nov 2026, 00:55 | 41,301 | -27 |
| 31 Oct 2026, 03:50 | 41,328 | +26 |
| 30 Oct 2026, 05:57 | 41,302 | -23 |
| 29 Oct 2026, 08:06 | 41,325 | -24 |
| 28 Oct 2026, 05:08 | 41,349 | -13 |
| 27 Oct 2026, 02:09 | 41,362 | -21 |
| 26 Oct 2026, 00:31 | 41,383 | -13 |
| 24 Oct 2026, 22:45 | 41,396 | -20 |
| 24 Oct 2026, 01:01 | 41,416 | -12 |
| 23 Oct 2026, 01:36 | 41,428 | -12 |
| 22 Oct 2026, 00:19 | 41,440 | first reading |
228 posts held, back to 23 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 222 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. It is computed over the 39 of 62 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 228 (23 July 2026 – 9 November 2026) |
| Views total | 63,589 |
| Reactions total | 176 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 17:50 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.
Measured directly from 16 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.
829 reactions across 137 posts, in 15 distinct kinds. The most used accounts for 40.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 336 | 40.5% | |
| 👍 | 259 | 31.2% | |
| ⚡ | 149 | 18.0% | |
| 🔥 | 28 | 3.38% | |
| 🤔 | 12 | 1.45% | |
| 👏 | 11 | 1.33% | |
| 🤯 | 11 | 1.33% | |
| 💯 | 9 | 1.09% | |
| 😢 | 5 | 0.603% | |
| 🤓 | 4 | 0.483% | |
| ☃ | 1 | 0.121% | |
| 🎉 | 1 | 0.121% | |
| 🏆 | 1 | 0.121% | |
| 😎 | 1 | 0.121% | |
| 😭 | 1 | 0.121% |
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 146 of the 228 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 829 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 228 most recent posts we hold, published 23 July 2026 to 9 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @EnglishByEar. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 228 most recent posts we hold for this entry, published 23 July 2026 to 9 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFHPa1a2 | 1 | 3 November 2026 | 3 November 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 228 most recent posts we hold, published 23 July 2026 to 9 November 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.
Telegram’s own ‘edited’ marker: 0 of 62 posts held from the last 30 days (0%) 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).
I beg your pardon
Shares as published. No per-option vote count is published by Telegram, so none is shown.
⚡6
Всё, что нужно для легкой учебы, успешной карьеры и мощной прокачки иностранных языков, в одном месте! 🚀 Друзья, мы объединили в одну удобную папку каналы, которые помогут сдать экзамены на максимум, запустить бизнес, упростить учебу и открыть новые карьерные возможности для вас и ваших детей:▫️ 🤍 Школа на лайте: секреты легкой домашки, подготовка к первому классу и развитие ребенка без нервов. 🤍 Экзамены без пани…
❤3🔥3💯2
Плaтим 2200 pyблeй зa oтзыв нa OZON 💙 • Kpoмe дeнeг вы пoлyчaeтe eщe и тoвapы для oтзывoв. • Пoдoйдeт и для шкoльникa и для мaмы в дeкpeтe. • Moжнo paбoтaть c тeлeфoнa. • Зaдaния ecть кaждый дeнь. Bзять пoдpaбoткy 👇 https://t.me/+dvYBjHcQ4DI1ZThi
Приветики! Как вам такая подборка инглиш-каналов? С ними реально можно закрыть все потребности в изучении английского: 1. Английский курсом для продвинутых! — тг канал-тренажёр для продвинутых в английском! Методично прокачай каузативы, сленг и идиомы! 2. Визуальный английский — загони английский сразу в подкорку через визуууааал!!!! 3. 6 котов про English — 6 котов про English — оригинальные short stories на анг…
File, posted without a caption
👍1
As far as I'm concerned, it's time for her to break up with Tim—he just doesn't treat her as well as she deserves.
👍6
Грамматику в английском не нужно учить ⚠️ Ее нужно понемногу тренировать каждый день и доводить до автоматизма. В канале English Grammar Lessons упражнения, тесты и уроки, которые помогают перестать угадывать грамматику и начать ее чувствовать. 🤩Нужно всего 5–10 минут в день, чтобы правильная конструкция приходила в голову раньше, чем ты успеешь вспомнить правило. Начни прямо сейчас: ⤵️ By the time we arrived, t…
He didn’t study, so he’s got only ________if he fails (`винить кого-либо`)
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
⚡6
В этой инглиш-подборке нет случайных блогов — только проверенные. Загляните в каждый! ◽️English from London — Английский глазами человека, живущего в Лондоне! Фишки носителей, неожиданные детали языка и атмосфера страны. В канале ищите полезные гайды! ◽️ Well…English — Английский для общения, решений и перемен. Разбираем жизненные ситуации и находим нужные слова. Чтобы английский помогал вам там, где он действител…
File, posted without a caption
Are you feeling better?" "I beg your pardon?" "I said: Are you feeling better?"
👍3
Самое ценное за 23 года преподавания в одном канале Эксперты Международного центра ILS уже 20+ лет преподают английский, а теперь завели канал, в котором каждый день объясняют: 📌 сложную грамматику – просто и понятно 📌 слова и фразы – как реально говорят за границей 📌 полезные лайфхаки – ваш языковой барьер рухнет 🔥 Бонус: преподаватели создали полезные гайды и интерактивные задания, который можно бесплатно забрат…
Showing the 12 most recent of 228 posts we hold for @EnglishByEar. 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.
We recorded 53 posts on @EnglishByEar 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.
The 6 most recent of 33 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
I beg your pardon
Shares as published. No per-option vote count is published by Telegram, so none is shown.
He didn’t study, so he’s got only ________if he fails (`винить кого-либо`)
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
I let my kids sleep with me in my bedroom _________, like if they've had a nightmare. ('при определенных обстоятельствах')
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Easy peasy lemon squeezy
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
I thought I was going to fail the test, but it turned out to be _______! ('проще пареной репы')
Shares as published. No per-option vote count is published by Telegram, so none is shown.
That's a big word, __? (Это большое слово, можете произнести по буквам?)
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 228 most recent posts we hold, published 23 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.
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.
Named by 8 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.
@EnglishByEar named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was 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.
Read from Telegram’s recommendation API, most recently 29 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 43 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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“Английский на слух” (@EnglishByEar), 41,230 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/EnglishByEar.
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.