Telegram RegisterThe public register of Telegram
Telegram profile photo for 福建(泉州厦门福州)车友总群公开榜

Channel

福建(泉州厦门福州)车友总群公开榜

@Fjxiucheziyuan

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

32,455subscribers

+743 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001422447821
TypeChannel
Username@Fjxiucheziyuan
Description福建车友总群 @fjcheyou 福建老司机群 @fjlaosiji
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Fjxiucheziyuan

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

23,60333,22428,413.57 August 2026 — 31,712 subscribers8 August 2026 — 31,563 subscribers9 August 2026 — 31,475 subscribers10 August 2026 — 31,359 subscribers11 August 2026 — 31,154 subscribers12 August 2026 — 31,086 subscribers13 August 2026 — 30,963 subscribers14 August 2026 — 30,627 subscribers16 August 2026 — 30,112 subscribers17 August 2026 — 29,750 subscribers18 August 2026 — 29,539 subscribers19 August 2026 — 29,152 subscribers20 August 2026 — 28,811 subscribers21 August 2026 — 27,955 subscribers23 August 2026 — 27,266 subscribers24 August 2026 — 26,737 subscribers25 August 2026 — 26,438 subscribers26 August 2026 — 26,243 subscribers27 August 2026 — 26,106 subscribers28 August 2026 — 25,718 subscribers30 August 2026 — 25,396 subscribers31 August 2026 — 25,212 subscribers1 September 2026 — 25,151 subscribers2 September 2026 — 24,945 subscribers3 September 2026 — 24,705 subscribers5 September 2026 — 24,427 subscribers9 September 2026 — 24,098 subscribers11 September 2026 — 23,603 subscribers13 September 2026 — 33,224 subscribers15 September 2026 — 32,919 subscribers16 September 2026 — 32,815 subscribers19 September 2026 — 32,455 subscribers32,4557 August 202619 September 2026
32 measurements spanning 43 days, net +743. 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 22,160–34,667 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
19 Sept 2026, 05:5732,455-360
16 Sept 2026, 21:5932,815-104
15 Sept 2026, 02:5932,919-305
13 Sept 2026, 10:3933,224+9,621
11 Sept 2026, 17:1523,603-495
9 Sept 2026, 00:0024,098-329
5 Sept 2026, 14:1524,427-278
3 Sept 2026, 16:5924,705-240
2 Sept 2026, 07:2324,945-206
1 Sept 2026, 03:4525,151-61
31 Aug 2026, 02:4625,212-184
30 Aug 2026, 00:4325,396-322
28 Aug 2026, 21:1825,718-388
27 Aug 2026, 19:2626,106-137
26 Aug 2026, 20:0426,243-195
25 Aug 2026, 20:0726,438-299
24 Aug 2026, 20:0726,737-529
23 Aug 2026, 06:3427,266-689
21 Aug 2026, 17:2727,955-856
20 Aug 2026, 17:1328,811first reading

Engagement

43 posts held, back to 7 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 69 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.57%
avg views ÷ 32,455 subscribers
Avg views / post
1,810
22 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
22
of 43 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 21 September 2026
Posts held43 (7 August 202621 September 2026)
Views total39,750
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 06:40 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

Photos
4,610
Videos
740
Links
694

Lifetime counters from Telegram’s own channel header, read 24 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
5m 01s
Average length
11s

Measured directly from 28 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

21 Sept 2026, 10:17 UTC≈2,000 viewsread 24 September 2026
Photo

【花名编号】#雪儿 【开课地区】#石狮 【联系方式】 ☎️点击获取 【标 签】 #400p #500p #半套 #全套 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️ 【老师报告】 报告1

20 Sept 2026, 03:50 UTC≈2,410 viewsread 24 September 2026
Photo

【花名编号】#叶子楣 【开课地区】#石狮 【联系方式】 ☎️点击获取 【标 签】 #600p #全套 #无限火力 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️ 【老师报告】 报告1 报告2 报告3 报告4

19 Sept 2026, 14:38 UTC≈2,380 viewsread 24 September 2026
Photo

【花名编号】#爽菲菲 【开课地区】#晋江 【联系方式】 ☎️点击获取 【标 签】 #500p #舌吻 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️ 【老师报告】 报告1

19 Sept 2026, 13:46 UTC≈2,200 viewsread 24 September 2026
Photo

【花名编号】#菲菲 【开课地区】#厦门 #湖里 【联系方式】 ☎️点击获取 【标 签】 #600p #水床 #无限火力 #包夜 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️

19 Sept 2026, 05:49 UTC≈1,600 viewsread 21 September 2026
Photo

【花名编号】#雨欣 【开课地区】#厦门 #湖里 【联系方式】 ☎️点击获取 【标 签】 #400p #500p #舌吻 #半套 #全套 #无限火力 #包夜 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️

17 Sept 2026, 09:36 UTC≈1,770 viewsread 19 September 2026
Photo

【花名编号】#小雨 【开课地区】#泉州 【联系方式】 ☎️点击获取 【标 签】 #700p #嫩妹 #舌吻 #可上门 #包夜 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️

17 Sept 2026, 05:45 UTC≈1,580 viewsread 19 September 2026
Photo

【花名编号】#沐子涵 【开课地区】#晋江 【联系方式】 ☎️点击获取 【标 签】 #600p #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️ 【老师报告】 报告1 报告2 报告3

17 Sept 2026, 03:21 UTC≈1,520 viewsread 19 September 2026
Photo

【花名编号】#爱丽丝 【开课地区】#泉州 【联系方式】 ☎️点击获取 【标 签】 #500p #半套 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️

16 Sept 2026, 09:46 UTC≈1,780 viewsread 19 September 2026
Photo

【花名编号】#可可 【开课地区】#晋江 【联系方式】 ☎️点击获取 【标 签】 #400p #舌吻 #嫩妹 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️ 【老师报告】 报告1

2 Sept 2026, 11:38 UTC≈1,080 viewsread 3 September 2026

🌏 华北地区/东北地区 天津 太原 石家庄 哈尔滨 大连 🌏 华中地区 郑州 南阳 新乡 武汉 武汉2 襄阳 长沙 衡阳 常德 🌏 华东地区 济南 济南2 临沂 枣庄泰安济宁 聊城 南京 苏州 淮安 南通 盐城 宿迁 扬州泰州镇江 徐州 连云港 无锡 常州 合肥 皖南 阜阳亳州 宿州淮北 蚌埠淮南 上海 杭州 宁波 湖州 嘉兴 绍兴 南昌 赣州 景德镇 福建 🌏 华南地区 广州 佛山 东莞 珠海 惠州 江门 中山 韶关 河源 南宁 柳州 海口 三亚 琼海 儋州 潮州揭阳 🌏 西南地区/西北地区 西安 兰州 重庆 成都 贵阳 遵义 昆明

2 Sept 2026, 08:28 UTC≈1,180 viewsread 3 September 2026
Photo

【花名编号】#瑶瑶 【开课地区】#厦门 #集美 【联系方式】 ☎️点击获取 【标 签】 #500p #舌吻 #无限火力 #包夜 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️

2 Sept 2026, 06:50 UTC≈1,180 viewsread 3 September 2026
Photo

【花名编号】#乐乐 【开课地区】#泉州 【联系方式】 ☎️点击获取 【标 签】 #500pp #半套 #视频验证 (点击查看标签说明) 【报告提交】 点击这里 ❗️如有发现老师是中介或代聊第一时间向管理举报❗️

Showing the 12 most recent of 43 posts we hold for @Fjxiucheziyuan. 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.

Posts edited after publishing

@Fjxiucheziyuan edited 12 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
22 September 2026

Mentions

Named by 2 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.

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.

“福建(泉州厦门福州)车友总群公开榜” (@Fjxiucheziyuan), 32,455 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Fjxiucheziyuan.

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.