Telegram RegisterThe public register of Telegram
Telegram profile photo for DropMail.me

Bot

DropMail.me

@DropmailBot

On this record: Topic · Growth · Engagement · Citations · Referenced elsewhere · Cite this entry

39,113monthly users

+16,007 since we began measuring on 5 August 2026

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

Register entry

Telegram ID223734258
TypeBot
Username@DropmailBot
First recorded15 August 2026
Last confirmed live25 September 2026
Measurements held24
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/DropmailBot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Growth

22,70539,11330,9095 August 2026 — 23,106 monthly users6 August 2026 — 22,705 monthly users9 August 2026 — 23,300 monthly users12 August 2026 — 23,191 monthly users15 August 2026 — 23,191 monthly users16 August 2026 — 23,699 monthly users17 August 2026 — 23,768 monthly users18 August 2026 — 23,335 monthly users19 August 2026 — 23,916 monthly users20 August 2026 — 23,945 monthly users23 August 2026 — 23,925 monthly users25 August 2026 — 28,537 monthly users26 August 2026 — 29,002 monthly users27 August 2026 — 29,712 monthly users28 August 2026 — 30,503 monthly users31 August 2026 — 31,270 monthly users2 September 2026 — 32,204 monthly users3 September 2026 — 32,610 monthly users8 September 2026 — 33,873 monthly users11 September 2026 — 35,796 monthly users13 September 2026 — 36,617 monthly users14 September 2026 — 36,784 monthly users16 September 2026 — 37,538 monthly users25 September 2026 — 39,113 monthly users5 August 202625 September 2026
24 measurements spanning 50 days, net +16,007. 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 20,244–41,574 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 24
Measured (UTC)Monthly usersChange
25 Sept 2026, 10:5839,113+1,575
16 Sept 2026, 12:5737,538+754
14 Sept 2026, 19:5736,784+167
13 Sept 2026, 03:1736,617+821
11 Sept 2026, 07:4135,796+1,923
8 Sept 2026, 12:5633,873+1,263
3 Sept 2026, 10:0232,610+406
2 Sept 2026, 03:5832,204+934
31 Aug 2026, 00:1331,270+767
28 Aug 2026, 23:4330,503+791
27 Aug 2026, 21:1429,712+710
26 Aug 2026, 02:1729,002+465
25 Aug 2026, 01:3428,537+4,612
23 Aug 2026, 13:5323,925-20
20 Aug 2026, 14:0723,945+29
19 Aug 2026, 14:1223,916+581
18 Aug 2026, 12:4323,335-433
17 Aug 2026, 15:0723,768+69
16 Aug 2026, 06:5423,699+508
15 Aug 2026, 19:2223,191first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

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.

Mentions

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

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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Hacker News

This handle was named once in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.

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

“DropMail.me” (@DropmailBot), 39,113 monthly users as measured 25 September 2026. Telegram Register, tgregister.com/channel/DropmailBot.

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.