😀😀😀😀😀 新上押公群 😃😃 常乐集团小额洗资 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+Q6sEiAILvIliNWM1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

Channel
达利担保 公群导航 @dldb
@dlcIb
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
103,293subscribers
+0 since we began measuring on 26 September 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1002219560076 |
|---|---|
| Type | Channel |
| Username | @dlcIb |
| Description | 达利钱包 @DLQB 💎人员配置💎 达利老板: @geju 担保负责人: @jjba 专群负责人: @diao 纠纷负责人: @dava 供需负责人: @mimi 💎官方频道💎 达利供需频道: @lwclb 达利担保公群: @dlcIb 钱包交易群 : @DBDB |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dlcIb |
Topic
Hacking & security — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 09:22 | 103,293 | no change |
| 26 Sept 2026, 08:47 | 103,293 | first reading |
Engagement
121 posts held, back to 25 September 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 7 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.199%
- avg views ÷ 103,293 subscribers
- Avg views / post
- 206
- 121 posts measured
- Reaction rate
- 0.519%
- reactions ÷ views · ER floor
- Posts in window
- 121
- of 121 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 18 of 121 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 September 2026 |
|---|---|
| Posts held | 121 (25 September 2026 – 29 September 2026) |
| Views total | 24,867 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 09:51 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
- Links
- ≈4,430
Lifetime counters from Telegram’s own channel header, read 29 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
18 reactions across 18 posts, in 2 distinct kinds. The most used accounts for 94.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17 | 94.4% | |
| ❤ | 1 | 5.56% |
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 18 of the 121 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 121 most recent posts we hold, published 25 September 2026 to 29 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
😀😀😀😀😀 新上押公群 😃😃😄😃 公群3129 -供押15000U-恒泰支付小额卡码代收做单就送88🧧,代收无风险冻结包赔付 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+m3-DbH0dMm41NGE1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
😀😀😀😀😀 新上押公群 😃😃😃 强盛集团小额洗资 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+GrOIHGFYDlRkYzRl 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
😀😀😀😀😀新上押公群😃😃😃 公群360【盘口直招拍照团队】商场 停车场 街道拍照📸 😄😄😃😄😃 稳定结算❤️轻松日入过万😃😄😄😃😄😃 😃😃:😃😃😃😃😃😃😃 ——————— ⭐️公群通道:https://t.me/+6cEcaywIdLozMzVl 👈点击进入 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
👍1
😀😀😀😀😀 新上押公群 😃😃😃😃 天天集团针孔/摄像头 押金28888u 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+hZdv5uyBGZ82YzU1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
👍1
😀😀😀😀😀 新上押公群 😃😃 众信集团支付宝微信收款码小额代收 50000U 做单就送288🧧,代收无风险冻结包赔付!👍 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+dRzDjmDEnaxhYmM1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
😀😀😀😀😀 新上押公群 😃😄😃😃 鸿兴集团抖音代刷 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+WW0mztNBo8g5ZmI1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
😀😀😀😀😀 新上押公群 😃😃😃 强盛集团小额洗资 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+GrOIHGFYDlRkYzRl 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
😀😀😀😀😀 新上押公群 😃😃😄😃 公群3129 -供押15000U-恒泰支付小额卡码代收做单就送88🧧,代收无风险冻结包赔付 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+m3-DbH0dMm41NGE1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
😀😀😀😀😀新上押公群😃😃😃 公群360【盘口直招拍照团队】商场 停车场 街道拍照📸 😄😄😃😄😃 稳定结算❤️轻松日入过万😃😄😄😃😄😃 😃😃:😃😃😃😃😃😃😃 ——————— ⭐️公群通道:https://t.me/+6cEcaywIdLozMzVl 👈点击进入 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
👍1
😀😀😀😀😀 新上押公群 😃😃😄😃 公群3129 -供押15000U-恒泰支付小额卡码代收做单就送88🧧,代收无风险冻结包赔付 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+m3-DbH0dMm41NGE1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
😀😀😀😀😀 新上押公群 😃😄😃😃 鸿兴集团抖音代刷 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+WW0mztNBo8g5ZmI1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法
Showing the 12 most recent of 121 posts we hold for @dlcIb. 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 2 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“达利担保 公群导航 @dldb” (@dlcIb), 103,293 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/dlcIb.
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.