Channel
فروش اکانت کپکات | کپ کات پرو | کپکات پرو | Cap Cut Pro
@Kpopllyr
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,388subscribers
-671 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002016130662 |
|---|---|
| Type | Channel |
| Username | @Kpopllyr |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/Kpopllyr |
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 86% 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 |
|---|---|---|
| 24 Oct 2026, 02:06 | 3,388 | -33 |
| 20 Oct 2026, 22:06 | 3,421 | -38 |
| 17 Oct 2026, 16:05 | 3,459 | -34 |
| 14 Oct 2026, 19:55 | 3,493 | -59 |
| 11 Oct 2026, 17:39 | 3,552 | -154 |
| 5 Oct 2026, 11:40 | 3,706 | -112 |
| 27 Sept 2026, 20:39 | 3,818 | -117 |
| 15 Sept 2026, 11:56 | 3,935 | -7 |
| 12 Sept 2026, 06:59 | 3,942 | -28 |
| 7 Sept 2026, 16:16 | 3,970 | -25 |
| 5 Sept 2026, 20:27 | 3,995 | no change |
| 2 Sept 2026, 22:38 | 3,995 | -31 |
| 30 Aug 2026, 19:44 | 4,026 | -9 |
| 28 Aug 2026, 01:18 | 4,035 | -21 |
| 24 Aug 2026, 22:27 | 4,056 | -3 |
| 23 Aug 2026, 16:00 | 4,059 | 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.
@World_davini2 · 53,038
Telegram ranks this channel #11 of 59 here — alongside 58 others — read 23 August 2026
@lyricvibe_x · 22,722
Telegram ranks this channel #15 of 58 here — alongside 57 others — read 17 September 2026
@ayate_mood · 62,782
Telegram ranks this channel #19 of 52 here — alongside 51 others — read 25 August 2026
@moonmusicdark · 24,664
Telegram ranks this channel #22 of 50 here — alongside 49 others — read 14 September 2026
This channel appears in 4 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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“فروش اکانت کپکات | کپ کات پرو | کپکات پرو | Cap Cut Pro” (@Kpopllyr), 3,388 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/Kpopllyr.
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.