Channel
Trap BeaTs بیت ترپ
@y6w4v
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,500subscribers
+63 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001908897860 |
|---|---|
| Type | Channel |
| Username | @y6w4v |
| Created | Between 1 March 2023 and 31 December 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/y6w4v |
Topic
Music — 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 28 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 |
|---|---|---|
| 1 Oct 2026, 00:19 | 1,500 | +7 |
| 28 Sept 2026, 03:09 | 1,493 | no change |
| 16 Sept 2026, 14:59 | 1,493 | +3 |
| 12 Sept 2026, 13:57 | 1,490 | +5 |
| 8 Sept 2026, 22:18 | 1,485 | +4 |
| 3 Sept 2026, 06:34 | 1,481 | +7 |
| 31 Aug 2026, 10:34 | 1,474 | +6 |
| 28 Aug 2026, 01:38 | 1,468 | +11 |
| 25 Aug 2026, 06:36 | 1,457 | +8 |
| 22 Aug 2026, 12:42 | 1,449 | +11 |
| 18 Aug 2026, 21:34 | 1,438 | +1 |
| 18 Aug 2026, 11:45 | 1,437 | 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.
@wzmusic · 20,001
Telegram ranks this channel #2 of 68 here — alongside 67 others — read 29 September 2026
@beatgeram · 42,288
Telegram ranks this channel #52 of 78 here — alongside 77 others — read 30 August 2026
@vinak · 179,606
Telegram ranks this channel #53 of 54 here — alongside 53 others — read 31 August 2026
@RezaPishro_pishro · 23,810
Telegram ranks this channel #57 of 67 here — alongside 66 others — read 17 September 2026
@beatkhor · 23,390
Telegram ranks this channel #62 of 70 here — alongside 69 others — read 18 September 2026
@PlugBeat · 51,591
Telegram ranks this channel #65 of 76 here — alongside 75 others — read 28 August 2026
@beatrapofficial · 89,993
Telegram ranks this channel #76 of 86 here — alongside 85 others — read 18 August 2026
This channel appears in 7 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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Trap BeaTs بیت ترپ” (@y6w4v), 1,500 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/y6w4v.
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.