Telegram RegisterThe public register of Telegram
Telegram profile photo for FIRSTBELL CA CHAT

Supergroup

FIRSTBELL CA CHAT

@firstbellcachat

Has discussion group

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

7,737members

+0 since we began measuring on 26 August 2026

321 online right now

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

Register entry

Telegram ID-1001882747173
TypeSupergroup
Username@firstbellcachat
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live27 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/firstbellcachat

Growth

7,73726 Aug 2026, 21:46 — 7,737 members27 Aug 2026, 03:53 — 7,737 members26 Aug 2026, 21:4627 Aug 2026, 03:53
2 measurements taken within a single day. 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 7,729–7,745 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
27 Aug 2026, 03:537,737no change
26 Aug 2026, 21:467,737first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Citation-graph rank

Citation-graph rank — 335,711 of 1,621,120entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“FIRSTBELL CA CHAT” (@firstbellcachat), 7,737 members as measured 27 August 2026. Telegram Register, tgregister.com/channel/firstbellcachat.

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.