Telegram RegisterThe public register of Telegram

Channel

Lemby_Channel

@Lemby_Channel

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

1,326subscribers

+7 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002450356844
TypeChannel
Username@Lemby_Channel
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/Lemby_Channel

Growth

1,3191,3261,322.510 August 2026 — 1,319 subscribers10 August 2026 — 1,319 subscribers13 August 2026 — 1,326 subscribers10 August 202613 August 2026
3 measurements spanning 3 days, net +7. 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 1,318–1,327 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 08:051,326+7
10 Aug 2026, 05:501,319no change
10 Aug 2026, 00:471,319first reading

Engagement

19 posts held, back to 25 June 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
27.1%
avg views ÷ 1,326 subscribers
Avg views / post
359
10 posts measured
Reaction rate
1.72%
reactions ÷ views · ER floor
Posts in window
10
of 19 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. It is computed over the 6 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held19 (25 June 20267 August 2026)
Views total3,593
Reactions total34
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 00:47 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.

Reaction mix

48 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 54.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2654.2%
🤯612.5%
🍾510.4%
👍510.4%
😁36.25%
🤩24.17%
👀12.08%

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

Measured over the 19 most recent posts we hold, published 25 June 2026 to 7 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

7 Aug 2026, 06:59 UTC236 views12 reactionsread 10 August 2026

目前emby库大概有105W,有在用的用户应该都发觉稳定性和流畅度都远不如以前了,问题很早就排查出了,是独服的硬盘性能达到了瓶颈了,在面对100w级别的资源,i/o达到瓶颈了,前几天上了几台前端分摊了部分压力。经过这几天观察,确实能轻微缓解压力,但本质问题无法解决,还是emby服务端的压力过多,起搏速度慢,资源入库多的时候容易卡死,只能通过升级服务端来解决,这个回到一个重要的问题,我没钱,每个月的发电收入也平摊不了现在的成本,所以就是没得解决。就这样了,不好不坏地运行下去。

8👍2🤩2

30 Jul 2026, 11:48 UTC413 views6 reactionsread 10 August 2026

入库的资源太多了,服务器有点顶不住了

🤯6

27 Jul 2026, 17:12 UTC365 views4 reactionsread 10 August 2026

emby圈子这么奇葩的嘛,吵架先扣帽子,按个身份再打靶,一点道理都不讲,有点意思啊

😁3👀1

12 Jul 2026, 07:48 UTC484 views1 reactionsread 10 August 2026
Forwarded from @boomtechreviewsPhoto

Richard余 , 英文全名 Richard Billy . 作为李平先生的老乡 , 深知操B才是第一生产力 . 华为造的车叫什么 ? — AITO(爱透), 意义非常明确 . 曾经有苹果的员工形容即将卸任的苹果CEO Tim Cook的情绪波动幅度大概就是 : 100分里面只会有33到35的变化 . 按照这个标准 , 余承东从10:39:15开始能算50 , 到了11:01:10的时候已经达到90了 , 11:01:39直接飙到 100了 . 这几个员工被开除真的是一点都不值得同情 . 以后找新工作入职的时候先了解一下公司产品的定位 , 以及公司的老板和CEO都是哪里人 , Telegram那么多免费BOT先帮他们全家出道一下 ...

1

Showing the 12 most recent of 19 posts we hold for @Lemby_Channel. 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,030,721 of 1,169,250entries 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.

Forward network

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

“Lemby_Channel” (@Lemby_Channel), 1,326 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Lemby_Channel.

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.