Telegram RegisterThe public register of Telegram
Telegram profile photo for بوت همسه 📨

Bot

بوت همسه 📨

@ililbot

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

40,160monthly users

+6,538 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 ID6004302579
TypeBot
Username@ililbot
First recorded13 August 2026
Last confirmed live31 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/ililbot

Growth

33,58840,16036,8746 August 2026 — 33,622 monthly users8 August 2026 — 33,588 monthly users9 August 2026 — 33,615 monthly users11 August 2026 — 34,016 monthly users12 August 2026 — 34,338 monthly users13 August 2026 — 34,338 monthly users14 August 2026 — 35,262 monthly users17 August 2026 — 35,557 monthly users18 August 2026 — 35,747 monthly users19 August 2026 — 35,810 monthly users20 August 2026 — 35,423 monthly users22 August 2026 — 36,731 monthly users24 August 2026 — 37,261 monthly users26 August 2026 — 38,238 monthly users27 August 2026 — 38,611 monthly users29 August 2026 — 39,561 monthly users31 August 2026 — 40,160 monthly users6 August 202631 August 2026
17 measurements spanning 25 days, net +6,538. 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 32,602–41,146 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
31 Aug 2026, 02:2640,160+599
29 Aug 2026, 02:2539,561+950
27 Aug 2026, 03:3638,611+373
26 Aug 2026, 05:1138,238+977
24 Aug 2026, 07:0837,261+530
22 Aug 2026, 17:2736,731+1,308
20 Aug 2026, 06:4535,423-387
19 Aug 2026, 09:3535,810+63
18 Aug 2026, 12:0735,747+190
17 Aug 2026, 13:0735,557+295
14 Aug 2026, 12:4835,262+924
13 Aug 2026, 19:1334,338no change
12 Aug 2026, 01:3334,338+322
11 Aug 2026, 02:2534,016+401
9 Aug 2026, 02:2133,615+27
8 Aug 2026, 02:2533,588-34
6 Aug 2026, 14:2133,622first 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 4 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 31 August 2026 — this entry's latest reading, not the date you are reading this.

“بوت همسه 📨” (@ililbot), 40,160 monthly users as measured 31 August 2026. Telegram Register, tgregister.com/channel/ililbot.

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.