Telegram RegisterThe public register of Telegram
Telegram profile photo for hiss removal

Channel

hiss removal

@hissremoval

On this record: Growth · Engagement · Citations · Cite this entry

669subscribers

+17 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-1001006374358
TypeChannel
Username@hissremoval
Descriptionличный архив
Created26 November 2015 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 October 2026
Last confirmed live10 October 2026
Measurements held9
On Telegramt.me/hissremoval

Growth

652671661.56 August 2026 — 652 subscribers13 August 2026 — 658 subscribers20 August 2026 — 659 subscribers27 August 2026 — 657 subscribers2 September 2026 — 662 subscribers12 September 2026 — 666 subscribers26 September 2026 — 671 subscribers6 October 2026 — 669 subscribers10 October 2026 — 669 subscribers6696 August 202610 October 2026
9 measurements spanning 65 days, net +17. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 649–674 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 19:42669no change
6 Oct 2026, 17:14669-2
26 Sept 2026, 18:41671+5
12 Sept 2026, 01:21666+4
2 Sept 2026, 19:44662+5
27 Aug 2026, 05:43657-2
20 Aug 2026, 21:16659+1
13 Aug 2026, 11:26658+6
6 Aug 2026, 12:01652first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“hiss removal” (@hissremoval), 669 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/hissremoval.

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.