Telegram RegisterThe public register of Telegram
Telegram profile photo for 金沙二道

Channel

金沙二道

@JSPAYGX

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

19subscribers

-6 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-1003596553732
TypeChannel
Username@JSPAYGX
CreatedBetween 1 December 2025 and 27 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live31 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/JSPAYGX

Growth

1925227 August 2026 — 25 subscribers8 August 2026 — 24 subscribers11 August 2026 — 24 subscribers16 August 2026 — 23 subscribers24 August 2026 — 22 subscribers31 August 2026 — 19 subscribers7 August 202631 August 2026
6 measurements spanning 24 days, net -6. 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 18–26 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 13:2719-3
24 Aug 2026, 08:1822-1
16 Aug 2026, 14:2523-1
11 Aug 2026, 11:0124no change
8 Aug 2026, 13:5224-1
7 Aug 2026, 18:5525first reading

Engagement

20 posts held, back to 27 February 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 20 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

28 Jul 2026, 11:04 UTC292 viewsread 11 August 2026

😀公出精聊/大区二道料 需大量二道保当天 保三承兑 😟 😀需:AB过三方 证券 期货承兑 底料换汇/拦截 😟 😀 😟👍 @uutt233

21 Jul 2026, 02:52 UTC279 viewsread 11 August 2026

📱大区二道公出现货100W 来对公大额承兑 可保当天/保三 单笔10W起打😀😟👍@uutt233

12 Jun 2026, 05:19 UTC447 viewsread 11 August 2026

📱大区二道公出现货80W 对私对公不限 可保当天/保三 单笔10W起打😀😟👍@uutt233

8 Jun 2026, 11:53 UTC129 viewsread 11 August 2026

😀😀 😀😀 😀😀😀 📱供股票大区二道料😟 📱供精聊二道料😟 📱供股配资二道料😟 📱供资金盘二道料😟 📱供大混三黑进算二道料😟 📱供科技二道料😟 📱以上料有:保当天、保三天 、保7天 进算 放料只收U 📱需2道各种回U车:😀😀😀 😃石油公对公(可提供三证报备) 😃京东公对公(可提供三证报备) 😃黄金公对公(可提供三证报备) 😀😀😀😀😀😀😀😀😀 现货叫车

31 May 2026, 05:04 UTC111 viewsread 11 August 2026

😀😀 😀😀 😀😀😀 📱供股票大区二道料😟 📱供精聊二道料😟 📱供股配资二道料😟 📱供资金盘二道料😟 📱供大混三黑进算二道料😟 📱供科技二道料😟 📱以上料有:保当天、保三天 、保7天 进算 放料只收U 📱需2道各种回U车:😀😀😀 😃石油公对公(可提供三证报备) 😃京东公对公(可提供三证报备) 😃黄金公对公(可提供三证报备) 😀😀😀😀😀😀😀😀😀 现货叫车

26 May 2026, 17:15 UTC83 viewsread 11 August 2026

😀😀 😀😀 😀😀😀 📱供股票大区二道料😟 📱供精聊二道料😟 📱供股配资二道料😟 📱供资金盘二道料😟 📱供大混三黑进算二道料😟 📱供科技二道料😟 📱以上料有:保当天、保三天 、保7天 进算 放料只收U 📱需2道各种回U车:😀😀😀 😃石油公对公(可提供三证报备) 😃京东公对公(可提供三证报备) 😃黄金公对公(可提供三证报备) 😀😀😀😀😀😀😀😀😀 现货叫车

13 May 2026, 16:44 UTC90 viewsread 11 August 2026

😀😀 😀😀 😀😀😀 📱供股票大区二道料😟 📱供精聊二道料😟 📱供股配资二道料😟 📱供资金盘二道料😟 📱供大混三黑进算二道料😟 📱供科技二道料😟 📱以上料有:保当天、保三天 、保7天 进算 放料只收U 📱需2道各种回U车:😀😀😀 😃石油公对公(可提供三证报备) 😃京东公对公(可提供三证报备) 😃黄金公对公(可提供三证报备) 😀😀😀😀😀😀😀😀😀 现货叫车

5 May 2026, 20:33 UTC89 viewsread 11 August 2026

😀😀 😀😀 😀😀😀 📱供股票大区二道料😟 📱供精聊二道料😟 📱供股配资二道料😟 📱供资金盘二道料😟 📱供大混三黑进算二道料😟 📱供科技二道料😟 📱以上料有:保当天、保三天 、保7天 进算 放料只收U 📱需2道各种回U车:😀😀😀 😃石油公对公(可提供三证报备) 😃京东公对公(可提供三证报备) 😃黄金公对公(可提供三证报备) 😀😀😀😀😀😀😀😀😀 现货叫车

17 Apr 2026, 18:11 UTC112 viewsread 11 August 2026

📱精聊大区公出保三 明天400万量 来大额卡车单笔20万起 📱精聊大区公出保三 明天400万量 来大额卡车单笔20万起 😟👍@uutt233

29 Mar 2026, 07:18 UTC591 viewsread 11 August 2026

📱精聊公出保当天现货100万 来大额卡单笔20万起 📱精聊公出保当天现货100万 来大额卡单笔20万起 😟👍@uutt233

28 Mar 2026, 07:33 UTC595 viewsread 11 August 2026

📱精聊公出保当天现货50万 来大额对公单笔10万起 📱精聊公出保当天现货50万 来大额对公单笔10万起 😟👍@uutt233

21 Mar 2026, 14:04 UTC674 viewsread 11 August 2026

📱预约明天大区/精聊保当天 公对公承兑 200+ 能吃的来约 📱预约明天大区/精聊保当天 公对公承兑 200+ 😟👍@uutt233

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

“金沙二道” (@JSPAYGX), 19 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/JSPAYGX.

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.