Telegram RegisterThe public register of Telegram

Channel

土豆公群做业务注意事项

@tdgql668

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

297subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002497852279
TypeChannel
Username@tdgql668
Created12 January 2025measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/tdgql668

Growth

2977 Aug 2026, 10:31 — 297 subscribers8 Aug 2026, 08:04 — 297 subscribers7 Aug 2026, 10:318 Aug 2026, 08:04
2 measurements taken within a single day. 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 296–298 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 08:04297no change
7 Aug 2026, 10:31297first reading

Engagement

13 posts held, back to 12 January 2025the 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 13 posts for this entry, the most recent from 12 January 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
8

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

12 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1083.3%
👍216.7%

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

Measured over the 13 most recent posts we hold, published 12 January 2025 to 12 January 2025, 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

12 Jan 2025, 06:05 UTC≈1,370 views3 reactionsread 8 August 2026

快速导航 土豆担保 - 人员名单 土豆担保 - 公群对接业务注意事项 土豆担保 - 交易说明 土豆担保 - 公群交易流程 土豆担保 - 公群收费标准 土豆担保 - 公群注意事项 土豆担保 - 公群日常管理注意事项 土豆担保 - 群老板和业务员账号安全注意事项 土豆担保 - 骗子常用手法介绍 土豆担保 - 关于密保和原地址 土豆担保 - 关于公群商户正常运营

3

12 Jan 2025, 06:04 UTC≈1,200 views2 reactionsread 8 August 2026

土豆担保 - 关于公群商户正常运营 为了确保公群的正常运营,我们在此公告如下: 1. 特殊情况营业规定: 商户可授权特殊情况群老板失联业务员可正常营业(如需授权可随时联系工作人员),在群老板失联期间由业务员代营业确保公群业务,授权营业风险需商户自行把控,如出现业务员套取押金等行为和土豆担保无关 2.特殊情况非原地址退押规定: 土豆担保默认退押地址为上押原地址,如商户因特殊情况需非原地址退押,需联系工作人员核实密保或原地址加押核实身份,核实密保/原地址加押无误后可按正常流程办理退押;如无法提供密保或无法原地址加押需按商户退押地址发出24小时后过报时办理退押 3.特殊情况退押规定: 商户只能公群老板有退押权限, 如特殊情况群老板失联,业务员要退押需提供密保和原地址加押核实身份: 1)业务员原地址退押且可以提供密保核实,申请办理退押,挂起7天后办理退押 2)业务员非原地址退押且可以提供密保核实,申请办理退押,挂起7天后办理退押

2

12 Jan 2025, 06:04 UTC692 viewsread 8 August 2026

土豆担保 - 关于密保和原地址 为了确保公群的资金安全,我们在此公告如下: 开群群老板头衔可设置密保用于特殊情况核实身份(如需设置密保请联系群内工作人员),密保只能群老板自己知道,不可告诉他人 1、无密保核实身份:第三方账户可提供原地址加押未设置密保或密保核实不对,群内置顶24小时声明无其他客户找来可恢复群老板头衔 2、无原地址核实身份:第三方账户可提供密保,群内置顶24小时声明无其他客户找来可恢复群老板头衔 3、跟换安全项:原群老板头衔/密保/原地址(开群上押的原地址,原地址不可更改);3个安全选项有密保有原地址可直接更换群老板头衔(如只有一个安全选项需群内置顶24小时);有原群老板头衔和原地址可重置密保(如只有一个安全选项需群内置顶24小时) 注:如出现特殊情况,原群老板头衔/密保/原地址三个安全选项谁的安全选项多默认谁为商户群老板,为公群资金安全,请各位商户保管好自己的安全选项

12 Jan 2025, 06:04 UTC534 viewsread 8 August 2026

土豆担保 - 骗子常用手法介绍 1.抄袭使用土豆担保头像、昵称、简介; 2.使用特殊字符模仿土豆担保用户名,如:小写L、字母O和数字0等; 3.抄袭头像、昵称、简介,不显示电话号码或用户名; 4.抄袭头像、昵称、将电话号码或用户名写入简介栏。 5.骗子不光会冒充我们的工作人员,还会冒充我们的大群、公群和交易群、把群简介资料复制的和我们真群一模一样,骗客户入群后再逐个进行诈骗。 6.将土豆担保用户名打乱顺序,比如将kfpd写成kfdp,将kfpd666写成是kfpd999之类 7.还有些骗子会完全复制正确信息后,在某些位置修改一部份来进行行骗,要注意核实,不要轻易下判断

12 Jan 2025, 06:04 UTC480 views0 reactionsread 8 August 2026

土豆担保 - 群老板和业务员账号安全注意事项 1️⃣设置业务员必须是线下认识的才行 1、业务员必须是线下认识的才行,网上认识的不行; 2、网上认识的业务员如果在群里面乱贴卡号、地址,卷钱跑路,造成的损失群老板需要全部承担; 2️⃣所有管理员账号必须设置二步验证,防止被盗号的风险 1、点开飞机设置-隐私和安全-两步验证-设置一个你自己知道的密码; 2、没有设置两步验证的飞机账号风险非常大的,设置以后只有知道你的两步验证密码才能登录你的飞机; 3️⃣设置只有好友可以拉群 点开飞机设置-隐私和安全-隐私(被邀请权限)设置为我的联系人,这样只有你认识的添加过联系人的好友才能拉你进群了,防止被人拉进模仿的公群; 4️⃣添加官方人员和客户好友并备注好信息 1、防止骗子冒充官方人员找群老板办理业务、收取费用; 2、注意把交易的客户加为好友并备注名字,防骗子混在中间插入个地址,让回款,下发到骗子那去了,告知客户把地址附在转账截图下面一

12 Jan 2025, 06:04 UTC375 views1 reactionsread 8 August 2026

土豆担保 - 公群日常管理注意事项 1️⃣ 群名、群简介、群规则编辑须知: 群名 1、公群群名12个字以内,需要写明业务类型; 2、群名可参考此格式【 24小时纯白资收u 】 简介 1、群简介50个字左右,写清楚业务范围,让客户清楚的了解; 2、群简介的内容会通过链接预览展示给客户,能起到宣传推广作用; 群规 1、群规根据经营的业务类型制定,规则尽量详细一点,避免交易过程中产生纠纷; 2、规则制定可以通过土豆公群【@tdgq】参考其他老板怎么制定群规; 3、规则制定前可先关注土豆担保仲裁原则【@hwdbzc66】,学习关于规则注意事项,可以减少或避免纠纷; 2️⃣公群交易流程要求 1、交易前,请客户先关注 @tdkf33 ,看清楚群规则,谈好交易内容,确认到账核对【地址、账号】后再进行支付; 2、付款后将支付截图发群内并附带收款地址,群老板查收到账下发记账,将回款截图发群内让客户查收; 3、【地址、账号】记录必须发在群

👍1

12 Jan 2025, 06:04 UTC338 viewsread 8 August 2026

土豆担保 - 公群注意事项 一、开群和退押须知 1、开群请先关注公群商户频道【@tdsh888】了解如何管理经营公群,群内提醒客户请勿相信私聊发群链接的,都是骗子,请直接拉黑; 2、新开公群会登记到 土豆公群【@tdgq】内,如发现未上公群导航,请第一时间联系交易员; 3、开群后添加官方人员好友并备注信息,防止骗子冒充; 4、设置业务员必须是线下认识的才行,网上认识的不行,业务员出现的问题视为群老板全责; 5、所有管理员账号必须设置二步验证,防止被盗号,若出现账号被盗造成客户损失,群老板全责; 6、置顶信息不能超过3条,官方人员的置顶信息不能取消,群内交易的信息不能删除,有纠纷的用户不能踢出群,发现后会永久收回置顶和踢人、删消息权限; 7、公群老板和业务员非必要情况不要修改用户名,如需修改用户名请第一时间联系交易员报备,擅自变更用户名公群内出现一切问题群老板全责,VIP公群群老板修改用户名前报备交易员下公群导航联系人,更换好后

12 Jan 2025, 06:04 UTC279 views1 reactionsread 8 August 2026

土豆担保 - 公群收费标准 公群推广费200U,下押关群,以下为各类型公群收费标准 第一类: 1、代收/承兑/群内跑分 /银行卡套现/卡密核销/聚合码 上押15000U起,月费500U; 注:公群做收现业务需加押5000U封存,不能做为交易金额; 2、APP后台跑分 上押50000U,月费900U,群内需老板每日提供后台数据; 3、VIP小公群 ① 金流类,月费300U; 代收/承兑 上押15000U 注:公群做收现业务需加押5000U封存,不能做为交易金额; 收U代付 上押30000U起,其中20000U作为交易额度 ,10000u 封存: ②非金流类,月费200u 4、汇旺美金/汇旺U/ABA 互换 上押20000U,月费500U 第二类: 1、解封银行卡工商9920 /解封交易所支付宝/ POS机出售 上押15000u,月费200u ,交易佣金3%; 2、搭建类/代办公户/三方、四方进件 上押15000u,月费

1

12 Jan 2025, 06:03 UTC270 views2 reactionsread 8 August 2026

土豆担保 - 公群交易流程 1、进群后请先确认是否为官方公群,可以联系 @tdkf 进行验证 2、验证真群后首先要确认群内管理员身份,认清群老板以及业务员,并了解置顶消息中的交易规则后,查看群名状态以及群押金再进行交易。 3、交易前要确认群内是否有未完成的交易,检查当前机器人记账是否已回清,入款前询问下当前是否有款未回,翻下聊天记录查看上一位用户是否已回复到账,得到明确回复后再开始进行交易。(注:如交易时需要一定时间才能完成交易的用户必须要在公群内说明情况并告知后面交易客户,且需自行关注群内交易情况,如未在群内告知后果自负)没有确认清账导致超押入款的,如果群老板跑路,超押部分将不赔付。 4、交易过程中所有账号、地址、截图相关信息一定要在群里进行,涉及个人隐私的可以部分以星号代替,并私聊发完整的。土豆担保只保障在当前交易群内的交易,私下交易或其他地方交易,后果自负,不要相信任何私聊,很可能是骗子冒充的,若交易出现纠纷,私聊截图不

2

12 Jan 2025, 06:03 UTC242 views1 reactionsread 8 August 2026

土豆担保 - 交易说明 一:供需双方在担保群查阅供求信息,选定交易目标后,联系 @tdkf 安排交易群进行担保交易。 二:供需双方明确交易内容、商品和价格,自行协商完毕后,联系 @tdkf 安排交易群进行交易担保。 交易步骤(通用版): 第一步、供需双方联系土豆担保官 @tdkf 安排交易群对接,非土豆担保工作人员建群一律无效; 第二步、供需双方需在土豆担保交易群内协商并确认交易详情,如:商品描述、收货标准、结算日期、收款标准、交易金额、交易数量、佣金金额、手续费等相关内容。 第三步、由交易员汇总编辑买卖双方交易详情并最终由买卖双方确认后方可正式开始交易; 第四步、买家将货款转入土豆担保上押账户并提供转账截图; 第五步、由交易员确认收款后通知卖家发货; 第六步、卖家接到交易员发货通知后开始发货,并提供发货凭证; 第七步、买家确认收货后通知交易员放款; 第八步、收到买家收货确认或放款通知后交易员扣除佣金向卖家解押放款,并提供转

1

12 Jan 2025, 06:03 UTC272 views2 reactionsread 8 August 2026

土豆担保 - 公群对接业务注意事项 1. 确认公群真实性:进入公群后请先确认是否为土豆官方公群,可以使用 @tdqg 验群或联系 @tdkf进行验证 2. 核实管理员身份:对接公群业务时,请认准带群老板以及业务员头衔的公群管理员,避免他人冒充行骗。 3. 谨慎私聊:不要相信主动私聊的人员,若有人声称是公群相关人员,请参考注意事项1、2核实公群及管理员身份。 4. 遵守公群规则:在公群内做业务前,务必查看公群置顶的业务规则,确保了解并遵守,以免引起纠纷。 5. 查询报备状态:业务前先查询记账/报备机器人的最新状态,确认公群是否超压。如有超压,请联系群内交易员。 6. 报备交易:进行业务时,务必联系公群老板或管理员进行报备,报备后方可有效担保。报备异常时,请及时联系群内交易员。 7. 担保范围:担保仅针对公群,不涉及个人,不对公群老板的个人信誉做保证。 8. 处理纠纷:如遇纠纷,请联系 @tdkf 纠纷/违规举报窗口

1👍1

Showing the 12 most recent of 13 posts we hold for @tdgql668. 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.

Citation-graph rank

Citation-graph rank — 632,715 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“土豆公群做业务注意事项” (@tdgql668), 297 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/tdgql668.

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.