✅永乐担保招拉手 0.7U/5R 💰新频道人少,特别好推,日入五百+不是问题 🎉机器人里面有指定文案去推广。 👉永乐担保计划拿一万U 用来拉人头,请各位拉手转告朋友。 https://t.me/+IOyF1xxfChs0MWFh
👍1

Channel
@yldb000
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
49subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001182414590 |
|---|---|
| Type | Channel |
| Username | @yldb000 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/yldb000 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 20:53 | 49 | -1 |
| 10 Aug 2026, 11:30 | 50 | no change |
| 7 Aug 2026, 06:28 | 50 | first reading |
20 posts held, back to 8 May 2022 — 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 pageof 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 20 posts for this entry, the most recent from 11 March 2023. An engagement rate over an empty window would be a number about nothing.
28 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 53.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 15 | 53.6% | |
| 💯 | 4 | 14.3% | |
| 😁 | 3 | 10.7% | |
| ❤ | 2 | 7.14% | |
| 👌 | 1 | 3.57% | |
| 😍 | 1 | 3.57% | |
| 😱 | 1 | 3.57% | |
| 😴 | 1 | 3.57% |
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 20 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 28reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 May 2022 to 11 March 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
✅永乐担保招拉手 0.7U/5R 💰新频道人少,特别好推,日入五百+不是问题 🎉机器人里面有指定文案去推广。 👉永乐担保计划拿一万U 用来拉人头,请各位拉手转告朋友。 https://t.me/+IOyF1xxfChs0MWFh
👍1
👏永乐担保担保公群 永乐官方大群 @yldb999 永乐供需频道 @yldb888 永乐公群频道 @yldb000 永乐供需限时活动中,原50U频道现在2折,10U,同步推送核心大群 上押公群免手续费,上下都无,截至0405 唯一管理员 @yldb7 @yldb8
💯4😁3👍2❤1😍1😱1😴1
✅如果在押公群没有合适的项目或者价格 请转移到付费广告💰 @yldb888 做项目尽量找在押商家,以免产生不必要的损失 ⚠️任何公群都有负责人 @yldb7 在 🆘如果不在都是骗子,模仿者! 📣开押金担保公群联系永乐负责人 @yldb8
免费机器人由永乐担保提供 @yldb6_bot 1.支持自定义按钮 2.支持超级链接 3.进群欢迎语 4.进群禁言时间 5.进群验证必须关注频道 6.关键词回复信息 7.关键词拦截删除 8.删除进/退群消息 9.设置定时广告 不懂的可以咨询 : @yldb8
👌1
备用帖
👍2
备用帖
备用帖
备用帖
🚸TG永乐担保🟡公群导航 pinned «—⚒永乐担保自助服务中心⚙️— 👨✈️永乐担保唯一负责人 @yldb8 ✅付费广告 交流专群✅ 🔍担保公群 发布广告🥇 👨🏻💻正版飞机 欧易下载 💰 📖 担保规则 海外苹果🆔 🔍VPN下载 …»
备用帖
👍1
备用帖
备用帖
Showing the 12 most recent of 20 posts we hold for @yldb000. 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.
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.
@yldb000 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“🚸TG永乐担保🟡公群导航” (@yldb000), 49 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/yldb000.
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.