Telegram RegisterThe public register of Telegram
Telegram profile photo for i.nily

Channel

i.nily

@i0nily

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

66,286subscribers

+11,855 since we began measuring on 9 September 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003551342750
TypeChannel
Username@i0nily
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live5 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/i0nily

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 28 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

54,43167,06060,745.59 September 2026 — 54,431 subscribers9 September 2026 — 54,431 subscribers11 September 2026 — 56,266 subscribers13 September 2026 — 57,088 subscribers15 September 2026 — 58,014 subscribers17 September 2026 — 59,089 subscribers28 September 2026 — 64,718 subscribers5 October 2026 — 65,907 subscribers9 October 2026 — 66,387 subscribers13 October 2026 — 66,678 subscribers14 October 2026 — 66,843 subscribers15 October 2026 — 66,904 subscribers16 October 2026 — 66,980 subscribers17 October 2026 — 67,014 subscribers18 October 2026 — 67,038 subscribers19 October 2026 — 67,003 subscribers20 October 2026 — 66,961 subscribers21 October 2026 — 67,060 subscribers22 October 2026 — 66,968 subscribers23 October 2026 — 66,789 subscribers24 October 2026 — 66,791 subscribers25 October 2026 — 66,805 subscribers26 October 2026 — 66,795 subscribers27 October 2026 — 66,793 subscribers28 October 2026 — 66,698 subscribers29 October 2026 — 66,667 subscribers30 October 2026 — 66,684 subscribers31 October 2026 — 66,644 subscribers1 November 2026 — 66,553 subscribers2 November 2026 — 66,430 subscribers3 November 2026 — 66,389 subscribers4 November 2026 — 66,374 subscribers5 November 2026 — 66,286 subscribers66,2869 September 20265 November 2026
33 measurements spanning 57 days, net +11,855. 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 52,537–68,954 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
5 Nov 2026, 21:1166,286-88
4 Nov 2026, 21:5666,374-15
3 Nov 2026, 22:0666,389-41
2 Nov 2026, 18:5666,430-123
1 Nov 2026, 17:3066,553-91
31 Oct 2026, 16:4666,644-40
30 Oct 2026, 16:1766,684+17
29 Oct 2026, 13:5666,667-31
28 Oct 2026, 16:0866,698-95
27 Oct 2026, 18:0066,793-2
26 Oct 2026, 20:5966,795-10
25 Oct 2026, 22:0566,805+14
24 Oct 2026, 21:4166,791+2
23 Oct 2026, 23:1666,789-179
22 Oct 2026, 20:0066,968-92
21 Oct 2026, 15:0867,060+99
20 Oct 2026, 09:3766,961-42
19 Oct 2026, 12:5567,003-35
18 Oct 2026, 14:2867,038+24
17 Oct 2026, 13:4567,014first reading

Engagement

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

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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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.

“i.nily” (@i0nily), 66,286 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/i0nily.

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.