Telegram RegisterThe public register of Telegram
Telegram profile photo for HILIYA SIGNAL GROUP

Channel

HILIYA SIGNAL GROUP

@HILIYASIGNALGROUP65

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

6,113subscribers

+216 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-1002067648938
TypeChannel
Username@HILIYASIGNALGROUP65
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live4 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/HILIYASIGNALGROUP65

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 60% 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

5,8956,1256,0107 August 2026 — 5,897 subscribers7 August 2026 — 5,895 subscribers10 August 2026 — 5,904 subscribers13 August 2026 — 5,900 subscribers17 August 2026 — 5,982 subscribers20 August 2026 — 6,044 subscribers23 August 2026 — 6,081 subscribers27 August 2026 — 6,075 subscribers29 August 2026 — 6,075 subscribers30 August 2026 — 6,083 subscribers2 September 2026 — 6,097 subscribers6 September 2026 — 6,086 subscribers11 September 2026 — 6,084 subscribers14 September 2026 — 6,081 subscribers19 September 2026 — 6,082 subscribers29 September 2026 — 6,074 subscribers6 October 2026 — 6,075 subscribers12 October 2026 — 6,069 subscribers15 October 2026 — 6,067 subscribers18 October 2026 — 6,125 subscribers21 October 2026 — 6,115 subscribers23 October 2026 — 6,118 subscribers26 October 2026 — 6,104 subscribers30 October 2026 — 6,113 subscribers1 November 2026 — 6,115 subscribers4 November 2026 — 6,113 subscribers6,1137 August 20264 November 2026
26 measurements spanning 89 days, net +216. 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 5,861–6,160 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
4 Nov 2026, 15:156,113-2
1 Nov 2026, 22:156,115+2
30 Oct 2026, 04:296,113+9
26 Oct 2026, 23:386,104-14
23 Oct 2026, 22:366,118+3
21 Oct 2026, 07:486,115-10
18 Oct 2026, 15:386,125+58
15 Oct 2026, 22:296,067-2
12 Oct 2026, 23:576,069-6
6 Oct 2026, 19:416,075+1
29 Sept 2026, 11:026,074-8
19 Sept 2026, 02:396,082+1
14 Sept 2026, 13:206,081-3
11 Sept 2026, 04:206,084-2
6 Sept 2026, 13:596,086-11
2 Sept 2026, 01:056,097+14
30 Aug 2026, 08:436,083+8
29 Aug 2026, 12:186,075no change
27 Aug 2026, 03:556,075-6
23 Aug 2026, 19:146,081first reading

Engagement

No public post preview. We read this entry on 4 November 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.

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.

Whitetiger Siginal Group
@alaminfreesiginal · 37,988
Telegram ranks this channel #3 of 83 here — alongside 82 others — read 30 August 2026
Sea of Satoshi 💧(CTO)
@sea_of_satoshi · 31,403
Telegram ranks this channel #11 of 83 here — alongside 82 others — read 4 September 2026
Arewa Trading Academy
@arewatradingacademyO1 · 52,489
Telegram ranks this channel #15 of 86 here — alongside 85 others — read 24 August 2026
BYB TRADING ACADEMY📊
@BYBtradingacademy · 20,878
Telegram ranks this channel #32 of 71 here — alongside 70 others — read 24 September 2026
Panther Airdrops
@PantherAirdropsz · 58,901
Telegram ranks this channel #42 of 60 here — alongside 59 others — read 20 August 2026
Sheikh Bashir Ahmad Sani Sokoto
@Sheikhbashirahmadsokoto · 29,943
Telegram ranks this channel #50 of 64 here — alongside 63 others — read 9 September 2026
WAZOBIA CRYPTO
@wazobiacryptoo · 74,856
Telegram ranks this channel #61 of 86 here — alongside 85 others — read 24 August 2026
XM Trading Academy
@ahmedfreesignals · 302,138
Telegram ranks this channel #64 of 88 here — alongside 87 others — read 11 August 2026

This channel appears in 8 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“HILIYA SIGNAL GROUP” (@HILIYASIGNALGROUP65), 6,113 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/HILIYASIGNALGROUP65.

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.