Channel
✝️Christian Music trap HOUSE
@christianmusictraphouse
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,499subscribers
-48 since we began measuring on 8 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001165484901 |
|---|---|
| Type | Channel |
| Username | @christianmusictraphouse |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/christianmusictraphouse |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 09:50 | 2,499 | -6 |
| 4 Nov 2026, 18:28 | 2,505 | -6 |
| 1 Nov 2026, 13:38 | 2,511 | -2 |
| 29 Oct 2026, 21:09 | 2,513 | -4 |
| 26 Oct 2026, 22:06 | 2,517 | -4 |
| 23 Oct 2026, 17:27 | 2,521 | -2 |
| 21 Oct 2026, 01:09 | 2,523 | -7 |
| 17 Oct 2026, 23:06 | 2,530 | -5 |
| 15 Oct 2026, 00:31 | 2,535 | -10 |
| 11 Oct 2026, 20:42 | 2,545 | +1 |
| 5 Oct 2026, 09:37 | 2,544 | -4 |
| 27 Sept 2026, 07:15 | 2,548 | -7 |
| 18 Sept 2026, 02:17 | 2,555 | +5 |
| 15 Sept 2026, 01:16 | 2,550 | no change |
| 14 Sept 2026, 06:59 | 2,550 | +3 |
| 8 Sept 2026, 04:47 | 2,547 | 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.
@ghanaianchmusic · 34,977
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 8 September 2026
@biblebooks777 · 30,483
Telegram ranks this channel #38 of 87 here — alongside 86 others — read 8 September 2026
@DownloadKoinoniaSermons · 21,443
Telegram ranks this channel #50 of 71 here — alongside 70 others — read 23 September 2026
@Clibraryforyou · 19,254
Telegram ranks this channel #73 of 85 here — alongside 84 others — read 3 October 2026
@theophilus35 · 47,690
Telegram ranks this channel #73 of 82 here — alongside 81 others — read 8 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“✝️Christian Music trap HOUSE” (@christianmusictraphouse), 2,499 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/christianmusictraphouse.
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.