Telegram RegisterThe public register of Telegram
Telegram profile photo for Piggy Bank 🏀

Bot

Piggy Bank 🏀

@piggybankgamebot

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

24,216monthly users

-832 since we began measuring on 6 August 2026

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

Register entry

Telegram ID7070093783
TypeBot
Username@piggybankgamebot
First recorded15 August 2026
Last confirmed live7 November 2026
Measurements held45
Confirmed unchanged3 times, most recently 7 November 2026
On Telegramt.me/piggybankgamebot

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

17,51225,04821,2806 August 2026 — 25,048 monthly users8 August 2026 — 24,886 monthly users9 August 2026 — 24,375 monthly users11 August 2026 — 23,901 monthly users12 August 2026 — 23,574 monthly users13 August 2026 — 23,315 monthly users14 August 2026 — 22,722 monthly users15 August 2026 — 22,722 monthly users16 August 2026 — 18,143 monthly users17 August 2026 — 18,578 monthly users18 August 2026 — 18,395 monthly users19 August 2026 — 17,818 monthly users20 August 2026 — 17,512 monthly users21 August 2026 — 17,577 monthly users22 August 2026 — 17,707 monthly users24 August 2026 — 17,715 monthly users27 August 2026 — 17,795 monthly users29 August 2026 — 18,039 monthly users30 August 2026 — 18,159 monthly users1 September 2026 — 18,544 monthly users2 September 2026 — 18,768 monthly users3 September 2026 — 18,859 monthly users5 September 2026 — 19,054 monthly users8 September 2026 — 19,199 monthly users11 September 2026 — 24,223 monthly users13 September 2026 — 23,953 monthly users14 September 2026 — 24,420 monthly users18 September 2026 — 24,321 monthly users25 September 2026 — 24,068 monthly users3 October 2026 — 23,337 monthly users8 October 2026 — 23,633 monthly users12 October 2026 — 22,913 monthly users14 October 2026 — 22,630 monthly users15 October 2026 — 23,127 monthly users16 October 2026 — 23,084 monthly users20 October 2026 — 22,730 monthly users21 October 2026 — 22,278 monthly users22 October 2026 — 22,704 monthly users23 October 2026 — 22,659 monthly users24 October 2026 — 22,658 monthly users28 October 2026 — 22,856 monthly users31 October 2026 — 22,228 monthly users1 November 2026 — 23,100 monthly users3 November 2026 — 23,941 monthly users5 November 2026 — 24,216 monthly users24,2166 August 20265 November 2026
45 measurements spanning 91 days, net -832. 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 16,382–26,178 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 45
Measured (UTC)Monthly usersChange
5 Nov 2026, 11:4724,216+275
3 Nov 2026, 14:5523,941+841
1 Nov 2026, 15:0623,100+872
31 Oct 2026, 12:0522,228-628
28 Oct 2026, 15:4622,856+198
24 Oct 2026, 18:0122,658-1
23 Oct 2026, 19:1122,659-45
22 Oct 2026, 18:4122,704+426
21 Oct 2026, 14:0422,278-452
20 Oct 2026, 08:5022,730-354
16 Oct 2026, 11:5823,084-43
15 Oct 2026, 11:4923,127+497
14 Oct 2026, 09:4622,630-283
12 Oct 2026, 19:5022,913-720
8 Oct 2026, 10:4123,633+296
3 Oct 2026, 23:1523,337-731
25 Sept 2026, 05:3824,068-253
18 Sept 2026, 21:1524,321-99
14 Sept 2026, 14:3724,420+467
13 Sept 2026, 03:5523,953first 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 103 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 22 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“Piggy Bank 🏀” (@piggybankgamebot), 24,216 monthly users as measured 5 November 2026. Telegram Register, tgregister.com/channel/piggybankgamebot.

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.