24 Jul 2026, 14:18 UTC19 viewsread 11 August 2026
— Да ладно тебе! Бывает *Титан улыбается. Спустя время они подошли к поясу Койпера и Титан прошагнул через астероиды, ведя за собой Луну*
![Telegram profile photo for Titan [NSFW]](https://cdn.tgregister.com/av/7f/7ffa1711eea475308f96842ada7ad4936924ee3b7bed0735cf8d23ce0d008cea.jpg)
Channel
Titan [NSFW]
@Titan_nsfw_ask
On this record: Growth · Engagement · Posts · Citations · Cite this entry
16subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003893945863 |
|---|---|
| Type | Channel |
| Username | @Titan_nsfw_ask |
| Created | Between 1 February 2026 and 17 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Titan_nsfw_ask |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 04:38 | 16 | +1 |
| 26 Aug 2026, 00:53 | 15 | -1 |
| 11 Aug 2026, 22:30 | 16 | no change |
| 11 Aug 2026, 15:15 | 16 | first reading |
Engagement
20 posts held, back to 17 July 2026 — 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 20 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
24 Jul 2026, 12:11 UTC9 viewsread 11 August 2026
Forwarded from @nsfwayy
Ивент окончен
22 Jul 2026, 11:33 UTC23 viewsread 11 August 2026
— Что за глупый вопрос? Это потому, что я ваш лидер.
22 Jul 2026, 00:07 UTC24 viewsread 11 August 2026
— Тебе повезло. Я редко отлучался ещё куда-то, кроме собраний спутников *Говорил Титан, пока шёл, перебирая руками и смотря по сторонам"
22 Jul 2026, 00:00 UTC20 viewsread 11 August 2026
— Серьёзно? Ладно, давай "Пояс Койпера это далеко не близко, но если погулять, то можно. Титан захватил с собой по пути бинокль, который прямо сейчас висит у него на шее" — Ты когда-то был там?
21 Jul 2026, 23:47 UTC19 viewsread 11 August 2026
Сапп : простите за неактив! Буду исправляться
21 Jul 2026, 23:46 UTC20 viewsread 11 August 2026
— Какая ещё погода в космосе? :/ Ну да ладно, тогда давай выходи, мне надо за собой ещё всё проверить. *Титан проверил включена ли вода, газ или свет. Убедившись, что все в порядке, он закрыл за ними двумя входную дверь" — Итак. Куда держим путь?
20 Jul 2026, 06:45 UTC21 viewsread 11 August 2026
— Можем прогуляться? Снаружи норм вроде *Титан убрал шахматы в сторону*
18 Jul 2026, 23:29 UTC21 viewsread 11 August 2026
*Спустя множество ходов Луна всё-таки выиграл Титана, отчего тот вскинул руками и мотнул головой* — Ну, ладно, это было неплохо. Чем ещё займёмся?
18 Jul 2026, 21:56 UTC21 viewsread 11 August 2026
*Титан с самым глупо-сосредоточенным лицом и надеждой съедает его пешку напротив своей*
18 Jul 2026, 19:34 UTC22 viewsread 11 August 2026
*Внимательно следя за ходом Луны, Титан походил королём вплотную к стене (с6)*
18 Jul 2026, 19:12 UTC20 viewsread 11 August 2026
*Титан ходит пешкой по середине. Он решил начать с малого*
Showing the 12 most recent of 20 posts we hold for @Titan_nsfw_ask. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Titan [NSFW]” (@Titan_nsfw_ask), 16 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Titan_nsfw_ask.
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.