Telegram RegisterThe public register of Telegram
Telegram profile photo for Q Anon Army: One Squad Under God of Digital Souldiers.

Channel

Q Anon Army: One Squad Under God of Digital Souldiers.

@freedomunion_1

Has discussion group

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

3,070subscribers

-72 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001337029197
TypeChannel
Username@freedomunion_1
Created17 January 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 September 2026
Last confirmed live17 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/freedomunion_1

Topic

Politics & activism — 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 14 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

3,0703,1423,1067 August 2026 — 3,142 subscribers10 August 2026 — 3,136 subscribers12 August 2026 — 3,133 subscribers16 August 2026 — 3,125 subscribers19 August 2026 — 3,121 subscribers23 August 2026 — 3,116 subscribers26 August 2026 — 3,111 subscribers29 August 2026 — 3,109 subscribers1 September 2026 — 3,099 subscribers4 September 2026 — 3,091 subscribers10 September 2026 — 3,084 subscribers10 September 2026 — 3,084 subscribers13 September 2026 — 3,076 subscribers17 September 2026 — 3,070 subscribers7 August 202617 September 2026
14 measurements spanning 41 days, net -72. 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 3,059–3,153 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 04:563,070-6
13 Sept 2026, 13:423,076-8
10 Sept 2026, 23:373,084no change
10 Sept 2026, 00:423,084-7
4 Sept 2026, 23:193,091-8
1 Sept 2026, 16:333,099-10
29 Aug 2026, 13:573,109-2
26 Aug 2026, 07:533,111-5
23 Aug 2026, 06:053,116-5
19 Aug 2026, 11:533,121-4
16 Aug 2026, 17:233,125-8
12 Aug 2026, 23:023,133-3
10 Aug 2026, 08:403,136-6
7 Aug 2026, 00:193,142first 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.

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.

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

“Q Anon Army: One Squad Under God of Digital Souldiers.” (@freedomunion_1), 3,070 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/freedomunion_1.

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.