Telegram RegisterThe public register of Telegram
Telegram profile photo for Rickler Alerts

Channel

Rickler Alerts

@rickler_alert

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

57subscribers

-2 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-1001670582897
TypeChannel
Username@rickler_alert
Created23 May 2023 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live25 October 2026
Measurements held5
Confirmed unchanged3 times, most recently 25 October 2026
On Telegramt.me/rickler_alert

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 97% 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 the other topics.

Growth

565957.57 August 2026 — 59 subscribers10 August 2026 — 59 subscribers24 August 2026 — 58 subscribers2 October 2026 — 56 subscribers12 October 2026 — 57 subscribers577 August 202612 October 2026
5 measurements spanning 66 days, net -2. 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 56–59 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 02:4157+1
2 Oct 2026, 11:5756-2
24 Aug 2026, 02:4258-1
10 Aug 2026, 05:3059no change
7 Aug 2026, 09:3659first reading

Engagement

12 posts held, back to 23 May 2023 — 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 12 posts for this entry, the most recent from 23 May 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 12 most recent of 12 posts we hold for @rickler_alert. 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.

Mentions

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

“Rickler Alerts” (@rickler_alert), 57 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/rickler_alert.

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.