Channel
XXXTENTACION | اکس اکس اکس تنتاسیون
@FullArchive_xxxtentacion
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,104subscribers
+85 since we began measuring on 5 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001757416494 |
|---|---|
| Type | Channel |
| Username | @FullArchive_xxxtentacion |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/FullArchive_xxxtentacion |
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 20 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 00:44 | 2,104 | -1 |
| 3 Nov 2026, 09:30 | 2,105 | -7 |
| 31 Oct 2026, 17:34 | 2,112 | -2 |
| 28 Oct 2026, 14:15 | 2,114 | +3 |
| 25 Oct 2026, 23:27 | 2,111 | +4 |
| 22 Oct 2026, 22:16 | 2,107 | +3 |
| 19 Oct 2026, 15:54 | 2,104 | -3 |
| 16 Oct 2026, 11:08 | 2,107 | +2 |
| 13 Oct 2026, 20:31 | 2,105 | +8 |
| 8 Oct 2026, 18:22 | 2,097 | +7 |
| 2 Oct 2026, 14:20 | 2,090 | +31 |
| 20 Sept 2026, 02:30 | 2,059 | no change |
| 16 Sept 2026, 19:36 | 2,059 | +12 |
| 12 Sept 2026, 11:55 | 2,047 | +19 |
| 8 Sept 2026, 19:35 | 2,028 | +9 |
| 5 Sept 2026, 12:47 | 2,019 | 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.
@music_hub_xxx · 52,057
Telegram ranks this channel #27 of 36 here — alongside 35 others — read 5 September 2026
@DariushTaraneh · 26,914
Telegram ranks this channel #34 of 66 here — alongside 65 others — read 10 September 2026
@Ehaamofficial · 30,954
Telegram ranks this channel #38 of 59 here — alongside 58 others — read 15 September 2026
@new_medical · 21,603
Telegram ranks this channel #79 of 81 here — alongside 80 others — read 23 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“XXXTENTACION | اکس اکس اکس تنتاسیون” (@FullArchive_xxxtentacion), 2,104 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/FullArchive_xxxtentacion.
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.