Telegram RegisterThe public register of Telegram
Telegram profile photo for 资源交流共享

Channel

资源交流共享

@LFGJ88888

On this record: Growth · Engagement · Posts · Citations · Cite this entry

411subscribers

+107 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1002149166408
TypeChannel
Username@LFGJ88888
CreatedBetween 1 April 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/LFGJ88888

Growth

301448374.519 August 2026 — 304 subscribers19 August 2026 — 304 subscribers26 August 2026 — 303 subscribers2 September 2026 — 301 subscribers11 September 2026 — 448 subscribers19 September 2026 — 411 subscribers41119 August 202619 September 2026
6 measurements spanning 30 days, net +107. 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 279–470 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 09:56411-37
11 Sept 2026, 21:57448+147
2 Sept 2026, 23:59301-2
26 Aug 2026, 09:47303-1
19 Aug 2026, 23:15304no change
19 Aug 2026, 23:00304first reading

Engagement

15 posts held, back to 9 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 15 posts for this entry, the most recent from 16 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Aug 2026, 05:38 UTC51 viewsread 19 August 2026

长期专业收购对公账户 寻求各大户盘工作室 可提供扶持话术 诚邀具备实力的开户老板及车队相关负责人前来洽谈合作。 本司提供各种海外通道 有需要的盘总可前来咨询 业务不仅限于广告,欢迎各界有能力有资源有想法的有志人士共同发展

Signed 联发-焦皮(长期招户盘)

13 Aug 2026, 08:11 UTC80 viewsread 19 August 2026

空降se盘 长期招收卡接回u车队 大盘长期招收各种卡车 贴卡即射 效率高 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

11 Aug 2026, 06:10 UTC106 viewsread 19 August 2026

收支付宝人头无限收人 无需执照 过审直接就近周边安排 落地操作 变现快 效率高 收微信牛户人头 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

7 Aug 2026, 05:53 UTC134 viewsread 19 August 2026

色料长期招一道各种银行卡 大量缺卡 大小额来卡 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

4 Aug 2026, 05:53 UTC170 viewsread 19 August 2026

😁😁😁😁😁 ❗️需: 50-100-200-300-500大区户 ❗️需:500W—无限额,开通汇票功能户 ❗️需:1000W—无限额:地方银行、外资银行、村镇公户 😁😁😁😁😁😁😁😁 😁😁😁😁😁 ❗️需:加白名单公、私户银行办理渠道或白名单卡卡车队 ❗️需: 长期需50-500加白户 ❗️需: 资金盘保月承兑卡(要能实时查账的)

Signed 联发-焦皮(长期招户盘)

30 Jul 2026, 06:26 UTC186 viewsread 19 August 2026

需50—1000大区户 有货联系 需50—1000大区户 有货联系 需50—1000大区户 有货联系 需50—1000大区户 有货联系 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

30 Jul 2026, 03:55 UTC155 viewsread 19 August 2026

长期专业收购对公账户 寻求各大户盘工作室 可提供扶持话术 诚邀具备实力的开户老板及车队相关负责人前来洽谈合作。 本司提供各种海外通道 有需要的盘总可前来咨询 业务不仅限于广告,欢迎各界有能力有资源有想法的有志人士共同发展 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

27 Jul 2026, 02:37 UTC199 viewsread 19 August 2026
Photo

收支付宝人头无限收人 无需执照 过审直接就近周边安排 落地操作 变现快 效率高 收微信牛户人头 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

26 Jul 2026, 10:23 UTC151 viewsread 19 August 2026

浦发银行 光大银行 南京银行 平安银行 中信银行 北京农商 天津农商 广发银行 泉州银行 以上银行有对私额度即可 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

24 Jul 2026, 04:53 UTC177 viewsread 19 August 2026

来辆微信小额个人码车 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

21 Jul 2026, 09:00 UTC212 viewsread 19 August 2026

色料长期招一道各种银行卡 空降 车队 贷款车 平台卡 取现卡 扶贫卡 信用卡 什么卡都要 大量缺卡 大小额来卡 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

20 Jul 2026, 05:05 UTC219 viewsread 19 August 2026

长期专业收购对公账户 寻求各大户盘工作室 可提供扶持话术 诚邀具备实力的开户老板及车队相关负责人前来洽谈合作。 本司提供各种海外通道 有需要的盘总可前来咨询 业务不仅限于广告,欢迎各界有能力有资源有想法的有志人士共同发展 😁 @Jiaopi99

Signed 联发-焦皮(长期招户盘)

Showing the 12 most recent of 15 posts we hold for @LFGJ88888. 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 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“资源交流共享” (@LFGJ88888), 411 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/LFGJ88888.

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.