Channel
ππΌπΆπΎπ π πΈπ
@picksrey
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
1,641subscribers
-45 since we began measuring on 23 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1001447042488 |
|---|---|
| Type | Channel |
| Username | @picksrey |
| Created | Between 1 April 2019 and 31 October 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/picksrey |
Topic
Gambling & betting β 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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 |
|---|---|---|
| 12 Oct 2026, 17:06 | 1,641 | -8 |
| 6 Oct 2026, 12:41 | 1,649 | -5 |
| 29 Sept 2026, 04:42 | 1,654 | -7 |
| 25 Sept 2026, 02:53 | 1,661 | no change |
| 18 Sept 2026, 21:57 | 1,661 | -3 |
| 14 Sept 2026, 12:41 | 1,664 | -5 |
| 10 Sept 2026, 16:39 | 1,669 | -4 |
| 5 Sept 2026, 19:16 | 1,673 | -6 |
| 1 Sept 2026, 20:47 | 1,679 | -2 |
| 29 Aug 2026, 12:05 | 1,681 | -4 |
| 26 Aug 2026, 16:43 | 1,685 | -1 |
| 23 Aug 2026, 06:45 | 1,686 | first 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.
Appears in Telegramβs recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly β each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone elseβs query is independent of having been queried itself.
@MarcoReyTelegram Β· 36,487
Telegram ranks this channel #21 of 81 here β alongside 80 others β read 1 September 2026
@LosReyesApp Β· 53,789
Telegram ranks this channel #26 of 78 here β alongside 77 others β read 23 August 2026
@NBA_NFL_props Β· 52,076
Telegram ranks this channel #34 of 76 here β alongside 75 others β read 2 September 2026
@GrupoReyPicks Β· 66,750
Telegram ranks this channel #35 of 77 here β alongside 76 others β read 23 August 2026
@cristianrey0 Β· 26,998
Telegram ranks this channel #38 of 80 here β alongside 79 others β read 11 September 2026
@ChicoDolarStake10gratis Β· 24,031
Telegram ranks this channel #50 of 65 here β alongside 64 others β read 19 September 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegramβs list for THAT channel, not this one β see how this is measured.
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.
βππΌπΆπΎπ π πΈπβ (@picksrey), 1,641 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/picksrey.
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.