Telegram RegisterThe public register of Telegram
Telegram profile photo for BSWEEDY

Channel

BSWEEDY

@bsweedy_one

Has discussion group

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

123,006subscribers

-556 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001786132536
TypeChannel
Username@bsweedy_one
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/bsweedy_one

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 9 August 2026 and assigned it the closest of 31 fixed categories, at 77% 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

123,006124,962123,9847 August 2026 — 123,562 subscribers7 August 2026 — 123,577 subscribers8 August 2026 — 124,002 subscribers9 August 2026 — 124,182 subscribers9 August 2026 — 124,182 subscribers10 August 2026 — 124,287 subscribers11 August 2026 — 124,498 subscribers12 August 2026 — 124,634 subscribers13 August 2026 — 124,772 subscribers14 August 2026 — 124,875 subscribers16 August 2026 — 124,962 subscribers17 August 2026 — 124,908 subscribers18 August 2026 — 124,774 subscribers19 August 2026 — 124,585 subscribers20 August 2026 — 124,558 subscribers22 August 2026 — 124,390 subscribers24 August 2026 — 124,292 subscribers25 August 2026 — 124,166 subscribers26 August 2026 — 124,110 subscribers27 August 2026 — 124,100 subscribers28 August 2026 — 123,899 subscribers29 August 2026 — 123,824 subscribers29 August 2026 — 123,772 subscribers30 August 2026 — 123,739 subscribers31 August 2026 — 123,627 subscribers1 September 2026 — 123,471 subscribers3 September 2026 — 123,247 subscribers4 September 2026 — 123,033 subscribers7 September 2026 — 123,299 subscribers10 September 2026 — 123,409 subscribers12 September 2026 — 123,344 subscribers14 September 2026 — 123,333 subscribers15 September 2026 — 123,205 subscribers18 September 2026 — 123,006 subscribers7 August 202618 September 2026
34 measurements spanning 42 days, net -556. 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 122,713–125,255 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 03:39123,006-199
15 Sept 2026, 21:18123,205-128
14 Sept 2026, 05:01123,333-11
12 Sept 2026, 13:20123,344-65
10 Sept 2026, 09:17123,409+110
7 Sept 2026, 03:36123,299+266
4 Sept 2026, 10:57123,033-214
3 Sept 2026, 00:52123,247-224
1 Sept 2026, 19:43123,471-156
31 Aug 2026, 20:14123,627-112
30 Aug 2026, 21:54123,739-33
29 Aug 2026, 23:17123,772-52
29 Aug 2026, 02:45123,824-75
28 Aug 2026, 05:26123,899-201
27 Aug 2026, 03:45124,100-10
26 Aug 2026, 06:53124,110-56
25 Aug 2026, 04:54124,166-126
24 Aug 2026, 04:49124,292-98
22 Aug 2026, 10:05124,390-168
20 Aug 2026, 22:43124,558first reading

Engagement

No public post preview. We read this entry on 9 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.

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

“BSWEEDY” (@bsweedy_one), 123,006 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/bsweedy_one.

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.