Telegram RegisterThe public register of Telegram
Telegram profile photo for NFC POS 3D 碰碰 饼干料【综合频道】总押金5000u

Channel

NFC POS 3D 碰碰 饼干料【综合频道】总押金5000u

@newNFC3D

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

1,537subscribers

+196 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001107231541
TypeChannel
Username@newNFC3D
CreatedBetween 1 February 2017 and 31 July 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/newNFC3D

Growth

1,3411,5371,4397 August 2026 — 1,341 subscribers7 August 2026 — 1,341 subscribers8 August 2026 — 1,357 subscribers11 August 2026 — 1,408 subscribers15 August 2026 — 1,461 subscribers19 August 2026 — 1,493 subscribers22 August 2026 — 1,510 subscribers25 August 2026 — 1,537 subscribers7 August 202625 August 2026
8 measurements spanning 18 days, net +196. 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 1,312–1,566 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 18:061,537+27
22 Aug 2026, 11:241,510+17
19 Aug 2026, 03:351,493+32
15 Aug 2026, 16:451,461+53
11 Aug 2026, 21:431,408+51
8 Aug 2026, 12:451,357+16
7 Aug 2026, 22:221,341no change
7 Aug 2026, 19:381,341first reading

Engagement

16 posts held, back to 28 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
43.3%
avg views ÷ 1,537 subscribers
Avg views / post
666
16 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
16
of 16 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held16 (28 July 20267 August 2026)
Views total10,655
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 22:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

7 Aug 2026, 07:00 UTC445 viewsread 7 August 2026

😍 NFC 传卡种类 😍 💳 QR 内部 💳 TX 内部 💳 鲲鹏 (外卡) 🔥 💳 哪咤 💳 紫苹果 💳 瑞幸 💳 雷电 💳 闪电 💳 谷歌钱包 (超级推荐扫货) 💰 U9 (银联版) 💰 鲲鹏 (银联版) English language available ! Dm us : @Pos3D

6 Aug 2026, 16:44 UTC530 viewsread 7 August 2026

☀️ 八月份 POS ☀️ 🚩葡萄牙 Portugal🇵🇹 🚩蒙古 Mangolia 🇲🇳 🚩沙特 Saudi Arabia 🇸🇦 🚩印尼 Indonesia 🇮🇩 🚩内机 China 🇨🇳 🚩意大利大额 Italy 🇮🇹 🚩香港 Hong Kong 🇭🇰 🚩越南 Vietnam 🇻🇳 🚩老挝美金机 Laos 🇱🇦 稳定大 POS,提前预约。由于老板对工作不努力,所以急单通常接不了,敬请见谅 😅 @Pos3D

4 Aug 2026, 16:26 UTC633 viewsread 7 August 2026
Photo

☄️ 长期能接 FAB 滴滴 ☄️ 皆是谷歌电商大鱼 单品1500刀以上 能约的 Pos 滴滴 @Pos3D

4 Aug 2026, 06:47 UTC626 viewsread 7 August 2026

☄️ 目前拥有以下国家的卡 寻POS ☄️ ✔️ 新加坡 SG ✔️ 阿联酋 UAE ✔️ 英国 UK Looking for all country POS @Pos3D

3 Aug 2026, 17:12 UTC618 viewsread 7 August 2026

☄️ 寻可吃中东卡 与 英国卡 3D链接 ☄️ Looking for Pos and 3D payment link that can accept middle east Gulf card. 联系 @Pos3D

3 Aug 2026, 13:53 UTC652 viewsread 7 August 2026

☄️ 42 张阿联酋大卡 准备就绪 ☄️ 能接受阿联酋卡的 Pos 滴滴 能预付 / 上押 机器优先 @Pos3D

2 Aug 2026, 18:35 UTC700 viewsread 7 August 2026
Photo

☄️ 寻能接中东卡的 POS与3D链接 ☄️ ✔️阿联酋大卡寻各国有实力的Pos ✔️碰碰POS & 3D ✔️点位漂亮可谈 有意者联系 @Pos3D

2 Aug 2026, 15:17 UTC650 viewsread 7 August 2026
Photo

☄️ 海量各国大卡 ☄️ 可以针对不同 Pos 机吃的卡头准备卡 全新源码技术上卡 能合作的机主可滴滴 @Pos3D

2 Aug 2026, 12:29 UTC596 viewsread 7 August 2026

☄️ 八张中东FAB大卡 ☄️ 能接的滴滴 没打过的机子优先 @pos3D

2 Aug 2026, 10:59 UTC605 viewsread 7 August 2026
Photo

🫠 内部专用 / TX NFC QR 🫠 ✅一对一专用 ✅买一送三 ✅可以要求独立后台更新 ✅24小时客服 @Pos3D

1 Aug 2026, 08:04 UTC845 viewsread 7 August 2026
Photo

☄️ 寻大量英国Pos 英国虚拟碰 英国3D☄️ Looking for all resources in UK Pos 3D Link Soft Pos / Virtual Pos UK buyer 买手 长期大饭票 有资源一起来接洽 @Pos3D

Showing the 12 most recent of 16 posts we hold for @newNFC3D. 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 — 287,959 of 1,605,487entries 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“NFC POS 3D 碰碰 饼干料【综合频道】总押金5000u” (@newNFC3D), 1,537 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/newNFC3D.

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.