Telegram RegisterThe public register of Telegram

Channel

色刷🆚金图 金兔

@jintuge

2 usernames

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

4subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002529817308
TypeChannel
Usernames@daifurmb @jintuge
Description官网一口价,喜欢的直接拍。 更多🆔用户名 @tg8tg 频道。 用usdt购买联系 @ganjiang 39#
Created15 May 2025measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/jintuge

Growth

413 Aug 2026, 01:46 — 4 subscribers13 Aug 2026, 09:32 — 4 subscribers13 Aug 2026, 01:4613 Aug 2026, 09:32
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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 09:324no change
13 Aug 2026, 01:464first reading

Engagement

13 posts held, back to 15 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 27 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
5

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

13 Sept 2025, 03:13 UTC114 views0 reactionsread 13 August 2026

😢NFT @jintu 金图ps 金兔5000u 😢NFT @seshua 色刷 2600u

27 Aug 2025, 18:56 UTC139 viewsread 13 August 2026

https://fragment.com/username/@seshua 😢NFT @seshua 色刷(色刷料)

26 Aug 2025, 21:56 UTC138 viewsread 13 August 2026

😢NFT @tuosan 托三 😢NFT @daifurmb 代付人民币 NFT @daifuqian 代付💰 😢NFT @jintu 金图ps 金兔 👍 😢NFT @seshua 色刷

26 Aug 2025, 21:49 UTC104 viewsread 13 August 2026

https://fragment.com/username/@daifurmb 😢NFT @daifurmb 代付人民币

20 Jul 2025, 23:16 UTC200 viewsread 13 August 2026

https://fragment.com/username/@jintu 金图ps 金兔 👍 😢NFT @jintu

20 Jul 2025, 23:16 UTC186 viewsread 13 August 2026

😢NFT @jintu 金图ps 金兔 👍 @jintuge 金兔哥 @jintujituan 金图 金兔集团

20 Jul 2025, 23:16 UTC182 viewsread 13 August 2026

NFT 官网一口价,喜欢的直接拍。🧧 更多nft用户名 @tg8tg 🇸🇰 NFT列表: 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- usdt 购买联系 @ganjiang 干将

20 Jul 2025, 23:01 UTC164 viewsread 13 August 2026

@jintu 金图 @jintu4 金兔 @jintu44 金兔 @jintu444 金兔 @jintu678 金兔 @jintu999 金兔 @jintu8888 金图 @jintuge 金兔哥 @jintuvip 金图vip @pituvip 批图vip @vippitu vip批图 @jintukefu 金图客服 @jtdbqunv 金图担保群 @jintudanbao 金图担保 @jintujituan 金图集团 @trxjtbot Trx金兔bot @trxjintu trx金图 @jintutrx 金兔trx @jintups 金图ps @psjintu ps金图 @pitu999 p图 @pitu_jintu p图_金图

Showing the 12 most recent of 13 posts we hold for @jintuge. 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 — 697,033 of 1,345,403entries 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 18 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.

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

“色刷🆚金图 金兔” (@jintuge), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/jintuge.

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.