Channel
Nk byadwal
@nkby1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,249subscribers
-26 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001448225334 |
|---|---|
| Type | Channel |
| Username | @nkby1 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/nkby1 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 5 Nov 2026, 12:19 | 2,249 | +1 |
| 2 Nov 2026, 08:36 | 2,248 | -3 |
| 30 Oct 2026, 00:51 | 2,251 | -2 |
| 26 Oct 2026, 23:38 | 2,253 | +1 |
| 24 Oct 2026, 10:19 | 2,252 | +1 |
| 21 Oct 2026, 06:47 | 2,251 | -3 |
| 14 Oct 2026, 21:16 | 2,254 | +1 |
| 11 Oct 2026, 15:20 | 2,253 | -1 |
| 5 Oct 2026, 11:00 | 2,254 | +4 |
| 27 Sept 2026, 18:39 | 2,250 | -1 |
| 18 Sept 2026, 05:39 | 2,251 | -1 |
| 18 Sept 2026, 01:24 | 2,252 | no change |
| 14 Sept 2026, 01:22 | 2,252 | +1 |
| 4 Sept 2026, 11:18 | 2,251 | -1 |
| 31 Aug 2026, 21:23 | 2,252 | -3 |
| 28 Aug 2026, 16:34 | 2,255 | -4 |
| 25 Aug 2026, 05:47 | 2,259 | -6 |
| 22 Aug 2026, 15:42 | 2,265 | -2 |
| 19 Aug 2026, 13:13 | 2,267 | -3 |
| 16 Aug 2026, 06:28 | 2,270 | 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.
@pharmacy_job_vacancy · 26,198
Telegram ranks this channel #8 of 66 here — alongside 65 others — read 12 September 2026
@Maaneduofficial · 43,334
Telegram ranks this channel #32 of 74 here — alongside 73 others — read 29 August 2026
@neetu_singh_spoken_english · 214,479
Telegram ranks this channel #54 of 88 here — alongside 87 others — read 11 August 2026
@cceguru · 151,518
Telegram ranks this channel #92 of 92 here — alongside 91 others — read 12 August 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Nk byadwal” (@nkby1), 2,249 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/nkby1.
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.