Channel
POUND KING FOREX COMMUNITY
@poundking_community
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,962subscribers
-113 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001645007045 |
|---|---|
| Type | Channel |
| Username | @poundking_community |
| Created | Between 1 December 2021 and 31 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/poundking_community |
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 14 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 10:40 | 3,962 | -8 |
| 10 Sept 2026, 11:19 | 3,970 | -20 |
| 5 Sept 2026, 15:56 | 3,990 | -23 |
| 5 Sept 2026, 13:34 | 4,013 | no change |
| 1 Sept 2026, 15:43 | 4,013 | -7 |
| 29 Aug 2026, 18:52 | 4,020 | -5 |
| 27 Aug 2026, 05:15 | 4,025 | -5 |
| 23 Aug 2026, 19:54 | 4,030 | -10 |
| 20 Aug 2026, 11:33 | 4,040 | -2 |
| 17 Aug 2026, 18:29 | 4,042 | -7 |
| 14 Aug 2026, 19:15 | 4,049 | -8 |
| 11 Aug 2026, 07:06 | 4,057 | -12 |
| 8 Aug 2026, 07:53 | 4,069 | -6 |
| 7 Aug 2026, 12:25 | 4,075 | 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.
@tradewithpatfree · 77,473
Telegram ranks this channel #12 of 89 here — alongside 88 others — read 19 August 2026
@IAMSAIGEx · 33,567
Telegram ranks this channel #27 of 79 here — alongside 78 others — read 4 September 2026
@LittlePandaForex · 32,257
Telegram ranks this channel #29 of 79 here — alongside 78 others — read 14 September 2026
@mrpfxuniversity · 48,154
Telegram ranks this channel #35 of 77 here — alongside 76 others — read 26 August 2026
@kira_forex · 32,156
Telegram ranks this channel #51 of 86 here — alongside 85 others — read 5 September 2026
This channel appears in 5 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“POUND KING FOREX COMMUNITY” (@poundking_community), 3,962 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/poundking_community.
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.