Telegram RegisterThe public register of Telegram

Channel

🇬🇧Fixenglish

@fixenglish1

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,283subscribers

+34 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-1002544534548
TypeChannel
Username@fixenglish1
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/fixenglish1

Growth

2,2482,2832,265.56 August 2026 — 2,249 subscribers6 August 2026 — 2,248 subscribers6 August 2026 — 2,248 subscribers9 August 2026 — 2,264 subscribers12 August 2026 — 2,268 subscribers15 August 2026 — 2,283 subscribers6 August 202615 August 2026
6 measurements spanning 9 days, net +34. 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 2,243–2,288 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 01:362,283+15
12 Aug 2026, 04:042,268+4
9 Aug 2026, 14:222,264+16
6 Aug 2026, 06:022,248no change
6 Aug 2026, 05:302,248-1
6 Aug 2026, 01:482,249first reading

Engagement

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

ERR · 30 days
22.0%
avg views ÷ 2,283 subscribers
Avg views / post
501
7 posts measured
Reaction rate
0.618%
reactions ÷ views · ER floor
Posts in window
7
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. It is computed over the 6 of 7 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (4 June 20267 August 2026)
Views total3,508
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:52 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.

Reaction mix

97 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 79.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7779.4%
👍77.22%
🍓33.09%
👌22.06%
🙏22.06%
🍾11.03%
👎11.03%
👏11.03%
💩11.03%
🔥11.03%
😁11.03%

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 19 of the 20 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 97reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 4 June 2026 to 7 August 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.

Recent posts

7 Aug 2026, 09:55 UTC44 views0 reactionsread 7 August 2026
Forwarded from @hod_hod_Tabadol

🇺🇸کلاسهای مکالمه و رفع اشکال، درخواست پارتنر و پرسش و پاسخ انگلیسی 🇬🇧👇😍 https://t.me/+em-oV_Uj7uozYWQ0 انگلیسے یاد بگیــریم •• 🇺🇸@mrSaddiqienglishlearning فقط گرامر 🇺🇸@usuk1 تحلیل معنایی و درکِ عمیقِ انگلیسی 🇺🇸@Englishnutsbolts تقویت (مکالمه) با ۳۶۳ کارتون ۸ دقیقه ای 🇺🇸@EnglishCartoonn2024 نکات کاربردی زبان 🇺🇸@English_ili گرامر تخصصی انگلیسی 🇺🇸@Grammar_in_use25 انگلیسی کامل Complete English 🇺🇸@englishteachin

Signed ஜ( Aʅι )ஜ

7 Aug 2026, 07:32 UTC110 viewsread 7 August 2026

❌ اشتباه: I can't wait until Friday. ✅ طبیعی‌تر: I can't wait for Friday. چرا؟ وقتی می‌گی: I can't wait for Friday. یعنی: «بی‌صبرانه منتظر جمعه‌ام.» ❤️ اما اگر بگی: I can't wait until Friday. معنی تحت‌اللفظیش اینه: «نمی‌توانم تا جمعه صبر کنم.» به همین دلیل ممکنه شنونده فکر کنه منظورت اینه که انقدر بی‌طاقتی که نمی‌تونی تا جمعه دوام بیاری، نه اینکه صرفاً مشتاق جمعه‌ای. @Fixenglish1 🐳 اشتباهات رایج زبان

Signed ஜ( Aʅι )ஜ

2 Aug 2026, 16:51 UTC361 views5 reactionsread 7 August 2026

این اشتباه رایج از آن‌هایی است که حتی زبان‌آموزهای سطح بالا هم گاهی مرتکب می‌شوند. ❌ اشتباه: I can't bear with it. چرا اشتباه است؟ چون bear به‌تنهایی معنی «تحمل کردن» می‌دهد و بعد از آن with نمی‌آید. ✅ درست: I can't bear it. I can't stand it. اما چرا بعضی‌ها اشتباه می‌کنند؟ چون عبارت put up with را بلد هستند: I can't put up with it. ✅ و ناخودآگاه with را به bear هم اضافه می‌کنند: I can't bear with it. ❌

4💩1

Signed ஜ( Aʅι )ஜ

28 Jul 2026, 07:32 UTC609 views6 reactionsread 7 August 2026

❌ اشتباه رایج: I almost passed the exam. ❌ (وقتی منظورت «به‌زحمت قبول شدم» است.) ✅ درستش: I barely passed the exam. 📌 چرا؟ - almost = نزدیک بود، اما اتفاق نیفتاد. - barely = اتفاق افتاد، اما به‌زحمت. 📍 مثال: ❌ I almost caught the bus. = نزدیک بود به اتوبوس برسم، اما نرسیدم. ✅ I barely caught the bus. = به‌زحمت به اتوبوس رسیدم. 💡 نکته : اگر کاری انجام نشد → almost اگر کاری انجام شد، اما به‌سختی → barely @Fixe

4👌2

Signed ஜ( Aʅι )ஜ

23 Jul 2026, 12:46 UTC768 views3 reactionsread 7 August 2026

اشتباه رایج: Because و That's why را با هم به کار نبرید. ❌ Because I was tired, that's why I slept early. ✅ Because I was tired, I slept early. یا ✅ I was tired. That's why I slept early @Fixenglish1 ⭐️ کانال تخصصی اشتباهات رایج زبان

3

Signed ஜ( Aʅι )ஜ

22 Jul 2026, 19:13 UTC715 views3 reactionsread 7 August 2026

❌ اشتباه رایج: The reason is because... ✅ درست: The reason is that... یا It's because... --- چرا؟ کلمه‌ی reason خودش معنی «دلیل» رو می‌ده، و because هم یعنی «به خاطر اینکه». استفاده از هر دو کنار هم، از نظر نگارشی اضافی (redundant) محسوب می‌شه. --- مثال‌ها ❌ The reason I left is because I was tired. ✅ The reason I left is that I was tired. ✅ I left because I was tired. @Fixenglish1 🎓 اشتباهات رایج زبان

3

Signed ஜ( Aʅι )ஜ

17 Jul 2026, 18:25 UTC901 views4 reactionsread 7 August 2026

🚫 اشتباه رایج ❌ I wish I would know the answer. ✅ I wish I knew the answer. 💡 چرا؟ وقتی I wish برای حسرت درباره وضعیت فعلی به کار می‌رود، بعد از آن از Past Simple استفاده می‌کنیم، نه would. ✔️ I wish I knew. ✔️ I wish I had more time. ❌ I wish I would know... ❌ I wish I would have... @Fixenglish1 👨‍🏫 کانال تخصصی اشتباهات رایج 🎓 اشتباهات رایج زبان

👍31

Signed ஜ( Aʅι )ஜ

11 Jul 2026, 16:35 UTC≈1,150 views5 reactionsread 7 August 2026

🚫 اشتباه رایج ❌ No sooner I arrived than it started to rain. ✅ No sooner had I arrived than it started to rain. 📌 مثال‌های کاربردی: ❌ Hardly I had sat down when the phone rang. ✅ Hardly had I sat down when the phone rang. ❌ Rarely I see such talent. ✅ Rarely do I see such talent. 💡 نکته‌ : بعد از قیدهای منفی یا محدودکننده مثل: 🔹 No sooner 🔹 Hardly 🔹 Rarely 🔹 Seldom 🔹 Never 🔹 Little ترتیب جمله برعکس می‌شود (

2🙏2👍1

Signed ஜ( Aʅι )ஜ

6 Jul 2026, 17:44 UTC≈1,210 views6 reactionsread 7 August 2026

🚫 اشتباه رایج: ❌ I have been in Paris since two weeks. ✅ I have been in Paris for two weeks. 📌 مثال‌های کاربردی: ❌ She has lived here since three months. ✅ She has lived here for three months. ❌ We have known each other since ten years. ✅ We have known each other for ten years. ❌ I have worked here since 2022. ✅ I have worked here since 2022. ✅ 💡 نکته‌ : since برای نقطه‌ی شروع زمان است. ✔️ since 2022 ✔️ since

5🔥1

Signed ஜ( Aʅι )ஜ

4 Jul 2026, 14:57 UTC≈1,110 views10 reactionsread 7 August 2026

🚫 اشتباه رایج: ❌ I married with her. ✅ I married her. ✅ I am married to her. 📌 مثال‌های کاربردی: ❌ He married with Sarah. ✅ He married Sarah. ❌ They got married with each other. ✅ They got married to each other. ❌ Is she married with him? ✅ Is she married to him? 💡 نکته‌ : 🔹 marry + شخص ✔️ He married Anna. 🔹 be married to + شخص ✔️ He is married to Anna. 🔹 get married to + شخص ✔️ They got married to each oth

7🍓3

Signed ஜ( Aʅι )ஜ

23 Jun 2026, 16:30 UTC≈1,440 views5 reactionsread 7 August 2026

🚫 اشتباه رایج: ❌ Despite of the rain, we went out. ✅ Despite the rain, we went out. ✅ In spite of the rain, we went out. --- 📌 چرا؟ "Despite" به تنهایی استفاده می‌شود و بعدش مستقیماً اسم یا gerund می‌آید. ✔ despite the rain ✔ despite being tired اما "in spite" همیشه با "of" می‌آید: ✔ in spite of the rain ✔ in spite of being tired --- 📌 نکته : ✅ despite + noun / V-ing ✅ in spite of + noun / V-ing ❌ despit

4👏1

Signed ஜ( Aʅι )ஜ

22 Jun 2026, 16:11 UTC≈1,120 views5 reactionsread 7 August 2026

📌 نکته گرامری | job vs work 🔹 job = شغل (اسم قابل شمارش) ✔ I have a new job. --- 🔹 work = کار (اسم غیرقابل شمارش) ✔ I have a lot of work. --- 🚫 اشتباه رایج: ❌ I have many works. ✅ I have a lot of work. --- 💡 نکته طلایی job = شغل work = کار بعد از work معمولاً a/an یا جمع (works) نمی‌آید. 🔥 @Fixenglish1 ⭐️ اشتباهات رایج زبان

3👍1😁1

Signed ஜ( Aʅι )ஜ

Showing the 12 most recent of 20 posts we hold for @fixenglish1. 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 — 115,731 of 1,345,403entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

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

“🇬🇧Fixenglish” (@fixenglish1), 2,283 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/fixenglish1.

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.