Telegram RegisterThe public register of Telegram
Telegram profile photo for EfshaGari 2

Bot

EfshaGari 2

@EfshaGarisbot

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

70,231monthly users

-11,227 since we began measuring on 1 September 2026

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

Register entry

Telegram ID1762951006
TypeBot
Username@EfshaGarisbot
First recorded1 September 2026
Last confirmed live19 September 2026
Measurements held8
Confirmed unchanged2 times, most recently 19 September 2026
On Telegramt.me/EfshaGarisbot

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 16 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 why it has no browse page of its own yet.

Growth

70,23195,45582,8431 September 2026 — 81,458 monthly users1 September 2026 — 81,458 monthly users2 September 2026 — 86,284 monthly users5 September 2026 — 95,455 monthly users8 September 2026 — 79,590 monthly users11 September 2026 — 76,085 monthly users13 September 2026 — 73,520 monthly users16 September 2026 — 70,231 monthly users1 September 202616 September 2026
8 measurements spanning 16 days, net -11,227. 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 66,447–99,239 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
16 Sept 2026, 20:5670,231-3,289
13 Sept 2026, 08:5573,520-2,565
11 Sept 2026, 14:3976,085-3,505
8 Sept 2026, 20:1779,590-15,865
5 Sept 2026, 14:3995,455+9,171
2 Sept 2026, 10:0486,284+4,826
1 Sept 2026, 11:4081,458no change
1 Sept 2026, 00:0081,458first 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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“EfshaGari 2” (@EfshaGarisbot), 70,231 monthly users as measured 16 September 2026. Telegram Register, tgregister.com/channel/EfshaGarisbot.

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.