Telegram RegisterThe public register of Telegram
Telegram profile photo for PLU2Barcode Bot

Bot

PLU2Barcode Bot

@plu2barcode_bot

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

42,156monthly users

+613 since we began measuring on 7 August 2026

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

Register entry

Telegram ID7249687162
TypeBot
Username@plu2barcode_bot
First recorded12 August 2026
Last confirmed live25 August 2026
Measurements held11
Confirmed unchanged2 times, most recently 25 August 2026
On Telegramt.me/plu2barcode_bot

Growth

41,43842,37541,906.57 August 2026 — 41,543 monthly users8 August 2026 — 41,438 monthly users11 August 2026 — 41,510 monthly users12 August 2026 — 41,558 monthly users12 August 2026 — 41,558 monthly users14 August 2026 — 41,697 monthly users17 August 2026 — 41,830 monthly users18 August 2026 — 42,375 monthly users20 August 2026 — 42,073 monthly users23 August 2026 — 42,100 monthly users24 August 2026 — 42,156 monthly users42,1567 August 202624 August 2026
11 measurements spanning 17 days, net +613. 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 41,297–42,516 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
24 Aug 2026, 20:5742,156+56
23 Aug 2026, 05:4742,100+27
20 Aug 2026, 10:2242,073-302
18 Aug 2026, 10:0442,375+545
17 Aug 2026, 10:1841,830+133
14 Aug 2026, 09:1441,697+139
12 Aug 2026, 20:0541,558no change
12 Aug 2026, 02:1241,558+48
11 Aug 2026, 02:2141,510+72
8 Aug 2026, 23:0141,438-105
7 Aug 2026, 22:4341,543first 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 1 registered channel — 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.

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

“PLU2Barcode Bot” (@plu2barcode_bot), 42,156 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/plu2barcode_bot.

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.