30 Oct 2024, 20:37 UTC108 viewsread 29 August 2026
ну, допустим, мяу.
Signed hennessy. ᴴᴾᴿᴺ
Channel
порой хочется сдаться.
@phssh1
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
8subscribers
-1 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001954158964 |
|---|---|
| Type | Channel |
| Username | @phssh1 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/phssh1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 15:39 | 8 | -1 |
| 29 Aug 2026, 04:30 | 9 | no change |
| 29 Aug 2026, 04:15 | 9 | first reading |
Engagement
19 posts held, back to 22 August 2024 — 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 19 posts for this entry, the most recent from 30 October 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 5s
- Average length
- 5s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
25 Sept 2024, 20:27 UTC126 viewsread 29 August 2026
вечным сном
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:27 UTC126 viewsread 29 August 2026
надеюсь я скоро усну
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:22 UTC127 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:20 UTC127 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:16 UTC127 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:15 UTC125 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:12 UTC125 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:11 UTC115 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:09 UTC104 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:09 UTC83 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
25 Sept 2024, 20:04 UTC63 viewsread 29 August 2026
Voice message
Voice message, posted without a caption
Signed hennessy. ᴴᴾᴿᴺ
Showing the 12 most recent of 19 posts we hold for @phssh1. 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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“порой хочется сдаться.” (@phssh1), 8 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/phssh1.
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.