Telegram RegisterThe public register of Telegram
Telegram profile photo for 非越媒体库

Channel

非越媒体库

@lilililililiiillllli

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

12,051subscribers

+1,455 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002161349624
TypeChannel
Username@lilililililiiillllli
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/lilililililiiillllli

Topic

Marketing & affiliate — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 why it has no browse page of its own yet.

Growth

10,59612,05111,323.57 August 2026 — 10,596 subscribers7 August 2026 — 10,596 subscribers8 August 2026 — 10,606 subscribers9 August 2026 — 10,620 subscribers10 August 2026 — 10,616 subscribers11 August 2026 — 10,646 subscribers12 August 2026 — 10,900 subscribers13 August 2026 — 10,938 subscribers15 August 2026 — 10,979 subscribers16 August 2026 — 11,195 subscribers17 August 2026 — 11,215 subscribers18 August 2026 — 11,238 subscribers19 August 2026 — 11,273 subscribers20 August 2026 — 11,295 subscribers22 August 2026 — 11,308 subscribers23 August 2026 — 11,477 subscribers25 August 2026 — 11,507 subscribers26 August 2026 — 11,525 subscribers27 August 2026 — 11,538 subscribers27 August 2026 — 11,571 subscribers28 August 2026 — 11,583 subscribers29 August 2026 — 11,595 subscribers30 August 2026 — 11,619 subscribers31 August 2026 — 11,618 subscribers1 September 2026 — 11,907 subscribers2 September 2026 — 11,927 subscribers3 September 2026 — 11,928 subscribers6 September 2026 — 11,957 subscribers9 September 2026 — 11,979 subscribers12 September 2026 — 11,998 subscribers13 September 2026 — 11,995 subscribers15 September 2026 — 12,010 subscribers17 September 2026 — 12,028 subscribers19 September 2026 — 12,051 subscribers7 August 202619 September 2026
34 measurements spanning 43 days, net +1,455. 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 10,378–12,269 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
19 Sept 2026, 15:0012,051+23
17 Sept 2026, 03:2112,028+18
15 Sept 2026, 07:4112,010+15
13 Sept 2026, 18:3811,995-3
12 Sept 2026, 00:3611,998+19
9 Sept 2026, 13:3611,979+22
6 Sept 2026, 05:2111,957+29
3 Sept 2026, 22:2111,928+1
2 Sept 2026, 16:4711,927+20
1 Sept 2026, 17:3411,907+289
31 Aug 2026, 17:1211,618-1
30 Aug 2026, 19:4711,619+24
29 Aug 2026, 21:2311,595+12
28 Aug 2026, 19:2811,583+12
27 Aug 2026, 22:0711,571+33
27 Aug 2026, 01:2611,538+13
26 Aug 2026, 01:4211,525+18
25 Aug 2026, 02:4811,507+30
23 Aug 2026, 19:3311,477+169
22 Aug 2026, 01:3411,308first reading

Engagement

22 posts held, back to 1 January 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 45 pages 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 22 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 50s
Average length
1m 50s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

174 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 46.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8046.0%
❤6135.1%
🥰2313.2%
😱52.87%
💩42.30%
🤔10.575%

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 18 of the 22 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 174 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 1 January 2025 to 12 August 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

12 Aug 2026, 12:20 UTC≈3,590 viewsread 2 September 2026

GeeTV 目前招收代理(下线),感兴趣有量的联系合作 联系 Bot:@ChenNSBot

27 Jun 2026, 14:39 UTC≈5,210 views6 reactionsread 2 September 2026

注意看一下线路中的推流地址,加入代理列表

👍5❤1

27 Jun 2026, 07:14 UTC≈5,780 views59 reactionsread 2 September 2026
Photo

都放心大胆的蹬,咱公益硬件、带宽资源还是很充足滴🤗

👍50❤6🥰3

25 Jun 2026, 10:50 UTC≈5,280 viewsread 2 September 2026

需要 GeeTV体验的私我 Bot 领取 @ChenNSBot 发卡站 https://siepro.me

20 Jun 2026, 09:48 UTC≈5,330 views3 reactionsread 2 September 2026

只禁infuse媒体库模式、emby官方客户端(所有)、浏览器、禁止日本ip。同时一个播放,其他没有限制

❤3

16 Jun 2026, 13:40 UTC≈6,490 views2 reactionsread 2 September 2026

🔧 Emby 登录问题自助指南 检测到你遇到了连接问题,请根据错误现象自查: 📱 客户端错误(4xx) 400 请求格式错误 → 检查URL参数或重启客户端 401 登录失败 → 重新输入账号密码,Token可能过期 403 无权限 → 联系服主确认账号状态或IP封禁 404 地址错误 → 检查服务器地址拼写 405 请求方式不对 → 客户端或代理配置问题 🔧 服务器错误(5xx) 500 Emby内部错误 → 等会儿再试或联系服主 502/503/504 网关问题 → 服务器重启中,等2-3分钟 ☁️ Cloudflare 错误(套了CF) 520 服务器抽风 → 刷新或等30秒 521 服务器挂了 → 联系服主 522/524 连接/响应超时 → 检查网络或服务器负载过高 523 DNS解析失败 → 检查域名是否正确 525/526 证书错误 → 检查HTTPS配置,或暂用HTTP测试 530 DNS错误 → 域名解析配…

❤2

7 Nov 2025, 14:56 UTC≈11,500 views20 reactionsread 2 September 2026

鉴于这段时间公益服稳定性较差,暂停维护 24 小时

❤15😱5

30 Oct 2025, 08:38 UTC≈13,200 views1 reactionsread 2 September 2026

由于之前的账号炸了,现启用新账号管理Bot:@fyemby_bot emby账号等不受影响,关注使用新Bot即可

❤1

17 Aug 2025, 22:45 UTC≈13,700 views24 reactionsread 2 September 2026

线路有升级和更改,各位注意及时变更

❤20👍4

Showing the 12 most recent of 22 posts we hold for @lilililililiiillllli. 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.

Posts edited after publishing

@lilililililiiillllli edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
15 August 2026
Most recent edit
15 August 2026

Forward network

Republished by

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“非越媒体库” (@lilililililiiillllli), 12,051 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/lilililililiiillllli.

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.