Telegram RegisterThe public register of Telegram
Telegram profile photo for Meest Пошта

Bot

Meest Пошта

@meestposhtomat_bot

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

69,169monthly users

+9,429 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 ID1480974941
TypeBot
Username@meestposhtomat_bot
First recorded11 August 2026
Last confirmed live7 September 2026
Measurements held21
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/meestposhtomat_bot

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 65% 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

58,79469,16963,981.57 August 2026 — 59,740 monthly users9 August 2026 — 58,794 monthly users10 August 2026 — 59,580 monthly users11 August 2026 — 59,580 monthly users12 August 2026 — 59,667 monthly users14 August 2026 — 60,054 monthly users15 August 2026 — 60,989 monthly users17 August 2026 — 60,474 monthly users18 August 2026 — 60,980 monthly users20 August 2026 — 62,010 monthly users22 August 2026 — 62,986 monthly users23 August 2026 — 63,493 monthly users25 August 2026 — 63,412 monthly users26 August 2026 — 63,604 monthly users27 August 2026 — 63,865 monthly users29 August 2026 — 66,359 monthly users30 August 2026 — 66,956 monthly users31 August 2026 — 66,195 monthly users2 September 2026 — 66,455 monthly users4 September 2026 — 67,435 monthly users7 September 2026 — 69,169 monthly users7 August 20267 September 2026
21 measurements spanning 31 days, net +9,429. 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 57,238–70,725 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 21
Measured (UTC)Monthly usersChange
7 Sept 2026, 14:5669,169+1,734
4 Sept 2026, 16:4167,435+980
2 Sept 2026, 00:3466,455+260
31 Aug 2026, 23:3666,195-761
30 Aug 2026, 23:5466,956+597
29 Aug 2026, 04:5766,359+2,494
27 Aug 2026, 05:0263,865+261
26 Aug 2026, 06:0363,604+192
25 Aug 2026, 03:1463,412-81
23 Aug 2026, 21:0763,493+507
22 Aug 2026, 05:5662,986+976
20 Aug 2026, 18:0362,010+1,030
18 Aug 2026, 18:3460,980+506
17 Aug 2026, 21:5260,474-515
15 Aug 2026, 16:5260,989+935
14 Aug 2026, 03:1560,054+387
12 Aug 2026, 19:4759,667+87
11 Aug 2026, 19:1559,580no change
10 Aug 2026, 20:5159,580+786
9 Aug 2026, 21:3158,794first 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.

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

“Meest Пошта” (@meestposhtomat_bot), 69,169 monthly users as measured 7 September 2026. Telegram Register, tgregister.com/channel/meestposhtomat_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.