https://www.strava.com/challenges/6212

Channel
Strava Challenges
@strava_challenges
On this record: Topic · Growth · Engagement · Posts · Cite this entry
3,157subscribers
+90 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001241754416 |
|---|---|
| Type | Channel |
| Username | @strava_challenges |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/strava_challenges |
Topic
Sports — 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 53% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 20:20 | 3,157 | +18 |
| 28 Sept 2026, 15:38 | 3,139 | +13 |
| 18 Sept 2026, 14:00 | 3,126 | +1 |
| 14 Sept 2026, 09:39 | 3,125 | +4 |
| 10 Sept 2026, 19:37 | 3,121 | +9 |
| 5 Sept 2026, 11:40 | 3,112 | +7 |
| 1 Sept 2026, 21:55 | 3,105 | +4 |
| 29 Aug 2026, 21:08 | 3,101 | +8 |
| 27 Aug 2026, 03:19 | 3,093 | +4 |
| 24 Aug 2026, 00:24 | 3,089 | +3 |
| 20 Aug 2026, 05:22 | 3,086 | +6 |
| 17 Aug 2026, 09:38 | 3,080 | -1 |
| 13 Aug 2026, 09:28 | 3,081 | +7 |
| 10 Aug 2026, 07:30 | 3,074 | +7 |
| 7 Aug 2026, 03:28 | 3,067 | no change |
| 6 Aug 2026, 17:45 | 3,067 | first reading |
Engagement
24 posts held, back to 30 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages 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 24 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://www.strava.com/challenges/6256
https://www.strava.com/challenges/6257
https://www.strava.com/challenges/6262
https://www.strava.com/challenges/6277
https://www.strava.com/challenges/6272
https://www.strava.com/challenges/6216
https://www.strava.com/challenges/6201
https://www.strava.com/challenges/6260
https://www.strava.com/challenges/6197
https://www.strava.com/challenges/6217
https://www.strava.com/challenges/6218
Showing the 12 most recent of 24 posts we hold for @strava_challenges. 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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“Strava Challenges” (@strava_challenges), 3,157 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/strava_challenges.
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.