Channel
ENTRY HUNTERS 💎
@entry_hunterss
On this record: Growth · Engagement · Telegram's recommendations · Cite this entry
7,002subscribers
-83 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001786515164 |
|---|---|
| Type | Channel |
| Username | @entry_hunterss |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/entry_hunterss |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 08:38 | 7,002 | -22 |
| 30 Aug 2026, 07:33 | 7,024 | -9 |
| 27 Aug 2026, 11:42 | 7,033 | no change |
| 27 Aug 2026, 07:55 | 7,033 | -2 |
| 24 Aug 2026, 11:32 | 7,035 | -9 |
| 20 Aug 2026, 18:58 | 7,044 | -15 |
| 18 Aug 2026, 03:34 | 7,059 | -8 |
| 15 Aug 2026, 02:23 | 7,067 | -19 |
| 11 Aug 2026, 19:57 | 7,086 | +1 |
| 11 Aug 2026, 11:15 | 7,085 | 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.
@mrpfxuniversity · 48,234
Telegram ranks this channel #9 of 77 here — alongside 76 others — read 26 August 2026
@theforexbulls · 106,095
Telegram ranks this channel #10 of 78 here — alongside 77 others — read 15 August 2026
@stunnnerv75freetelegram · 40,598
Telegram ranks this channel #20 of 73 here — alongside 72 others — read 30 August 2026
@FXGOAT1 · 114,883
Telegram ranks this channel #25 of 84 here — alongside 83 others — read 14 August 2026
@kojoforextrades · 286,404
Telegram ranks this channel #25 of 85 here — alongside 84 others — read 11 August 2026
@FXGOAT0 · 104,028
Telegram ranks this channel #27 of 81 here — alongside 80 others — read 16 August 2026
@habbyforex · 305,557
Telegram ranks this channel #34 of 85 here — alongside 84 others — read 11 August 2026
@Thecoffiefxlll · 38,127
Telegram ranks this channel #43 of 79 here — alongside 78 others — read 31 August 2026
@yoforexgold · 143,601
Telegram ranks this channel #55 of 74 here — alongside 73 others — read 12 August 2026
@firepipsignals · 237,248
Telegram ranks this channel #65 of 83 here — alongside 82 others — read 11 August 2026
@alexsetandforget · 213,429
Telegram ranks this channel #72 of 80 here — alongside 79 others — read 11 August 2026
@KingFtpForex · 49,289
Telegram ranks this channel #81 of 86 here — alongside 85 others — read 25 August 2026
This channel appears in 12 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“ENTRY HUNTERS 💎” (@entry_hunterss), 7,002 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/entry_hunterss.
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.