Telegram RegisterThe public register of Telegram
Telegram profile photo for 企业工具 接粉号 客服号

Channel

企业工具 接粉号 客服号

@axiuluo66888

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

92subscribers

+6 since we began measuring on 1 September 2026

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

Register entry

Telegram ID-1002047765522
TypeChannel
Username@axiuluo66888
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live18 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/axiuluo66888

Growth

8692891 September 2026 — 86 subscribers2 September 2026 — 87 subscribers10 September 2026 — 89 subscribers18 September 2026 — 92 subscribers1 September 202618 September 2026
4 measurements spanning 17 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 85–93 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 18:0292+3
10 Sept 2026, 09:1689+2
2 Sept 2026, 00:4887+1
1 Sept 2026, 11:3086first reading

Engagement

15 posts held, back to 24 July 2025the 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
334.8%
avg views ÷ 92 subscribers
Avg views / post
308
4 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
4
of 15 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. It is computed over the 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held15 (24 July 20251 September 2026)
Views total1,232
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 11:30 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
47s
Average length
47s

Measured directly from 1 video 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

26 Aug 2026, 00:19 UTC≈1,080 viewsread 1 September 2026

1️⃣出三合一企业微信主体🉑转云机 🉑转云机 🉑超管,已过获客 ,需要的滴滴

16 Aug 2026, 11:29 UTC198 viewsread 1 September 2026
Photo

二维码接粉 股票粉 任何粉都接 不死 不死 不死 新东西 来吃肉

19 Apr 2026, 07:03 UTC430 viewsread 1 September 2026
Photo

信广域,信广远方,域通八面 🤣🤣🤣网页和PC端更新重大更新 📱界面和交互优化,更美观, 省去不必要的操作 比如勾选隐私政策才能登录,现在去除登录更快捷 📱支持同一账号再多个web和桌面客户端登录 📱支持多个账号管理,随时切换账号 📱优化已读未读问题 📱页面顶部增加快捷切换账号区域,添加当前账号信息水印方便一眼就能看出登录的那个账号 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 😄😃😄😃😄😃😃🌟

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

“企业工具 接粉号 客服号” (@axiuluo66888), 92 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/axiuluo66888.

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.