Telegram RegisterThe public register of Telegram
Telegram profile photo for knoxider.lua

Channel

knoxider.lua

@knox1d3r

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

87subscribers

-4 since we began measuring on 26 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004304024542
TypeChannel
Username@knox1d3r
CreatedBetween 1 June 2026 and 22 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 September 2026
Last confirmed live9 November 2026
Measurements held7
Confirmed unchanged2 times, most recently 9 November 2026
On Telegramt.me/knox1d3r

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 92% 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

869188.526 September 2026 — 91 subscribers26 September 2026 — 91 subscribers4 October 2026 — 88 subscribers13 October 2026 — 87 subscribers20 October 2026 — 88 subscribers27 October 2026 — 86 subscribers2 November 2026 — 87 subscribers8726 September 20262 November 2026
7 measurements spanning 38 days, net -4. 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 85–92 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 19:1687+1
27 Oct 2026, 04:5786-2
20 Oct 2026, 11:3588+1
13 Oct 2026, 23:2987-1
4 Oct 2026, 10:5588-3
26 Sept 2026, 04:2291no change
26 Sept 2026, 03:4791first reading

Engagement

17 posts held, back to 22 September 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 25 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

14 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤857.1%
😁428.6%
🤬214.3%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 22 September 2026 to 25 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

25 Sept 2026, 20:35 UTC32 viewsread 26 September 2026

Проще говоря, я в тотально в ахуе с тем, что человек который буквально живёт ликвипедией, делает такой пиздец и ладно он сделал ошибку, я за это его не осуждаю, мне похуй на это, мне не похуй на то, как он не хочет признавать это и пытается выставить так, какой я хуёвый, вина тоже есть на мне, что поторопился, но я просил его 2 раза, 2 БЛЯТЬ РАЗА просто удалить изображение, вместо этого он решил читать лекции о том, …

25 Sept 2026, 20:31 UTC32 viewsread 26 September 2026
Photo

Вот ответ адекватного человека

25 Sept 2026, 20:27 UTC37 viewsread 26 September 2026
Photo

Дорогие друзья, я бы хотел вопросик такой маленький узнать, вы видите что это ИИ ??? Чисто узнать хочу у всех, просьба прежде чем оставить коммент, просто присмотреться и узнать

25 Sept 2026, 20:04 UTC41 viewsread 26 September 2026

Я не буду говорить с кем именно я посрался, но меня кинули в чс буквально за то, что он сам сделал ошибку тогда, когда я с просил чела просто удалить я хз в чём проблема просто удалить что бы убрать баг но нет, надо сделать меня виноватым

25 Sept 2026, 20:03 UTC41 viewsread 26 September 2026

У меня слов нет с типов с ликвипедии, у них кто угодно виноват но только не они

25 Sept 2026, 05:53 UTC71 views7 reactionsread 26 September 2026

Завтра журо покажет как надо трахать

😁4🤬2❤1

24 Sept 2026, 18:44 UTC72 viewsread 26 September 2026

К слову ни один из них в этом списке не причём от слова совсем, он просто нашёл рандомный момент где им просто щедрый донатер донит большую сумму и всё он брал и перед фулл чатом их подъёбывал, очень мерзкий поступок и я не собираюсь молчать об этом

24 Sept 2026, 18:42 UTC74 views2 reactionsread 26 September 2026

Что-бы вы понимали, за что я его засираю не из-за донатов которые он делает и "скрывает" на свой турнир через продавцов (Это уже фулл коммьюнити знает) так ещё и на других нормальных типов берёт и гонит, у меня есть все пруфы о том, что он делал, честно мне похуй забанят или нет, серьёзно тип хоть и делает хуйню но не стоит закрывать глаза на то, что он принёс большой вклад в APAC Коммьюнити и за это его банить глупо…

❤2

24 Sept 2026, 18:34 UTC73 viewsread 26 September 2026
Photo

Ща лакшай доебётся до чела, смешно будет очень

Showing the 12 most recent of 17 posts we hold for @knox1d3r. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“knoxider.lua” (@knox1d3r), 87 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/knox1d3r.

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.