
Channel
CE’
@waveeeye
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,905subscribers
-103 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002053686075 |
|---|---|
| Type | Channel |
| Username | @waveeeye |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/waveeeye |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 15:50 | 1,905 | -8 |
| 9 Nov 2026, 10:17 | 1,913 | -2 |
| 5 Nov 2026, 21:19 | 1,915 | -2 |
| 3 Nov 2026, 00:27 | 1,917 | -2 |
| 30 Oct 2026, 15:16 | 1,919 | -6 |
| 27 Oct 2026, 09:55 | 1,925 | -5 |
| 24 Oct 2026, 14:15 | 1,930 | -3 |
| 21 Oct 2026, 23:38 | 1,933 | -3 |
| 18 Oct 2026, 23:56 | 1,936 | -3 |
| 16 Oct 2026, 04:17 | 1,939 | -4 |
| 13 Oct 2026, 00:21 | 1,943 | -8 |
| 6 Oct 2026, 15:20 | 1,951 | -5 |
| 29 Sept 2026, 23:36 | 1,956 | -25 |
| 21 Sept 2026, 01:56 | 1,981 | no change |
| 16 Sept 2026, 03:17 | 1,981 | -5 |
| 12 Sept 2026, 08:36 | 1,986 | -6 |
| 8 Sept 2026, 03:56 | 1,992 | -9 |
| 2 Sept 2026, 18:24 | 2,001 | -2 |
| 31 Aug 2026, 00:14 | 2,003 | -5 |
| 27 Aug 2026, 15:01 | 2,008 | 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.
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.
@Mahiwno · 19,733
Telegram ranks this channel #32 of 61 here — alongside 60 others — read 4 October 2026
@Navarmaghze · 28,853
Telegram ranks this channel #47 of 64 here — alongside 63 others — read 8 September 2026
@extasymind · 216,316
Telegram ranks this channel #59 of 61 here — alongside 60 others — read 27 August 2026
@abi_magazine · 20,084
Telegram ranks this channel #81 of 82 here — alongside 81 others — read 27 September 2026
This channel appears in 4 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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“CE’” (@waveeeye), 1,905 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/waveeeye.
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.