Telegram RegisterThe public register of Telegram
Telegram profile photo for 极雾—效率自发仓

Channel

极雾—效率自发仓

@lelelelelelelelelelelpyq

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

1,312subscribers

+1,283 since we began measuring on 15 September 2026

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

Register entry

Telegram ID-1002017554605
TypeChannel
Username@lelelelelelelelelelelpyq
Created22 October 2023 — measured — dated from the channel’s first post
First recorded15 September 2026
Last confirmed live30 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 30 September 2026
On Telegramt.me/lelelelelelelelelelelpyq

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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

291,312670.515 September 2026 — 29 subscribers17 September 2026 — 122 subscribers30 September 2026 — 1,312 subscribers15 September 202630 September 2026
3 measurements spanning 15 days, net +1,283. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 21:551,312+1,190
17 Sept 2026, 10:41122+93
15 Sept 2026, 19:2229first reading

Engagement

11 posts held, back to 22 October 2023 — 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.

ERR · 30 days
2.70%
avg views ÷ 1,312 subscribers
Avg views / post
35.4
5 posts measured
Reaction rate
12.4%
reactions ÷ views · ER floor
Posts in window
6
of 11 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 15 September 2026
Posts held11 (22 October 2023 – 15 September 2026)
Views total177
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Sept 2026, 19:22 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.

What this channel posts

Video runtime
6s
Average length
6s

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

33 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2163.6%
👍927.3%
💩39.09%

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

Measured over the 11 most recent posts we hold, published 22 October 2023 to 15 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

15 Sept 2026, 17:34 UTCviews —

极雾—效率自发仓 pinned «明天出物流后不结账拖拖拉拉的我一定拦截你,我不跑你绝对也不能给任何人机会跑我,拦截后取消拦截必须付拦截费别跟我废话»

15 Sept 2026, 17:33 UTC23 views5 reactionsread 15 September 2026

明天出物流后不结账拖拖拉拉的我一定拦截你,我不跑你绝对也不能给任何人机会跑我,拦截后取消拦截必须付拦截费别跟我废话

💩3❤2

15 Sept 2026, 16:37 UTC36 views4 reactionsread 15 September 2026
Photo

全网招代理 @jiwu88 扣我拿代理价😢全网最低价

👍4

15 Sept 2026, 15:24 UTC39 views4 reactionsread 15 September 2026

禁区 新疆、西藏、内蒙古、北京、海南五地⻓期禁 禁区添加深圳 上海

❤4

15 Sept 2026, 15:23 UTC39 views5 reactionsread 15 September 2026

16 号 鸭嘴没货不要下,16号再下鸭嘴全部发扑克松,不退不换

❤5

15 Sept 2026, 05:34 UTC40 views4 reactionsread 15 September 2026

🥰各代理请注意⚠️为了能更精准·高效的为大家服务, 扫码下单之后请按照以下标准模版进行留言⬇️⬇️⬇️ 【品名/总数量/口味/备选不要带数量】 品名:黑条/鸭嘴兽/冰爆/UB蛋/五代杆子/六代杆子/巴博/阿尔法/外贸三颗/艺术家杆 格式一(有空格的) 黑条*3 西瓜1 苹果1 可乐 鸭嘴*2 西瓜1 苹果1 格式二(有空格的) 黑条*3 西瓜 苹果 可乐 鸭嘴*2 西瓜 苹果 格式三(有空格的) 黑条 西瓜1 苹果1 可乐1 鸭嘴 西瓜1 苹果1 格式四(没空格的) 黑条*3西瓜苹果可乐 鸭嘴*2西瓜苹果 🥰🥰🥰如果是因为代理自身下单备注不清,导致发错货和数量,售后一律自付邮费补发!!

❤4

8 Feb 2024, 16:08 UTC331 views3 reactionsread 15 September 2026

在这里祝愿大家在新的一年里踏入🐲龙年的龙门,迎来好运,事业腾飞,事事顺心财源滚滚。

❤3

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

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

“极雾—效率自发仓” (@lelelelelelelelelelelpyq), 1,312 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/lelelelelelelelelelelpyq.

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.