Telegram RegisterThe public register of Telegram
Telegram profile photo for 福州修车|精选资源

Channel

福州修车|精选资源

@pxinkuyoy

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

1,259subscribers

-20 since we began measuring on 5 September 2026

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

Register entry

Telegram ID-1003180485144
TypeChannel
Username@pxinkuyoy
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 September 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/pxinkuyoy

Growth

1,2591,2791,2695 September 2026 — 1,279 subscribers5 September 2026 — 1,279 subscribers8 September 2026 — 1,270 subscribers12 September 2026 — 1,273 subscribers17 September 2026 — 1,259 subscribers5 September 202617 September 2026
5 measurements spanning 11 days, net -20. 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,256–1,282 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 02:171,259-14
12 Sept 2026, 19:371,273+3
8 Sept 2026, 16:411,270-9
5 Sept 2026, 21:221,279no change
5 Sept 2026, 20:471,279first reading

Engagement

8 posts held, back to 25 August 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.

ERR · 30 days
1.18%
avg views ÷ 1,259 subscribers
Avg views / post
14.9
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 8 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 5 September 2026
Posts held8 (25 August 20265 September 2026)
Views total119
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Sept 2026, 21: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.

What this channel posts

Video runtime
34s
Average length
9s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

5 Sept 2026, 20:37 UTC1 viewsread 5 September 2026

🚀️雷电互推-BXF车🚀 AD: 问鼎/壹号/爆奖推荐100送100 🪽内射 翘臀 🪽探险与反差调教 🪽酒店上帝视角偷拍 🪽在线裸聊一对一👅包射包爽歪歪 🪽保定上门约 🪽🔥农村小学脱光全身检查🔞 🪽蜜桃🍑微密圈网红写真 🪽【色欲阁】高颜值口交口爆XP 🪽骚气小姐姐在线裸聊一对一👄 🪽文爱妹妹在线激情裸聊💋💋 🪽丰乳肥臀 🪽福州修车|精选资源 🪽珠海上门选妃总频道 🪽精品国漫🔥3D动画 🪽【惠州外围】全套上门验货付款 🪽91露出户外自拍 📁叮当猫互推机器人 互推交流: @leidianhutui111

5 Sept 2026, 20:31 UTC1 viewsread 5 September 2026

🚀️能量互推-B7车🚀 AD: TRX供应/能量租赁 1:全国莞式上门服务 2:福州修车|精选资源 3:暑假作业😍 4:精神小妹 5:我的初中女友 6:闷骚眼镜妹 7:反差女友泄密 8:大理上门约 9:免费机器人 机器人定制 AD: 中文搜索/超级引搜/飞机搜索 AD: 广告位招商

5 Sept 2026, 07:18 UTC4 viewsread 5 September 2026
Photo

🔥TeleTop 频道推荐 📢杏与糖 - 吃瓜探花阁 📢西安酒吧 商k 组团 接待狼友 📢GG精品 体育交锋 📢KL吉隆坡约爱LUCCY8000 📢MissAV 国产日韩欧美 📢烟台上门约 📢AV福利中心| 每日高清资源更新 📢重生之扫街大师 街拍美女 📢91TV - 精彩内容 📢全国上门服务【真实靠谱】 💎广告推荐 📢飞哥数据🌍SDK·DPI⚙️钉钉💰支... 📢⚽️注册送138🧧百家乐/棋牌/电竞体... 📢🅾️AG官网直营✅大客必备✅注册送15... 🔍互推公示 🪧流量互推说明

31 Aug 2026, 21:21 UTC17 viewsread 5 September 2026
Photo

🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道

28 Aug 2026, 09:23 UTC25 viewsread 5 September 2026
Photo

牛奶🥛肌肤 三点粉嫩 身体超级棒,口活一流,一碰就流水 女朋友感觉,甜美,温柔,听话,懂事 ❣️无需提前任何费用即可安排 🈶照片可选人,低消费,高质量❗️ 💯专业资源💯安全靠谱💯合作愉快💯 🌹唯一客服🛫TG:@chayuanyuan1 🌹双向限制🛫TG: @chayuanyuan1bot

28 Aug 2026, 09:20 UTC24 viewsread 5 September 2026
Photo

04。 166D 首次兼职✨ ✨南方甜妹 皮肤白皙 天然零整 可纯可欲✨ 真实在校生无纹身 不抽烟 无任何不良嗜好 常年健身完美身材 蜜桃臀 马甲线🥢筷子腿 高素质 双商在线,谈吐优雅

28 Aug 2026, 09:12 UTC20 viewsread 5 September 2026
Photo

天然无整容 甜美女友感 · · 皮肤白滑 波涛汹涌 温柔体贴 · 🌟真心期待与您的相遇🌟 ❣️无需提前任何费用即可安排 🈶照片可选人,低消费,高质量❗️

25 Aug 2026, 18:51 UTC27 viewsread 5 September 2026
Photo

小细腰 筷子腿 极品漫画身材 • 气质大牌 双商超高 不催不事 配合度极高 • 喜欢健身 全身柔软 可解锁各种姿势

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

“福州修车|精选资源” (@pxinkuyoy), 1,259 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/pxinkuyoy.

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.