Telegram RegisterThe public register of Telegram

Channel

echo | Telegram Bots

@echomaker

2 usernames

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

489,939subscribers

-2,471 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001303380811
TypeChannel
Usernames@echomaker @mkfr_bot
DescriptionThe largest professional platform specialized in making Telegram Bots. اكبر منصة أحترافية متخصصة لصنع الروبوتات. https://echo.tg
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 live12 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/echomaker

Topic

Technology — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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 2 other registered channels. 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
@echomaker/1001 · this entry20 Jul 2026, 05:39 UTC@AVJK0/8520 Jul 2026, 19:25 UTC0.9914 hours
@echomaker/989 · this entry8 May 2026, 11:02 UTC@AVJK0/7717 May 2026, 20:13 UTC0.999 days
@echomaker/1000 · this entry20 May 2026, 09:01 UTC@AVJK0/8431 May 2026, 19:22 UTC0.9811 days
@echomaker/993 · this entry8 May 2026, 11:06 UTC@AVJK0/8117 May 2026, 20:13 UTC0.989 days
@echomaker/994 · this entry8 May 2026, 11:07 UTC@AVJK0/8217 May 2026, 20:13 UTC0.989 days
@echomaker/992 · this entry8 May 2026, 11:04 UTC@AVJK0/8017 May 2026, 20:13 UTC0.989 days
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@AVJK09 (8/8 hand-verifiable sample passed)0.989 daysthis entry (90)
@O_EOB5 (5/5 hand-verifiable sample passed)0.9972 secondsthis entry (50)

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 20 comparable posts for this entry, running 6 May 2026 to 20 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 @echomaker — 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.

Growth

489,939492,410491,174.56 August 2026 — 492,410 subscribers6 August 2026 — 492,410 subscribers7 August 2026 — 492,324 subscribers7 August 2026 — 492,324 subscribers7 August 2026 — 492,006 subscribers8 August 2026 — 491,882 subscribers8 August 2026 — 491,836 subscribers9 August 2026 — 491,365 subscribers9 August 2026 — 491,278 subscribers10 August 2026 — 490,954 subscribers10 August 2026 — 490,954 subscribers11 August 2026 — 490,570 subscribers11 August 2026 — 490,391 subscribers12 August 2026 — 490,104 subscribers12 August 2026 — 489,939 subscribers6 August 202612 August 2026
15 measurements spanning 6 days, net -2,471. 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 489,568–492,781 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 13:33489,939-165
12 Aug 2026, 05:24490,104-287
11 Aug 2026, 12:42490,391-179
11 Aug 2026, 08:22490,570-384
10 Aug 2026, 10:52490,954no change
10 Aug 2026, 10:50490,954-324
9 Aug 2026, 12:34491,278-87
9 Aug 2026, 08:41491,365-471
8 Aug 2026, 08:48491,836-46
8 Aug 2026, 05:21491,882-124
7 Aug 2026, 21:00492,006-318
7 Aug 2026, 05:41492,324no change
7 Aug 2026, 04:22492,324-86
6 Aug 2026, 23:15492,410no change
6 Aug 2026, 23:04492,410first reading

Engagement

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

ERR · 30 days
4.00%
avg views ÷ 489,939 subscribers
Avg views / post
19,600
2 posts measured
Reaction rate
0.214%
reactions ÷ views · ER floor
Posts in window
2
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 20 July 2026
Posts held20 (6 May 202620 July 2026)
Views total39,200
Reactions total84
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:38 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
413
Videos
1
Links
21

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

650 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 63.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
41063.1%
👨‍💻10115.5%
🔥7812.0%
👏619.38%

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 18 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 650reactions 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 6 May 2026 to 20 July 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.

Telegram Stars

Stars received
20
across the posts below
Posts paid on
8
of 19 we hold a reading for · 42%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @echomaker. 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 20 most recent posts we hold for this entry, published 6 May 2026 to 20 July 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.

Recent posts

20 Jul 2026, 05:40 UTC≈21,200 views58 reactions5 Starsread 12 August 2026

🚀 Massive Update — Bot Maker ━━━━━━━━━━━━━━━━━━━━ 🔒 New Force-Subscribe System Add up to 3 subscriptions of any type: channels · groups · bots · links. Set a subscriber limit with an automatic report sent to you on completion. ⏰ Scheduling & Custom Messages Schedule subscription time windows, fully customizable messages — everything under your control. 📊 Real Statistics Who viewed the gate · who actually joined · con

36👨‍💻11🔥11

20 Jul 2026, 05:39 UTC≈18,000 views26 reactionsread 12 August 2026

🚀 تحديث ضخم — بوت صانع البوتات ━━━━━━━━━━━━━━━━━━━━ 🔒 نظام الاشتراك الإجباري الجديد أضف حتى 3 اشتراكات من أي نوع: قنوات · مجموعات · بوتات · روابط. حدّد حداً أعلى للمشتركين مع تقرير تلقائي يصلك عند الاكتمال. ⏰ جدولة ورسائل مخصّصة جدولة أوقات الاشتراك، رسائل قابلة للتخصيص بالكامل، وكل شيء تحت سيطرتك. 📊 إحصائيات حقيقية من شاهد البوابة · من انضم فعلاً · نسبة التحويل — أرقام صادقة تعرف منها أداء كل اشتراك. 👁 معاينة مباشرة

20👨‍💻3🔥3

20 May 2026, 09:01 UTC≈54,900 views263 reactions5 Starsread 12 August 2026

🚀 تحديث - بوت الازرار - نظام الأزرار المرفقة ━━━━━━━━━━━━━━━━━━━━━━ ✨ الأزرار المرفقة الآن متاحة لكل أنواع الأزرار دعم كامل للأزرار من نوع محتوى عشوائي و اكثر من محتوى — مع إمكانية تعيين أزرار مرفقة لكل عنصر داخل الزر بشكل منفصل أو استخدام مجموعة افتراضية للجميع. 🧩 أنواع جديدة للأزرار المرفقة 🔗 رابط — يفتح موقع خارجي 🌐 Web App — يفتح تطبيق ويب داخل تيليجرام 📋 نسخ نص — يضع نصاً في حافظة المستخدم بضغطة واحدة 🧷 ربط

149👨‍💻56🔥31👏27

17 May 2026, 06:36 UTC≈47,200 views45 reactionsread 12 August 2026

🚀 New bot — Funding Bot ━━━━━━━━━━━━━━━━━━━━ 💡 What does this bot do? A complete points-economy bot to grow your Telegram channels and groups. Members earn points by joining funded channels, completing daily gifts, tasks, and invites — then spend those points to fund their own channels or buy services from the built-in store. ━━━━━━━━━━━━━━━━━━━━ 🛍 Services Store (SMM) Run your own store inside the bot! Connect y

31👏7🔥7

17 May 2026, 06:32 UTC≈27,100 views41 reactionsread 12 August 2026

🚀 تحديث جديد — بوت التمويل ━━━━━━━━━━━━━━━━━━━━ 🛍 متجر الخدمات (SMM) شغّل متجرك داخل البوت! اربط حسابك عند أي مزوّد خدمات، اختر الخدمات التي تريد بيعها بالنقاط، وسيتولّى البوت تنفيذ الطلبات تلقائياً. آلاف الخدمات منظّمة حسب المنصّة (إنستقرام · تيك توك · يوتيوب · تليجرام · X · فيسبوك …) مع بحث بالكلمة وترتيب من الأرخص. 🛠 الخدمات المحلية أضف خدمات تديرها بنفسك بدون أي مزوّد خارجي. الطلبات تصلك في قناتك مع أزرار: ✅ ت

30👨‍💻6👏4🔥1

8 May 2026, 11:11 UTC≈24,200 views42 reactionsread 12 August 2026

🚀 NEW UPDATE - Contact Bot ⚡ Action card under every user message: 👤 Info + stats + note 📝 Private notes per user 🚫 Ban · 🔇 Mute · ⏰ Snooze · 📌 Pin Smart toggle buttons that auto-flip ⏰ Snooze with duration picker (1h/4h/tomorrow/week) + auto-reminder when time's up 📎 Quick replies + smart suggestion: Bot suggests the best template from your user's message keywords, or shows the full list as /r1 /r2 /r3 buttons 🧭

29🔥6👨‍💻5👏2

8 May 2026, 11:08 UTC≈17,200 views21 reactionsread 12 August 2026

🚀 تحديث - بوت التواصل 🗑 حذف من الجهتين بضغطة واحدة ما يُحذف من جهتك: ✅ كل الرسائل الموجّهة من المستخدم ✅ كل بطاقات الإجراءات ✅ كل ردودك المرسلة ما يُحذف من جهة المستخدم: ✅ رسائله الأصلية (نعم! من جهته) ✅ كل ردودك التي وصلته ✅ رسائل /r القوالب ✅ رسالة الترحيب /start ✅ رسالة الاستلام التلقائية ✅ تنبيه الحظر شاشة التأكيد توضح بدقة: • من محادثتك: 47 • من محادثة المستخدم: 23 ⚠️ قيد تيليجرام: البوتات تستطيع حذف رسائله

19👏2

8 May 2026, 11:07 UTC≈15,500 views16 reactionsread 12 August 2026

🚀 تحديث - بوت التواصل 🎯 ميزات تفاعلية احترافية 🪞 مرآة التفاعلات: تتفاعل مع الرسالة المحوّلة في محادثتك → التفاعل ينعكس على رسالة المستخدم الأصلية تلقائياً تجربة محادثة طبيعية بين شخصين 🎯 إيموجي الاستلام: البوت يضع إيموجي تلقائياً على كل رسالة مستخدم • 67 إيموجي مدعوم • اختر واحد بضغطة من القائمة • أقل إزعاجاً من رسالة "تم الاستلام" 📤 توجيه لقناة عامة: • أضف البوت كأدمن في القناة • أرسل @username أو وجّه رسالة • ز

12🔥4

8 May 2026, 11:06 UTC≈14,300 views15 reactionsread 12 August 2026

🚀 تحديث - بوت التواصل 🧭 6 أنماط توزيع للأدمنية 📣 إرسال للجميع (افتراضي): كل أدمن يرى الرسالة، أول من يرد يقفل المحادثة، البطاقات تختفي من البقية تلقائياً 🎲 عشوائي ثابت: لكل مستخدم أدمن واحد، يبقى ثابت (sticky) 30 يوم ⚖️ حسب الحمل: يختار الأدمن الأقل انشغالاً (يحسب المحادثات النشطة) 🔄 تدوير (Round Robin): المستخدم التالي → الأدمن التالي بالترتيب، توزيع متساوٍ تماماً 🕐 حسب ساعات الدوام: لكل أدمن وقت دوامه، خارج و

15

8 May 2026, 11:04 UTC≈12,800 viewsread 12 August 2026

🚀 تحديث - بوت التواصل 📎 قوالب جاهزة + اقتراح ذكي تلقائي ⚡ الاقتراح الذكي: • البوت يحلل كلمات رسالة المستخدم • يحذف الكلمات الشائعة (من، على، the، a) • يقارن مع كل قالب محفوظ • يعرض الأفضل تحت بطاقة الرسالة • شروط: تطابق ≥ 2 كلمة أو ≥ 40% 📋 قائمة كاملة عند عدم التطابق: [/r1 شكراً] [/r2 السعر] [/r3 وقت العمل] 3 أزرار في الصف، إيموجي للوسائط (📷 / 🎥) 3 طرق إرسال: 1️⃣ أمر نصي: رد على الرسالة بـ /r1 /r2 2️⃣ ضغطة على ⚡

8 May 2026, 11:04 UTC≈12,300 views6 reactionsread 12 August 2026

🚀 تحديث - بوت التواصل ⏰ "خذها بعدين، ذكّرني" منتقي مدة بضغطة: • 1h / 4h / غداً / بعد 3 أيام / أسبوع التذكير التلقائي: • عند انقضاء المدة يصلك تذكير 💤 • زرّان: 👤 فتح البطاقة / ⏰ تأجيل مرة أخرى • مرتبط بالرسالة الأصلية للسياق العرض في كل مكان: ✅ بطاقة المعلومات (حالة + مدة متبقية) ✅ بطاقة كل رسالة جديدة من المستخدم ✅ زر التأجيل (✓ يظهر إذا فعّال) 🆚 الفرق: 🔇 كتم: الرسائل تختفي صامتة ⏰ تأجيل: الرسائل تصلك + تذكير 🚫

6

8 May 2026, 11:02 UTC≈11,200 views13 reactionsread 12 August 2026

🚀 تحديث - بوت التواصل ⚡ بطاقة أزرار تحت كل رسالة من المستخدم كل عملية بضغطة بدون كتابة أوامر: 👤 معلومات شاملة عن المستخدم: • اسم + ID + بايو + صورة • 📊 إحصائيات (عدد الرسائل، آخر تواصل، آخر رد) • 📝 الملاحظة المحفوظة • 🟢/🚫/🔇/💤 حالة المستخدم بأيقونات 📝 ملاحظة خاصة (تظهر في كل بطاقة دائماً) 🚫 حظر مع شاشة تأكيد + سجل كامل 🔇 كتم 24 ساعة ⏰ تأجيل بمنتقي مدة 📌 تثبيت في محادثتك أزرار توگل ذكية: حالتها تتبدّل تلقائياً (✅

6🔥3👏2👨‍💻2

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

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.

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

“echo | Telegram Bots” (@echomaker), 489,939 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/echomaker.

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.