Channel
شــِ💩ـت تست ها
@shit_testha
On this record: Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
6,837subscribers
+56 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002047961420 |
|---|---|
| Type | Channel |
| Username | @shit_testha |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/shit_testha |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 23:06 | 6,837 | -5 |
| 27 Aug 2026, 20:58 | 6,842 | no change |
| 26 Aug 2026, 19:23 | 6,842 | +9 |
| 23 Aug 2026, 08:38 | 6,833 | -3 |
| 20 Aug 2026, 05:37 | 6,836 | +7 |
| 17 Aug 2026, 11:14 | 6,829 | +11 |
| 13 Aug 2026, 13:58 | 6,818 | +25 |
| 10 Aug 2026, 11:52 | 6,793 | +12 |
| 7 Aug 2026, 17:03 | 6,781 | 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.
Mentions
Named by 2 registered channels — 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.
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.
@jaraghe_jazb · 47,745
Telegram ranks this channel #8 of 70 here — alongside 69 others — read 26 August 2026
@iliaen · 248,856
Telegram ranks this channel #27 of 60 here — alongside 59 others — read 24 August 2026
@mastrybook · 86,460
Telegram ranks this channel #49 of 67 here — alongside 66 others — read 21 August 2026
This channel appears in 3 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“شــِ💩ـت تست ها” (@shit_testha), 6,837 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/shit_testha.
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.