Telegram RegisterThe public register of Telegram
Telegram profile photo for 青龙担保公群

Channel

青龙担保公群

@qlgxgq

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

71subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001399863697
TypeChannel
Username@qlgxgq
CreatedBetween 1 May 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/qlgxgq

Growth

718 Aug 2026, 19:30 — 71 subscribers9 Aug 2026, 23:32 — 71 subscribers8 Aug 2026, 19:309 Aug 2026, 23:32
2 measurements spanning 1 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 70–72 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 23:3271no change
8 Aug 2026, 19:3071first reading

Engagement

20 posts held, back to 1 November 2021the 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 5 October 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
10

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

Recent posts

5 Oct 2024, 16:12 UTC≈4,690 viewsread 9 August 2026

要发供需的去我朋友那里和我效果一样 https://t.me/wd999

5 Oct 2024, 16:11 UTC≈4,680 viewsread 9 August 2026

青龙供需休息一段时间,过几个月重新起航!

31 Dec 2022, 03:51 UTC≈25,300 viewsread 9 August 2026

为了新老客户感谢对青龙的支持 🎉🎉🎉🎉🎉🎉 供需一次性充值5条广告赠送1条 供需一次性充值10条广告赠送3条 (随时可用) 活动时间:永久有效 置顶福利 火热招商中🔥 单条发布广告7u/50元一条 置顶一天➕发布2条18U或130元 置顶三天➕一天2条48U或350元 置顶一周➕一天2条90U或660元 置顶一月➕一天2条200U或1450元 晚上供需最后1条12U/88元

1 Sept 2022, 09:15 UTC≈25,200 viewsread 9 August 2026

📣公群收费正式通知❗️❗️ 注:1对1私群担保收费押金5%/每个月 即日起、开设公群可自选两种收费方式! 【青龙VIP担保公群】 一:管理费5%每月、下押收取手续费5%、公群退押后归属于公群老板。 二:来自于担保负责人账号本身的流量、如用户向灰产提问找谁做单、青龙会轮流推送给对应行业的VIP公群。 【青龙担保常规公群】 一:公群只收取管理费!无其他任何费用! 200U-900U 每个月7% 1000U-10000U 每个月5% 二:公群只负责推送到公群频道、以及公告频道。每个月按照上压金额赠送广告发布 每100u送1次 三:公群使用青龙担保建立的备用群!退押后收回公群留以备用。 【公群交易必读❗️】 ✅温馨提示:开公群并不等于青龙必须保证你的生意。做生意靠自己、公群给予你信用背书、和一定的流量支持.祝愿青龙的公群老板们生意兴隆!

1 Jan 2022, 08:29 UTC≈21,900 viewsread 9 August 2026

每天来发供需的人都在问 能不能包效果包效果能上多少人?这个问题简直就是废话 但凡动点脑子都不至于。效果好不好,还是那句话 看你的广告内容,以及客户的需求,我这里人是有。但是也不是每天都盯着我频道看的,供需发布一次能上个 30-50人的我特么的都不信,明显假,不可能每天都会有30-50 人在盯着你打广告.

10 Nov 2021, 08:54 UTC≈22,700 viewsread 9 August 2026

声明: 所有交易请经过青龙担保官方拉群,三方确认之后再进行交易,未通过青龙官方担保,私下交易如有被骗与我方无关,交易需谨慎。

Showing the 12 most recent of 20 posts we hold for @qlgxgq. 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 — 1,075,887 of 1,549,376entries 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.

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

“青龙担保公群” (@qlgxgq), 71 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/qlgxgq.

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.