Telegram RegisterThe public register of Telegram
Telegram profile photo for آرشیو آزمون و کتاب

Bot

آرشیو آزمون و کتاب

@gimiupbot

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

39,171monthly users

+2,087 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 ID6669720812
TypeBot
Username@gimiupbot
First recorded13 August 2026
Last confirmed live3 September 2026
Measurements held19
Confirmed unchanged2 times, most recently 3 September 2026
On Telegramt.me/gimiupbot

Growth

35,99939,17137,5857 August 2026 — 37,084 monthly users10 August 2026 — 37,746 monthly users12 August 2026 — 37,920 monthly users13 August 2026 — 37,920 monthly users13 August 2026 — 37,154 monthly users14 August 2026 — 36,806 monthly users16 August 2026 — 36,699 monthly users18 August 2026 — 36,824 monthly users20 August 2026 — 36,435 monthly users21 August 2026 — 35,999 monthly users22 August 2026 — 36,168 monthly users25 August 2026 — 36,420 monthly users26 August 2026 — 37,314 monthly users28 August 2026 — 37,812 monthly users29 August 2026 — 38,118 monthly users30 August 2026 — 38,243 monthly users31 August 2026 — 37,760 monthly users1 September 2026 — 38,133 monthly users2 September 2026 — 39,171 monthly users7 August 20262 September 2026
19 measurements spanning 26 days, net +2,087. 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 35,523–39,647 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
2 Sept 2026, 10:0839,171+1,038
1 Sept 2026, 10:3738,133+373
31 Aug 2026, 13:5737,760-483
30 Aug 2026, 10:5538,243+125
29 Aug 2026, 12:1338,118+306
28 Aug 2026, 11:0737,812+498
26 Aug 2026, 13:4237,314+894
25 Aug 2026, 13:3536,420+252
22 Aug 2026, 21:1536,168+169
21 Aug 2026, 09:0735,999-436
20 Aug 2026, 10:4436,435-389
18 Aug 2026, 13:2436,824+125
16 Aug 2026, 07:4636,699-107
14 Aug 2026, 17:5936,806-348
13 Aug 2026, 08:1537,154-766
13 Aug 2026, 02:4937,920no change
12 Aug 2026, 06:2337,920+174
10 Aug 2026, 07:0037,746+662
7 Aug 2026, 11:1637,084first 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 10 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“آرشیو آزمون و کتاب” (@gimiupbot), 39,171 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/gimiupbot.

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.