Telegram RegisterThe public register of Telegram
Telegram profile photo for کانال توی هاواسی

Channel

کانال توی هاواسی

@toyha

On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

8,204subscribers

+119 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001092127061
TypeChannel
Username@toyha
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live12 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/toyha

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 why it has no browse page of its own yet.

Growth

8,0858,2158,1506 August 2026 — 8,085 subscribers10 August 2026 — 8,090 subscribers14 August 2026 — 8,097 subscribers17 August 2026 — 8,107 subscribers20 August 2026 — 8,124 subscribers24 August 2026 — 8,136 subscribers25 August 2026 — 8,136 subscribers26 August 2026 — 8,146 subscribers29 August 2026 — 8,156 subscribers2 September 2026 — 8,174 subscribers5 September 2026 — 8,185 subscribers10 September 2026 — 8,201 subscribers18 September 2026 — 8,215 subscribers27 September 2026 — 8,193 subscribers5 October 2026 — 8,207 subscribers12 October 2026 — 8,204 subscribers8,2046 August 202612 October 2026
16 measurements spanning 66 days, net +119. 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 8,066–8,235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 00:598,204-3
5 Oct 2026, 07:018,207+14
27 Sept 2026, 05:388,193-22
18 Sept 2026, 05:558,215+14
10 Sept 2026, 19:598,201+16
5 Sept 2026, 22:018,185+11
2 Sept 2026, 01:338,174+18
29 Aug 2026, 19:178,156+10
26 Aug 2026, 21:458,146+10
25 Aug 2026, 11:408,136no change
24 Aug 2026, 05:298,136+12
20 Aug 2026, 20:478,124+17
17 Aug 2026, 14:058,107+10
14 Aug 2026, 00:088,097+7
10 Aug 2026, 11:438,090+5
6 Aug 2026, 15:448,085first reading

Engagement

No public post preview. We read this entry on 25 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

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.

Dj.Fariba1
@arez932 · 20,713
Telegram ranks this channel #13 of 71 here — alongside 70 others — read 25 September 2026
چَرخِش | 𝑪𝒉𝒂𝒓𝒌𝒉𝒆𝒔𝒔𝒉 |
@Charkhessh · 821,544
Telegram ranks this channel #13 of 60 here — alongside 59 others — read 12 August 2026
آهنگ جدید ترکی
@muz_icbay · 30,483
Telegram ranks this channel #26 of 60 here — alongside 59 others — read 8 September 2026
موزیک شاد آهنگ جدید
@MusicShad · 90,806
Telegram ranks this channel #57 of 79 here — alongside 78 others — read 17 August 2026
HEYDJ اهنگ ریمیکس پادکست
@HEYDEJAY · 60,366
Telegram ranks this channel #61 of 76 here — alongside 75 others — read 23 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“کانال توی هاواسی” (@toyha), 8,204 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/toyha.

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.