Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Class Action Sue Facebook & Google

Channel

Crypto Class Action Sue Facebook & Google

@SueFacebook

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

48subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001444405312
TypeChannel
Username@SueFacebook
CreatedBetween 1 April 2019 and 23 April 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live3 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 3 October 2026
On Telegramt.me/SueFacebook

Topic

Crypto & trading — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 38% 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

484948.57 August 2026 — 49 subscribers10 August 2026 — 49 subscribers10 September 2026 — 48 subscribers7 August 202610 September 2026
3 measurements spanning 33 days, net -1. 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 48–49 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 02:1948-1
10 Aug 2026, 12:3049no change
7 Aug 2026, 23:4249first reading

Engagement

20 posts held, back to 23 April 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 13 December 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Dec 2023, 11:27 UTC168 viewsread 10 August 2026

https://peakd.com/cryptoclassaction/@apshamilton/crypto-class-action-update-two-good-things-and-one-bad

12 Dec 2023, 16:19 UTC149 viewsread 10 August 2026

https://www.zerohedge.com/technology/google-loses-every-count-play-store-antitrust-case-epic-games

19 Oct 2023, 13:06 UTC167 viewsread 10 August 2026

An Application for Leave to Appeal has been filed in relation to the 29 Sept Judgement of Cheeseman J. See https://peakd.com/cryptoclassaction/@apshamilton/hamilton-v-meta-platforms-inc-2023-fca-1148-crypto-class-action-appeal

19 Oct 2023, 13:05 UTC159 viewsread 10 August 2026
File

Hamilton v Meta Platforms, Inc. [2023] FCA 1148 Notice to Group Members and Token Holders

14 Sept 2023, 06:30 UTC167 viewsread 10 August 2026

Just an update: We are still awaiting Judgement from this 2-3 Feb hearing.

13 Dec 2022, 13:17 UTC248 viewsread 10 August 2026

https://peakd.com/cryptoclassaction/@apshamilton/my-submissions-for-feb-2023-hearing-in-crypto-class-action-part-3-3

13 Dec 2022, 13:16 UTC210 viewsread 10 August 2026

https://peakd.com/cryptoclassaction/@apshamilton/my-submissions-for-feb-2023-hearing-in-crypto-class-action-part-2-3

13 Dec 2022, 13:16 UTC181 viewsread 10 August 2026

My latest submissions in the Crypto Class Action. https://peakd.com/cryptoclassaction/@apshamilton/my-submissions-for-feb-2023-hearing-in-crypto-class-action-part-1-2

12 Jun 2022, 11:13 UTC205 viewsread 10 August 2026

On Friday afternoon the Federal Court of Australia handed down its first judgment in the Crypto Class Action, finding that there is a prima facie case against Facebook and Google and giving leave to serve them in the USA. This is an important first step in bringing Big Tech to justice for unlawful anti-competitive and cartel conduct in banning the ads of the cryptocurrency industry in early 2018. More detail can be f…

18 Oct 2021, 13:41 UTC252 viewsread 10 August 2026

https://peakd.com/cryptoclassaction/@apshamilton/the-end-of-the-beginning--and-the-beginning-of-the-end-for-facebook-and-google

5 Oct 2021, 17:38 UTC252 viewsread 10 August 2026

https://peakd.com/cryptoclassaction/@apshamilton/i-didnt-take-facebook-down-last-night-but-

20 Jun 2021, 13:05 UTC256 viewsread 10 August 2026

There was a 6 Month hiatus between Court hearings as the Judge was too busy. A New Judge has been appointed and things are moving forward again.

Showing the 12 most recent of 20 posts we hold for @SueFacebook. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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

“Crypto Class Action Sue Facebook & Google” (@SueFacebook), 48 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/SueFacebook.

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.