![Telegram profile photo for nkeeei everyday [2021-2026]](https://cdn.tgregister.com/av/ff/ff94891bb56e424f99d81c3e0105f763bdad437696387150a3f0349337fbeedb.jpg)
Channel
nkeeei everyday [2021-2026]
@nkeeeieveryday
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,095subscribers
-66 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001588583954 |
|---|---|
| Type | Channel |
| Username | @nkeeeieveryday |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/nkeeeieveryday |
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 6 October 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 21:09 | 1,095 | -3 |
| 5 Nov 2026, 03:20 | 1,098 | -3 |
| 1 Nov 2026, 19:38 | 1,101 | +1 |
| 29 Oct 2026, 12:38 | 1,100 | -1 |
| 26 Oct 2026, 20:51 | 1,101 | -4 |
| 23 Oct 2026, 23:48 | 1,105 | -1 |
| 20 Oct 2026, 23:49 | 1,106 | +2 |
| 18 Oct 2026, 06:39 | 1,104 | -4 |
| 14 Oct 2026, 21:29 | 1,108 | -5 |
| 11 Oct 2026, 22:14 | 1,113 | -1 |
| 6 Oct 2026, 05:23 | 1,114 | no change |
| 5 Oct 2026, 09:40 | 1,114 | -5 |
| 27 Sept 2026, 06:00 | 1,119 | -4 |
| 18 Sept 2026, 00:57 | 1,123 | -7 |
| 14 Sept 2026, 04:36 | 1,130 | -8 |
| 10 Sept 2026, 15:00 | 1,138 | -6 |
| 5 Sept 2026, 11:38 | 1,144 | -6 |
| 1 Sept 2026, 07:06 | 1,150 | -1 |
| 29 Aug 2026, 16:14 | 1,151 | -2 |
| 26 Aug 2026, 14:24 | 1,153 | 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.
@artemshilovets · 27,927
Telegram ranks this channel #2 of 54 here — alongside 53 others — read 3 September 2026
@uniqe_ya · 26,052
Telegram ranks this channel #7 of 50 here — alongside 49 others — read 10 September 2026
This channel appears in 2 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“nkeeei everyday [2021-2026]” (@nkeeeieveryday), 1,095 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/nkeeeieveryday.
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.