Telegram RegisterThe public register of Telegram
Telegram profile photo for Weisses Armband

Channel

Weisses Armband

@weissesarmband

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

9,581subscribers

-147 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001340193197
TypeChannel
Username@weissesarmband
Created23 June 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded23 August 2026
Last confirmed live19 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/weissesarmband

Topic

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

9,5819,7289,654.56 August 2026 — 9,728 subscribers10 August 2026 — 9,718 subscribers13 August 2026 — 9,708 subscribers16 August 2026 — 9,695 subscribers19 August 2026 — 9,692 subscribers23 August 2026 — 9,684 subscribers23 August 2026 — 9,684 subscribers26 August 2026 — 9,669 subscribers30 August 2026 — 9,658 subscribers2 September 2026 — 9,646 subscribers6 September 2026 — 9,631 subscribers11 September 2026 — 9,618 subscribers14 September 2026 — 9,598 subscribers19 September 2026 — 9,581 subscribers6 August 202619 September 2026
14 measurements spanning 44 days, net -147. 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 9,559–9,750 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 09:219,581-17
14 Sept 2026, 20:389,598-20
11 Sept 2026, 10:009,618-13
6 Sept 2026, 07:429,631-15
2 Sept 2026, 03:139,646-12
30 Aug 2026, 02:349,658-11
26 Aug 2026, 15:469,669-15
23 Aug 2026, 11:209,684no change
23 Aug 2026, 07:289,684-8
19 Aug 2026, 08:469,692-3
16 Aug 2026, 17:439,695-13
13 Aug 2026, 02:249,708-10
10 Aug 2026, 01:259,718-10
6 Aug 2026, 09:409,728first reading

Engagement

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

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

“Weisses Armband” (@weissesarmband), 9,581 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/weissesarmband.

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.