Telegram RegisterThe public register of Telegram
Telegram profile photo for Livegram Bot

Bot

Livegram Bot

@LivegramBot

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

1,024,999monthly users

+39,931 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID179449893
TypeBot
Username@LivegramBot
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/LivegramBot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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

962,6521,062,0391,012,345.55 August 2026 — 985,068 monthly users6 August 2026 — 985,068 monthly users6 August 2026 — 982,903 monthly users7 August 2026 — 982,606 monthly users9 August 2026 — 985,573 monthly users10 August 2026 — 987,860 monthly users11 August 2026 — 990,122 monthly users12 August 2026 — 962,652 monthly users13 August 2026 — 962,911 monthly users14 August 2026 — 992,459 monthly users16 August 2026 — 993,808 monthly users17 August 2026 — 995,432 monthly users18 August 2026 — 994,097 monthly users19 August 2026 — 993,163 monthly users20 August 2026 — 992,782 monthly users22 August 2026 — 995,668 monthly users23 August 2026 — 999,939 monthly users25 August 2026 — 1,013,805 monthly users25 August 2026 — 1,032,856 monthly users27 August 2026 — 1,018,871 monthly users28 August 2026 — 1,059,204 monthly users29 August 2026 — 1,058,438 monthly users30 August 2026 — 1,061,201 monthly users31 August 2026 — 1,062,039 monthly users1 September 2026 — 1,058,133 monthly users2 September 2026 — 1,055,766 monthly users4 September 2026 — 1,016,246 monthly users7 September 2026 — 1,044,297 monthly users10 September 2026 — 1,040,829 monthly users12 September 2026 — 1,003,180 monthly users14 September 2026 — 1,001,802 monthly users15 September 2026 — 1,028,490 monthly users18 September 2026 — 1,024,999 monthly users1,024,9995 August 202618 September 2026
33 measurements spanning 43 days, net +39,931. 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 947,744–1,076,947 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 33
Measured (UTC)Monthly usersChange
18 Sept 2026, 02:021,024,999-3,491
15 Sept 2026, 22:381,028,490+26,688
14 Sept 2026, 04:161,001,802-1,378
12 Sept 2026, 13:401,003,180-37,649
10 Sept 2026, 12:001,040,829-3,468
7 Sept 2026, 04:171,044,297+28,051
4 Sept 2026, 09:571,016,246-39,520
2 Sept 2026, 22:381,055,766-2,367
1 Sept 2026, 23:471,058,133-3,906
31 Aug 2026, 23:181,062,039+838
30 Aug 2026, 22:551,061,201+2,763
29 Aug 2026, 23:121,058,438-766
28 Aug 2026, 22:551,059,204+40,333
27 Aug 2026, 01:441,018,871-13,985
25 Aug 2026, 23:071,032,856+19,051
25 Aug 2026, 02:031,013,805+13,866
23 Aug 2026, 13:13999,939+4,271
22 Aug 2026, 00:47995,668+2,886
20 Aug 2026, 19:38992,782-381
19 Aug 2026, 21:45993,163first 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 143 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Livegram Bot” (@LivegramBot), 1,024,999 monthly users as measured 18 September 2026. Telegram Register, tgregister.com/channel/LivegramBot.

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.