Telegram RegisterThe public register of Telegram
Telegram profile photo for Tadpole MTP

Channel

Tadpole MTP

@kedou_mtp

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

417subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001437885731
TypeChannel
Username@kedou_mtp
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/kedou_mtp

Growth

4174214197 August 2026 — 421 subscribers7 August 2026 — 421 subscribers15 August 2026 — 420 subscribers22 August 2026 — 419 subscribers29 August 2026 — 417 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net -4. 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 416–422 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 08:07417-2
22 Aug 2026, 20:16419-1
15 Aug 2026, 10:29420-1
7 Aug 2026, 17:48421no change
7 Aug 2026, 00:48421first reading

Engagement

20 posts held, back to 7 January 2022the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 July 2022. An engagement rate over an empty window would be a number about nothing.

Reaction mix

70 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 68.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4868.6%
🥰1318.6%
👎34.29%
🙏34.29%
👏22.86%
😁11.43%

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 12 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 70reactions 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 7 January 2022 to 9 July 2022, 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 Jul 2022, 13:39 UTCviews —

Tadpole MTP pinned «TG认证地址:http://104.208.117.134:80/add.php TG一键链接: https://t.me/proxy?server=104.208.117.134&port=443&secret=ee69e31c10119845fcaf12765a104f3c5b7777772e6d6963726f736f66742e636f6d TG认证地址:http://20.89.143.73/add.php TG一键链接: https://t.me/proxy?server=20.89.143…»

7 Jul 2022, 13:39 UTC≈4,220 views15 reactionsread 7 August 2026

TG认证地址:http://104.208.117.134:80/add.php TG一键链接: https://t.me/proxy?server=104.208.117.134&port=443&secret=ee69e31c10119845fcaf12765a104f3c5b7777772e6d6963726f736f66742e636f6d TG认证地址:http://20.89.143.73/add.php TG一键链接: https://t.me/proxy?server=20.89.143.73&port=443&secret=eef60fe04a6bb74fbb90fe13ae435f18c1646f7562616e2e636f6d @kedou_mtp

👍9🙏3👎2👏1

2 Jul 2022, 13:57 UTC≈4,260 viewsread 7 August 2026

白名单代理使用教程: 需点击添加白名单链接,(弹出页面后可以关闭,建议网页收藏)再点击TG一键链接,(不要开着梯子点认证!!!)网络变更后需要重新认证。

30 Jun 2022, 15:34 UTC≈2,940 views5 reactionsread 7 August 2026

这个号要没了 说实话 坚持这么长时间属实没想到 现在az号也不好买 且用且珍惜

👍3🥰2

17 Jun 2022, 10:57 UTC≈2,960 views1 reactionsread 7 August 2026

发现有人倒卖本频道的MTP,请立刻停止相关行为,如果在今晚12点前没有停止,将删除服务器。 it is found that someone resells the MTP of this channel, please stop the related behavior immediately. If it is not stopped before 12:00 tonight, the server will be deleted.

👏1

9 May 2022, 05:52 UTCviews —

Tadpole MTP pinned «http://20.89.143.73/add.php https://t.me/proxy?server=20.89.143.73&port=443&secret=eef60fe04a6bb74fbb90fe13ae435f18c1646f7562616e2e636f6d»

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

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

“Tadpole MTP” (@kedou_mtp), 417 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/kedou_mtp.

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.