2 Sept 2023, 19:42 UTC≈5,180 viewsread 10 August 2026
https://t.me/+DC2lIlJufrMxYmIy
Channel
V
@nxxxr
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
46subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001166008038 |
|---|---|
| Type | Channel |
| Username | @nxxxr |
| Created | 15 June 2018 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/nxxxr |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 10 Oct 2026, 05:41 | 46 | -1 |
| 14 Sept 2026, 20:40 | 47 | -1 |
| 29 Aug 2026, 00:12 | 48 | -1 |
| 21 Aug 2026, 07:44 | 49 | +1 |
| 13 Aug 2026, 12:35 | 48 | -2 |
| 10 Aug 2026, 11:16 | 50 | no change |
| 6 Aug 2026, 04:17 | 50 | first reading |
Engagement
6 posts held, back to 15 June 2018 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 2 September 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
8 Jul 2022, 08:21 UTC≈7,940 viewsread 10 August 2026
@shhoh_69
23 Jan 2019, 16:05 UTC≈30,200 viewsread 10 August 2026
.
20 Jul 2018, 06:02 UTC≈34,200 viewsread 10 August 2026
طبو هنا 😘👆
20 Jul 2018, 06:02 UTC≈34,300 viewsread 10 August 2026
https://t.me/joinchat/AAAAAE53x7D3Xsr35eD8Cg
15 Jun 2018, 03:40 UTCviews —
Channel created
Showing the 6 most recent of 6 posts we hold for @nxxxr. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Mentions
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“V” (@nxxxr), 46 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/nxxxr.
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.