Telegram RegisterThe public register of Telegram
Telegram profile photo for _ بوِتَ تحَميل سَتوريات من انِستا

Bot

_ بوِتَ تحَميل سَتوريات من انِستا

@Xxabot

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

31,600monthly users

+5,758 since we began measuring on 7 August 2026

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

Register entry

Telegram ID1359183784
TypeBot
Username@Xxabot
First recorded14 August 2026
Last confirmed live26 August 2026
Measurements held15
Confirmed unchanged2 times, most recently 26 August 2026
On Telegramt.me/Xxabot

Growth

25,61232,12128,866.57 August 2026 — 25,842 monthly users8 August 2026 — 26,332 monthly users10 August 2026 — 26,417 monthly users11 August 2026 — 26,594 monthly users13 August 2026 — 27,342 monthly users14 August 2026 — 27,342 monthly users14 August 2026 — 26,305 monthly users16 August 2026 — 26,285 monthly users17 August 2026 — 26,211 monthly users18 August 2026 — 26,114 monthly users19 August 2026 — 25,612 monthly users20 August 2026 — 32,121 monthly users22 August 2026 — 32,009 monthly users24 August 2026 — 31,914 monthly users25 August 2026 — 31,600 monthly users31,6007 August 202625 August 2026
15 measurements spanning 18 days, net +5,758. 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 24,636–33,097 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 10:1131,600-314
24 Aug 2026, 11:5731,914-95
22 Aug 2026, 18:4732,009-112
20 Aug 2026, 09:0232,121+6,509
19 Aug 2026, 12:2225,612-502
18 Aug 2026, 14:4526,114-97
17 Aug 2026, 13:0626,211-74
16 Aug 2026, 06:1226,285-20
14 Aug 2026, 20:1726,305-1,037
14 Aug 2026, 19:2927,342no change
13 Aug 2026, 11:3627,342+748
11 Aug 2026, 17:3126,594+177
10 Aug 2026, 16:2226,417+85
8 Aug 2026, 17:4226,332+490
7 Aug 2026, 04:1525,842first 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 5 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“_ بوِتَ تحَميل سَتوريات من انِستا” (@Xxabot), 31,600 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/Xxabot.

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.