
Channel
Insomnia
@pinsomniia
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,690subscribers
+195 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001166172611 |
|---|---|
| Type | Channel |
| Username | @pinsomniia |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/pinsomniia |
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 14 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 |
|---|---|---|
| 17 Nov 2026, 06:12 | 3,690 | -4 |
| 7 Nov 2026, 17:47 | 3,694 | -1 |
| 2 Nov 2026, 04:28 | 3,695 | -4 |
| 29 Oct 2026, 21:41 | 3,699 | -1 |
| 27 Oct 2026, 06:28 | 3,700 | -6 |
| 24 Oct 2026, 15:31 | 3,706 | -1 |
| 21 Oct 2026, 16:16 | 3,707 | -2 |
| 18 Oct 2026, 22:51 | 3,709 | -1 |
| 15 Oct 2026, 16:39 | 3,710 | -2 |
| 12 Oct 2026, 11:46 | 3,712 | -4 |
| 6 Oct 2026, 00:16 | 3,716 | +235 |
| 28 Sept 2026, 21:20 | 3,481 | -8 |
| 15 Sept 2026, 23:58 | 3,489 | +3 |
| 12 Sept 2026, 01:57 | 3,486 | -3 |
| 8 Sept 2026, 00:55 | 3,489 | no change |
| 7 Sept 2026, 17:37 | 3,489 | +3 |
| 3 Sept 2026, 00:53 | 3,486 | -1 |
| 27 Aug 2026, 08:37 | 3,487 | -3 |
| 24 Aug 2026, 14:58 | 3,490 | -2 |
| 20 Aug 2026, 17:04 | 3,492 | 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.
@XtexicX · 20,088
Telegram ranks this channel #14 of 55 here — alongside 54 others — read 26 September 2026
@the_heelia · 19,083
Telegram ranks this channel #30 of 81 here — alongside 80 others — read 3 October 2026
@TehBeatz · 23,016
Telegram ranks this channel #36 of 66 here — alongside 65 others — read 18 September 2026
@djfere · 259,797
Telegram ranks this channel #54 of 72 here — alongside 71 others — read 11 August 2026
@donyayeproject · 81,744
Telegram ranks this channel #62 of 65 here — alongside 64 others — read 26 August 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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Insomnia” (@pinsomniia), 3,690 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/pinsomniia.
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.