Telegram RegisterThe public register of Telegram
Telegram profile photo for $PEPE Miner 🐸

Bot

$PEPE Miner 🐸

@pepesminerbot

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

34,353monthly users

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

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

Register entry

Telegram ID8309078565
TypeBot
Username@pepesminerbot
First recorded13 August 2026
Last confirmed live6 November 2026
Measurements held52
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/pepesminerbot

Topic

Crypto & trading — 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 51% 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.

Growth

34,02449,66841,8466 August 2026 — 36,880 monthly users6 August 2026 — 37,177 monthly users7 August 2026 — 37,370 monthly users9 August 2026 — 37,835 monthly users10 August 2026 — 38,922 monthly users11 August 2026 — 39,650 monthly users13 August 2026 — 40,803 monthly users13 August 2026 — 40,803 monthly users14 August 2026 — 41,156 monthly users15 August 2026 — 41,379 monthly users16 August 2026 — 40,651 monthly users17 August 2026 — 40,442 monthly users19 August 2026 — 40,890 monthly users20 August 2026 — 41,319 monthly users22 August 2026 — 44,403 monthly users24 August 2026 — 45,076 monthly users25 August 2026 — 45,294 monthly users26 August 2026 — 45,728 monthly users27 August 2026 — 45,986 monthly users28 August 2026 — 46,210 monthly users30 August 2026 — 47,791 monthly users31 August 2026 — 48,023 monthly users1 September 2026 — 47,949 monthly users2 September 2026 — 48,324 monthly users6 September 2026 — 49,512 monthly users10 September 2026 — 49,668 monthly users12 September 2026 — 48,404 monthly users14 September 2026 — 47,888 monthly users15 September 2026 — 46,850 monthly users17 September 2026 — 45,811 monthly users28 September 2026 — 43,393 monthly users5 October 2026 — 39,671 monthly users9 October 2026 — 38,508 monthly users13 October 2026 — 38,027 monthly users15 October 2026 — 37,932 monthly users16 October 2026 — 37,947 monthly users18 October 2026 — 37,963 monthly users19 October 2026 — 37,982 monthly users20 October 2026 — 37,792 monthly users22 October 2026 — 37,423 monthly users24 October 2026 — 37,275 monthly users25 October 2026 — 37,182 monthly users25 October 2026 — 37,109 monthly users26 October 2026 — 34,963 monthly users27 October 2026 — 34,898 monthly users30 October 2026 — 34,024 monthly users30 October 2026 — 34,688 monthly users1 November 2026 — 34,714 monthly users3 November 2026 — 34,251 monthly users4 November 2026 — 34,273 monthly users5 November 2026 — 34,452 monthly users6 November 2026 — 34,353 monthly users34,3536 August 20266 November 2026
52 measurements spanning 92 days, net -2,527. 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 31,677–52,015 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 52
Measured (UTC)Monthly usersChange
6 Nov 2026, 02:5934,353-99
5 Nov 2026, 03:2534,452+179
4 Nov 2026, 00:3834,273+22
3 Nov 2026, 03:0934,251-463
1 Nov 2026, 02:2834,714+26
30 Oct 2026, 23:1434,688+664
30 Oct 2026, 01:4134,024-874
27 Oct 2026, 23:4534,898-65
26 Oct 2026, 22:5434,963-2,146
25 Oct 2026, 23:1537,109-73
25 Oct 2026, 01:5137,182-93
24 Oct 2026, 00:5637,275-148
22 Oct 2026, 22:4537,423-369
20 Oct 2026, 19:0637,792-190
19 Oct 2026, 18:5137,982+19
18 Oct 2026, 21:1937,963+16
16 Oct 2026, 23:5537,947+15
15 Oct 2026, 22:4637,932-95
13 Oct 2026, 14:1638,027-481
9 Oct 2026, 12:3538,508first 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.

Mentions

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

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

“$PEPE Miner 🐸” (@pepesminerbot), 34,353 monthly users as measured 6 November 2026. Telegram Register, tgregister.com/channel/pepesminerbot.

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.