
Channel
Declan Tyler
@declantylerchannen
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,773subscribers
-51 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001687270425 |
|---|---|
| Type | Channel |
| Username | @declantylerchannen |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/declantylerchannen |
Topic
Other / unclassifiable — 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 100% 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 |
|---|---|---|
| 17 Sept 2026, 17:59 | 3,773 | +3 |
| 13 Sept 2026, 16:21 | 3,770 | -13 |
| 9 Sept 2026, 23:00 | 3,783 | -11 |
| 6 Sept 2026, 20:41 | 3,794 | no change |
| 4 Sept 2026, 07:56 | 3,794 | +1 |
| 31 Aug 2026, 15:47 | 3,793 | -12 |
| 28 Aug 2026, 10:42 | 3,805 | +6 |
| 25 Aug 2026, 19:39 | 3,799 | -3 |
| 22 Aug 2026, 16:26 | 3,802 | -10 |
| 19 Aug 2026, 03:13 | 3,812 | -9 |
| 15 Aug 2026, 19:52 | 3,821 | -3 |
| 14 Aug 2026, 22:15 | 3,824 | 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.
@betspace_01 · 61,664
Telegram ranks this channel #13 of 59 here — alongside 58 others — read 21 August 2026
@mateoLuca2024 · 27,301
Telegram ranks this channel #28 of 83 here — alongside 82 others — read 10 September 2026
@royalzone1 · 21,232
Telegram ranks this channel #31 of 79 here — alongside 78 others — read 24 September 2026
@Jc_Smith_Score · 24,615
Telegram ranks this channel #31 of 77 here — alongside 76 others — read 15 September 2026
@nextgoal2025 · 42,581
Telegram ranks this channel #36 of 82 here — alongside 81 others — read 29 August 2026
@Sport_Zone_BETS · 43,108
Telegram ranks this channel #38 of 79 here — alongside 78 others — read 28 August 2026
@fixedexpert · 272,959
Telegram ranks this channel #39 of 84 here — alongside 83 others — read 20 August 2026
@Jamesinfos1 · 42,214
Telegram ranks this channel #40 of 80 here — alongside 79 others — read 29 August 2026
@arsenalevent · 24,743
Telegram ranks this channel #41 of 83 here — alongside 82 others — read 15 September 2026
@FootballInfo00 · 23,943
Telegram ranks this channel #42 of 81 here — alongside 80 others — read 17 September 2026
@Maximox700 · 31,429
Telegram ranks this channel #42 of 80 here — alongside 79 others — read 6 September 2026
@Level_up_bets · 34,254
Telegram ranks this channel #42 of 81 here — alongside 80 others — read 3 September 2026
@highscorechannel · 66,493
Telegram ranks this channel #43 of 85 here — alongside 84 others — read 19 August 2026
@diegomanipulated · 53,800
Telegram ranks this channel #44 of 81 here — alongside 80 others — read 24 August 2026
@bettingbrainzz · 38,526
Telegram ranks this channel #46 of 83 here — alongside 82 others — read 31 August 2026
@USAsecretbets · 38,839
Telegram ranks this channel #50 of 82 here — alongside 81 others — read 31 August 2026
@fixedmatch_Team · 64,229
Telegram ranks this channel #51 of 81 here — alongside 80 others — read 21 August 2026
@Cristian_iinfo_79 · 104,825
Telegram ranks this channel #56 of 87 here — alongside 86 others — read 14 August 2026
@Raul_BetHub · 42,130
Telegram ranks this channel #57 of 82 here — alongside 81 others — read 29 August 2026
@free_matches_free_bets · 49,757
Telegram ranks this channel #65 of 80 here — alongside 79 others — read 25 August 2026
@leakers_org · 79,981
Telegram ranks this channel #65 of 83 here — alongside 82 others — read 18 August 2026
@neymarfixed · 73,459
Telegram ranks this channel #69 of 87 here — alongside 86 others — read 18 August 2026
@Xmatches · 64,117
Telegram ranks this channel #71 of 87 here — alongside 86 others — read 21 August 2026
@DarkBets_info · 102,710
Telegram ranks this channel #73 of 80 here — alongside 79 others — read 15 August 2026
This channel appears in 26 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Declan Tyler” (@declantylerchannen), 3,773 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/declantylerchannen.
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.