Telegram RegisterThe public register of Telegram
Telegram profile photo for 达利担保 公群导航 @dldb

Channel

达利担保 公群导航 @dldb

@dlcIb

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

123,267subscribers

+19,974 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
TypeChannel
Username@dlcIb
Description达利钱包 @DLQB 💎人员配置💎 达利老板: @geju 担保负责人: @jjba 专群负责人: @cpdb 纠纷负责人: @dava 供需负责人: @mimi 💎官方频道💎 达利供需频道: @lwclb 达利担保公群: @dlcIb 钱包交易群 : @DBDB
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 September 2026
Last confirmed live18 November 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.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 the other topics.

Growth

76,782129,315103,048.526 September 2026 — 103,293 subscribers26 September 2026 — 103,293 subscribers4 October 2026 — 102,463 subscribers8 October 2026 — 101,513 subscribers13 October 2026 — 101,888 subscribers14 October 2026 — 99,855 subscribers15 October 2026 — 98,524 subscribers16 October 2026 — 102,774 subscribers17 October 2026 — 99,869 subscribers18 October 2026 — 99,015 subscribers19 October 2026 — 90,620 subscribers20 October 2026 — 88,539 subscribers21 October 2026 — 87,066 subscribers22 October 2026 — 84,172 subscribers24 October 2026 — 90,805 subscribers25 October 2026 — 107,618 subscribers26 October 2026 — 106,646 subscribers27 October 2026 — 105,314 subscribers28 October 2026 — 104,234 subscribers29 October 2026 — 95,551 subscribers30 October 2026 — 76,782 subscribers31 October 2026 — 80,946 subscribers1 November 2026 — 92,274 subscribers2 November 2026 — 102,432 subscribers3 November 2026 — 102,430 subscribers4 November 2026 — 102,142 subscribers5 November 2026 — 101,978 subscribers6 November 2026 — 101,618 subscribers7 November 2026 — 100,610 subscribers8 November 2026 — 125,359 subscribers10 November 2026 — 129,315 subscribers12 November 2026 — 127,949 subscribers15 November 2026 — 125,936 subscribers18 November 2026 — 123,267 subscribers123,26726 September 202618 November 2026
34 measurements spanning 53 days, net +19,974. 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 68,902–137,195 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Nov 2026, 16:10123,267-2,669
15 Nov 2026, 13:50125,936-2,013
12 Nov 2026, 07:14127,949-1,366
10 Nov 2026, 03:46129,315+3,956
8 Nov 2026, 20:56125,359+24,749
7 Nov 2026, 15:19100,610-1,008
6 Nov 2026, 12:10101,618-360
5 Nov 2026, 11:01101,978-164
4 Nov 2026, 14:01102,142-288
3 Nov 2026, 14:35102,430-2
2 Nov 2026, 16:36102,432+10,158
1 Nov 2026, 17:0592,274+11,328
31 Oct 2026, 16:3680,946+4,164
30 Oct 2026, 13:3876,782-18,769
29 Oct 2026, 10:0995,551-8,683
28 Oct 2026, 07:21104,234-1,080
27 Oct 2026, 04:07105,314-1,332
26 Oct 2026, 01:19106,646-972
25 Oct 2026, 02:01107,618+16,813
24 Oct 2026, 00:3090,805first reading

Engagement

2,028 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 108 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.031%
avg views ÷ 123,267 subscribers
Avg views / post
38.8
1,123 posts measured
Reaction rate
2.81%
reactions ÷ views · ER floor
Posts in window
1,123
of 2,028 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 408 of 1,123 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 19 November 2026
Posts held2,028 (25 September 2026 – 19 November 2026)
Views total43,599
Reactions total519
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Nov 2026, 04:36 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
≈6,570

Lifetime counters from Telegram’s own channel header, read 19 November 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

477 reactions across 367 posts, in 4 distinct kinds. The most used accounts for 96.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍45996.2%
❤163.35%
👏10.21%
😁10.21%

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 370 of the 1,000 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 477 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 24 October 2026 to 19 November 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

Telegram’s own ‘edited’ marker: 2 of 1,123 posts held from the last 30 days (0.178%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

19 Nov 2026, 04:02 UTC4 viewsread 19 November 2026

😀😀😀😀😀新上押公群😃😃😃 公群360【盘口直招拍照团队】商场 停车场 街道拍照📸 😄😄😃😄😃 稳定结算❤️轻松日入过万😃😄😄😃😄😃 😃😃:😃😃😃😃😃😃😃 ——————— ⭐️公群通道:https://t.me/+6cEcaywIdLozMzVl 👈点击进入 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

19 Nov 2026, 03:25 UTC9 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😃😃 公群44-供押20888U-恒泰支付小额卡码代收(24小时在线营业)做单就送88🧧,代收无风险冻结包赔付👍 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+m3-DbH0dMm41NGE1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

19 Nov 2026, 03:03 UTC9 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😃😄😃😃 鸿兴集团抖音代刷 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+WW0mztNBo8g5ZmI1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

19 Nov 2026, 02:10 UTC13 viewsread 19 November 2026

😀😀😀😀😀新上押公群😃😃😃 公群816 【红星集团·礼物代刷新项目】有❤ ❤就可以刷单 ⚡五分钟一单 每单利润💍🥽🥽➕⚡⚡⚡⚡⚡⚡ 😃😃:😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+8SY0FwIVm3MzYzdk 😃点击进入 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

19 Nov 2026, 02:04 UTC10 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😃😃😃 鼎盛集团假钞精仿1:1 押金28888u 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+TxHWlRG8IuUxODY9 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

19 Nov 2026, 01:31 UTC12 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😃😃 众信集团支付宝微信收款码小额代收 50000U 做单就送288🧧,代收无风险冻结包赔付!👍 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+dRzDjmDEnaxhYmM1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

19 Nov 2026, 00:25 UTC13 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😃😃 公群44-供押20888U-恒泰支付小额卡码代收(24小时在线营业)做单就送88🧧,代收无风险冻结包赔付👍 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+m3-DbH0dMm41NGE1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

19 Nov 2026, 00:01 UTC12 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😃😃😃 鼎盛集团淘宝/京东刷单 押金88888u 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+req2EnwRvZpkZjZl 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

18 Nov 2026, 23:03 UTC10 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😄😃😄 U享社·搬砖USDT赚钱 押金50000u 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+7GptPoZaonhkMWI8 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

18 Nov 2026, 22:00 UTC13 viewsread 19 November 2026

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

18 Nov 2026, 20:45 UTC15 viewsread 19 November 2026

😀😀😀😀😀 新上押公群 😃😃 公群44-供押20888U-恒泰支付小额卡码代收(24小时在线营业)做单就送88🧧,代收无风险冻结包赔付👍 😃😃 :😃😃😃😃😃😃😃 ——————— 公群通道:https://t.me/+m3-DbH0dMm41NGE1 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

18 Nov 2026, 20:10 UTC13 viewsread 19 November 2026

😀😀😀😀😀新上押公群😃😃😃 公群360【盘口直招拍照团队】商场 停车场 街道拍照📸 😄😄😃😄😃 稳定结算❤️轻松日入过万😃😄😄😃😄😃 😃😃:😃😃😃😃😃😃😃 ——————— ⭐️公群通道:https://t.me/+6cEcaywIdLozMzVl 👈点击进入 验群通道: @DLDB 😃公群大群 各类业务 公群报备流程 公群验群方法

Showing the 12 most recent of 2,028 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 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.

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

“达利担保 公群导航 @dldb” (@dlcIb), 123,267 subscribers as measured 18 November 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.