Telegram RegisterThe public register of Telegram
Telegram profile photo for Bulge

Channel

Bulge

@bulge

Has discussion group

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

10,909subscribers

+10 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001057671481
TypeChannel
Username@bulge
Created26 December 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded21 August 2026
Last confirmed live25 August 2026
Measurements held19
Confirmed unchanged2 times, most recently 25 August 2026
On Telegramt.me/bulge

Previous handles

Recorded in 2019 as “Bulge (join @bulge_chat!) — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

Growth

10,89410,90910,901.55 August 2026 — 10,899 subscribers6 August 2026 — 10,900 subscribers7 August 2026 — 10,902 subscribers8 August 2026 — 10,903 subscribers9 August 2026 — 10,899 subscribers10 August 2026 — 10,900 subscribers11 August 2026 — 10,898 subscribers12 August 2026 — 10,899 subscribers13 August 2026 — 10,894 subscribers14 August 2026 — 10,897 subscribers16 August 2026 — 10,896 subscribers17 August 2026 — 10,901 subscribers18 August 2026 — 10,904 subscribers19 August 2026 — 10,900 subscribers20 August 2026 — 10,906 subscribers21 August 2026 — 10,904 subscribers21 August 2026 — 10,904 subscribers22 August 2026 — 10,906 subscribers24 August 2026 — 10,909 subscribers5 August 202624 August 2026
19 measurements spanning 18 days, net +10. 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 10,892–10,911 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 11:1610,909+3
22 Aug 2026, 21:1710,906+2
21 Aug 2026, 21:2210,904no change
21 Aug 2026, 09:2610,904-2
20 Aug 2026, 10:3810,906+6
19 Aug 2026, 13:4410,900-4
18 Aug 2026, 13:1510,904+3
17 Aug 2026, 16:4510,901+5
16 Aug 2026, 08:0310,896-1
14 Aug 2026, 15:3510,897+3
13 Aug 2026, 06:5410,894-5
12 Aug 2026, 08:5210,899+1
11 Aug 2026, 06:4810,898-2
10 Aug 2026, 09:5010,900+1
9 Aug 2026, 10:3110,899-4
8 Aug 2026, 08:0210,903+1
7 Aug 2026, 07:4210,902+2
6 Aug 2026, 10:1010,900+1
5 Aug 2026, 23:1710,899first reading

Engagement

No public post preview. We read this entry on 22 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Citation-graph rank

Citation-graph rank — 335,617 of 1,602,868entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Bulge” (@bulge), 10,909 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/bulge.

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.