Telegram RegisterThe public register of Telegram
Telegram profile photo for Hatred's Gambles Journal

Channel

Hatred's Gambles Journal

@hatredgambles

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

18subscribers

-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-1002025451374
TypeChannel
Username@hatredgambles
CreatedBetween 1 November 2023 and 23 March 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live16 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 16 September 2026
On Telegramt.me/hatredgambles

Growth

181918.57 August 2026 — 19 subscribers11 August 2026 — 19 subscribers9 September 2026 — 18 subscribers7 August 20269 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 18–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 00:1918-1
11 Aug 2026, 16:4719no change
7 Aug 2026, 11:2719first reading

Engagement

20 posts held, back to 23 March 2024the 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 24 August 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Aug 2024, 04:17 UTC48 viewsread 11 August 2026

Been a while since shared anything, so here goes, been looking at it and think it could go hard $MOW at 250k 54nfJ5GStW6xLbFwbsakwrFUcBhjcWBiS1j7qe6GHkad

7 Jun 2024, 16:09 UTC68 viewsread 11 August 2026

RK letting the shorts load up even more before popping up?

7 Jun 2024, 07:49 UTC47 viewsread 11 August 2026

All DFV-related tokens are mooning, but the most iconic item has to be the red headband $HBAND Price gonna reprice.

7 Jun 2024, 06:40 UTC34 viewsread 11 August 2026

$HBAND 2x now and not many people know about this yet 🤐

7 Jun 2024, 05:05 UTC32 viewsread 11 August 2026

Gonna scoop some $HBAND before the legend gets onto the livestream w his iconic headband today. First headband ticker from a few days ago, 80k mcap good R/R EJyaqmhRmjbdC9xi9Yj3dzDfWHdiRZdUrowfkFdZsc2B

29 May 2024, 06:27 UTC39 viewsread 11 August 2026

top holder and dev still holding, aped more here 200k mcap. Moon or dust

Showing the 12 most recent of 20 posts we hold for @hatredgambles. 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Hatred's Gambles Journal” (@hatredgambles), 18 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/hatredgambles.

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.