Channel
@lelezs4
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2,108subscribers
+330 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004372073690 |
|---|---|
| Type | Channel |
| Username | @lelezs4 |
| Created | Between 1 June 2026 and 27 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/lelezs4 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 09:34 | 2,108 | +113 |
| 31 Aug 2026, 08:32 | 1,995 | +188 |
| 28 Aug 2026, 01:13 | 1,807 | +29 |
| 27 Aug 2026, 19:00 | 1,778 | first reading |
9 posts held, back to 27 August 2026 — 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 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.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 9 (27 August 2026 – 27 August 2026) |
| Views total | 1,537 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Aug 2026, 19:00 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.
Measured directly from 3 videos 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.
🎟 抽奖标题: ❤️沪上嫩妹甄选府《浦东 乐乐》【@lele_14z】❤️ 本次活动由【沪上嫩妹甄选府】倾情赞助！ 1️⃣本次活动将开启无限加成模式！叠加次数越多，中奖几率越大 2️⃣请24小时内联系老师兑换，3天内出击完成提交报告因炸号，退群，注销账号等原因，超时未兑换等原因的，不予兑奖！ 3️⃣活动最终解释权归本群管理团队所有。 ⚠️刷屏、灌水、纯表情、复制粘贴、无意义对话、删除消息、撤回内容等，一律视为无效发言，取消中奖资格！请用心交流！ 兑奖请联系：@lele_14z 消耗积分: 50 积分 定时开奖 2026-08-30 18:00:00 参与关键词: 府有佳人三千，独宠乐乐一天 已参与: 9人 🎁 奖品列表： P/PP通用半价优惠券 X 2 「乐透抽奖」 每消耗 50 积分 兑换一张乐透券 🎟 可多次参与抽奖提高中奖率 🎉 参与要求: ➕加入 - 乐乐的频道 ➕加入 - 【上海】沪上嫩妹甄选…
乐乐的频道 pinned a photo
🎰 浦东乐乐半价抽奖活动 📮 抽奖条件: 🎫 加入-乐乐的频道 🎫 加入-工兵团低价区 🎫 加入-工兵团福利频道 🎁 奖品内容: @lele_14z 半价优惠券 × 3 💡 活动说明: 半价优惠券*3 只能用于p 注意事项： 1. 先询问老师位置与自己距离考虑要不要参与抽奖 2.抽中福利时间3天内使用或者老师协商其他时间 3. 需要写报告“聊天群打模版” 4.写完报告记得私信我找我加积分 注：中了未去或者没有写报告者往后参与不了任何抽奖活动 📅 开奖日期:(UTC+8) 2026年08月29日 12时00分00秒
我在上海狼友互动群工兵上榜啦！ https://t.me/SHJVH099
https://t.me/gongbintuandijiaqu/7490
🎰 🔥浦东 乐乐 派送🧧现金红包和🎟通用半价工兵券福利名额抽奖活动🎁 📮 参与条件： 🎫 加入-乐乐的频道 🎫 加入-上海福利频道【美团大队】 🎫 加入-上海修车【美团大队】（广告群） 🎫 加入-上海修车交流群【美团大队】 └ 🎟️ 发言数大于 38 条 🎫 加入-上海出击报告【美团大队】 🎫 加入-上海修车选妃频道【美团大队】 🎁 奖品内容： 💰️ 浦东乐乐🎟通用半价券福利名额 × 2 💰️ 🧧现金红包18.8元 × 1 ⚠️ 抽奖说明： 1、关注活动指定的群组和频道 2、交流群发言达标 38 条(按规发言禁刷屏) 3、本次活动福利为🎟通用半价工兵券(活动价300P/600PP) 4、中奖者要求开奖后 7 天内完成约课和出击（或转让） 5、本次优惠活动为工兵报告券活动，完成出击后24小时内提交出击报告 6、中奖后24小时内联系老师 @lele_14z 中奖截图约课 ———————————— ❗️特别提示❗️ 活…
📊 4条车评，综合评分8.34 好评 100% |人照 7.88 |服务 8.88 中评 0% |颜值 7.88 |态度 8.88 差评 0% |身材 8 |环境 8.5 🚩 编号： TE178261209165 📣 艺名： 乐乐 🌐 区域： #浦东 #三林 💵 价格： 600P 1200PP 🔗 联系： @lele_14z 🔗 双向： @lele_14zbot 🖥 资料： 年龄21 身高160 体重45KG 胸B ✏️ 服务： 陪浴 舌吻 69 无套口 臀推 十指弹琴 漫游 胸推 臀推 足交 制服诱惑 丝袜诱惑 情趣诱惑 按摩 舔奶头 📌 标签： 颜值系 身材好 性价比 📝 评价： https://t.me/shlyddgj_bot?start=commentTeacher-TE178261209165
🌈标题：浦东 乐乐 @lele_14z 限p半价福利抽奖 👑抽奖编号：Z32836179 🎤说明： 中奖有机器人发送中奖信息，没收到信息说明没中奖；中奖联系老师领奖，福利有效期为7天，有特殊情况联系老师同意延期；可免费转赠，禁止买卖，过期作废！中奖者必须写评论，否则取消抽奖资格。 老师号不要抽奖，中奖作废！ 冒领者抽奖机器人永久拉黑。中奖后需出击后提交出击报告，@jizhizuojia_gc_bot 疑问等联系管理机器人 @jizhizuojia_manager_bot 🎁奖品： ➖浦东 乐乐 @lele_14z 限p半价（折后300p） x 2 ➖口令红包18.8 x 1 📌参与条件： ➖需要加入：🎟乐乐的频道 ➖需要加入：🎟魔都极致座驾体验群 ➖需要加入：🎟座驾福利群（老师勿进） ➖需要加入：🎟魔都极致座驾新赛道 ➖需要加入：🎟魔都极致座驾体验课程发布区 💻开奖方式：⏰开奖时间：2026-08-29 20:00:
📊 0条车评，综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 🚩 编号： TE178261209165 📣 艺名： 乐乐 🌐 区域： #浦东 #三林 💵 价格： 600P 1200PP 🔗 联系： @lele_14z 🔗 双向： @lele_14zbot 🖥 资料： 年龄21 身高160 体重45KG 胸B ✏️ 服务： 陪浴 舌吻 69 无套口 臀推 十指弹琴 漫游 胸推 臀推 足交 制服诱惑 丝袜诱惑 情趣诱惑 按摩 舔奶头 📌 标签： 颜值系 身材好 性价比 📝 评价： https://t.me/shlyddgj_bot?start=commentTeacher-TE178261209165
Showing the 9 most recent of 9 posts we hold for @lelezs4. 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.
Named by 10 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“乐乐的频道” (@lelezs4), 2,108 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/lelezs4.
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.