Telegram RegisterThe public register of Telegram

Channel

野良

@Yeliangk

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

5subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1004310047628
TypeChannel
Username@Yeliangk
Created25 July 2026measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Yeliangk

Growth

514 Aug 2026, 03:31 — 5 subscribers14 Aug 2026, 13:46 — 5 subscribers14 Aug 2026, 03:3114 Aug 2026, 13:46
2 measurements taken within a single day. 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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:465no change
14 Aug 2026, 03:315first reading

Engagement

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

ERR · 30 days
726.7%
avg views ÷ 5 subscribers
Avg views / post
36.3
6 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 7 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held7 (25 July 20269 August 2026)
Views total218
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 03:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

25 Jul 2026, 12:12 UTC62 viewsread 14 August 2026

费了一番功夫修了深色类微信主题。 彻底重构了原 CSS,解决了很多问题,极大改善了低灰阶的可读性。在一些细节的强调色上与微信更像了。 该主题主要在 tdesktop 上测试,移动端优先级不高(才不是懒得测呢) https://t.me/addtheme/NahidaModern 因为是绿色所以还用 Nahida🍃了 亮色版本请直接使用: http://t.me/addtheme/WeChat_v81, source 由于不存在灰阶损失,各方面都还不错 To Devs: 使用 Codex 重构了很多色值引用,现在灰度背景色、前景色、绿色强调色的变量更集中了,可以简单改几处就换掉几乎所有地方的强调色。如果有谁想改自己的主题,欢迎在本主题基础上更改,比官方的好很多。

25 Jul 2026, 12:12 UTC49 viewsread 14 August 2026
Photo

▎WaifuX 作为Mac用户,终于不用再对着Windows的Wallpaper Engine流口水了!开源神器WaifuX横空出世,让你的桌面彻底“活”起来。 由开发者jipika打造的免费工具,不仅聚合了Wallhaven和4K Wall的海量高清图库,更祭出了“杀手锏”:实验性兼容Wallpaper Engine创意工坊!那些烧显卡的场景壁纸现在也能在Mac(仅限Apple芯片)上优雅运行。 此外更离谱的是,WaifuX居然还内置了多源解析引擎,如bangumi及其他几个类似的解析源。 你的壁纸何必只是壁纸? https://github.com/jipika/WaifuX 🗒 标签: #Mac #开源软件 📢 频道: @me888888888888 🎈 群组: @imbbbbbbbbbbb 🪬 合作&推广:@imbbbbb_bot @imbbbbbbbb ☝️消息怕错过?请收藏频道并开启推送!☝️

25 Jul 2026, 12:12 UTC33 viewsread 14 August 2026
Photo

😀 Pastel 一款 IPA 下载工具 一款用于安装 IPA 历史版本的工具,适用于获取旧版应用并自动捕获数据包。下载后,可直接通过 AirDrop 传输至 iPhone、iPad 上并安装并使用。 目前只支持 macOS 26+ 且配备 Apple 芯片的 Mac。Windows 版本也即将发布。 地址:https://github.com/EEliberto/IPA-Download #资源 #IPA 发布频道:https://t.me/inaisi

25 Jul 2026, 12:11 UTC29 viewsread 14 August 2026

Telegram 转圈问题总结 1. 针对转圈打不开 🆕 Surge 使用 MTProto 很快很爽 ✅ 将 tg 的垃圾 IP 转移到好的 IP 上, 来源 更新: 转移到 147 和 201 版 可能 IP 又不好了 需要自己换 ✅ 95.161.76.100/31 reject ✅ 打断连接 ❓使用 SOCKS5 代理 ❓(刘老师说有效) 使用独立的出口 IP 来源 1 和 来源 2 ❓Snell v4 的优化,有望解决 Telegram 偶尔出现卡顿的问题,待观察是否确实有效 来源 2. 针对加载速度 ✅ 开会员 @PremiumBot ✅ 按 DC 分流 ❓使用魔改客户端 不确定有没有被和谐 🤭 模块脚本合集 🧐 频道资源合集 😄 恰饭推荐 💬 群组 🥰 #Telegram #转圈

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

Citation-graph rank

Citation-graph rank — 1,115,052 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“野良” (@Yeliangk), 5 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Yeliangk.

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.