Telegram RegisterThe public register of Telegram
Telegram profile photo for 时间&频道(无广)

Channel

时间&频道(无广)

@TIMEPD

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

32,107subscribers

+23,453 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-1004389718692
TypeChannel
Username@TIMEPD
CreatedBetween 1 June 2026 and 27 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/TIMEPD

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 45% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

22,100 average views per post against 32,107 subscribers — an engagement rate of 68.7%. Across the 1,284 registered channels in the same cohort — 31,624–99,923 subscribers, posting mainly in Chinese — the middle half sit between 1.01% and 5.67%, with a median of 2.58%.

What this was computed from
Window30 days (28 August 2026 – 27 September 2026)
Posts measured43 of 43 published in the window (0 exact, 43 rounded by Telegram)
Views totalled948,450
Mature posts only70.9% over 41 posts read at least 24h after publication
Subscribers32,107 measured 18 September 2026
Cohortb31623:zho · 1,284 channels · p10 0.301% · p25 1.01% · p50 2.58% · p75 5.67% · p90 11.4%
Position in cohort99.922th percentile · 26.7× the cohort median
Uncertainty±0.019% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 27 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

8,65432,10720,380.57 August 2026 — 8,654 subscribers8 August 2026 — 8,717 subscribers11 August 2026 — 10,068 subscribers12 August 2026 — 10,423 subscribers13 August 2026 — 10,757 subscribers14 August 2026 — 11,352 subscribers16 August 2026 — 11,999 subscribers17 August 2026 — 12,507 subscribers18 August 2026 — 12,871 subscribers19 August 2026 — 13,276 subscribers20 August 2026 — 13,577 subscribers21 August 2026 — 13,870 subscribers22 August 2026 — 14,470 subscribers24 August 2026 — 15,023 subscribers25 August 2026 — 15,375 subscribers26 August 2026 — 15,770 subscribers27 August 2026 — 16,508 subscribers28 August 2026 — 17,215 subscribers29 August 2026 — 18,125 subscribers30 August 2026 — 18,668 subscribers31 August 2026 — 19,187 subscribers1 September 2026 — 19,535 subscribers2 September 2026 — 19,867 subscribers3 September 2026 — 20,223 subscribers4 September 2026 — 20,936 subscribers6 September 2026 — 24,209 subscribers10 September 2026 — 26,562 subscribers12 September 2026 — 28,566 subscribers14 September 2026 — 29,883 subscribers15 September 2026 — 31,000 subscribers18 September 2026 — 32,107 subscribers7 August 202618 September 2026
31 measurements spanning 42 days, net +23,453. 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 5,136–35,625 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
18 Sept 2026, 06:2132,107+1,107
15 Sept 2026, 22:1831,000+1,117
14 Sept 2026, 04:0129,883+1,317
12 Sept 2026, 08:3828,566+2,004
10 Sept 2026, 03:1826,562+2,353
6 Sept 2026, 21:1724,209+3,273
4 Sept 2026, 08:3520,936+713
3 Sept 2026, 00:2420,223+356
2 Sept 2026, 00:2719,867+332
1 Sept 2026, 00:1519,535+348
31 Aug 2026, 01:4619,187+519
30 Aug 2026, 02:1618,668+543
29 Aug 2026, 05:3418,125+910
28 Aug 2026, 04:0817,215+707
27 Aug 2026, 06:2516,508+738
26 Aug 2026, 06:3315,770+395
25 Aug 2026, 08:1315,375+352
24 Aug 2026, 10:3215,023+553
22 Aug 2026, 19:1614,470+600
21 Aug 2026, 07:5313,870first reading

Engagement

96 posts held, back to 27 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
68.7%
avg views ÷ 32,107 subscribers
Avg views / post
22,100
43 posts measured
Reaction rate
0.59%
reactions ÷ views · ER floor
Posts in window
43
of 96 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 26 September 2026
Posts held96 (27 July 2026 – 26 September 2026)
Views total948,450
Reactions total5,600
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 01:44 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
25
Videos
7
Links
6

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

Video runtime
3m 26s
Average length
41s

Measured directly from 5 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.

Reaction mix

8,943 reactions across 96 posts, in 38 distinct kinds. The most used accounts for 63.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5,63963.1%
❤1,44316.1%
🫡5946.64%
😭2412.69%
😱1551.73%
👎1301.45%
🤣1121.25%
🤡670.749%
😡660.738%
🖕640.716%
💩610.682%
😍500.559%
👏490.548%
😁410.458%
🔥310.347%
🤔290.324%
🤩290.324%
🤮180.201%
😢170.19%
🍌160.179%
18 further kinds911.02%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 96 of the 96 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 8,943 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 96 most recent posts we hold, published 27 July 2026 to 26 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

26 Sept 2026, 14:46 UTC≈7,140 views99 reactionsread 27 September 2026

主打失控 kpad2和y70 5代怎么选择?

👍91❤5😱3

26 Sept 2026, 14:30 UTC≈7,440 views108 reactionsread 27 September 2026

y705代对比4代有提升吗

👍96😱6❤4🤔2

25 Sept 2026, 07:16 UTC≈16,600 views165 reactionsread 27 September 2026
Photo

骗子电报id 8473372856 勿上当

👍121🖕17❤15😍8🔥3👏1

25 Sept 2026, 04:32 UTC≈17,800 views396 reactionsread 27 September 2026

部分人解密已和谐无效果,别玩了我们斗不过腾讯的

👍203😱69😭58🤡34❤19👎8🌭4😁1

25 Sept 2026, 01:13 UTC≈18,100 views100 reactionsread 27 September 2026

已修复无悬浮窗,重新下载即可

👍86❤11👎3

24 Sept 2026, 16:37 UTC≈19,000 views126 reactionsread 27 September 2026

谁推荐的阿古朵 牢死了😭

👍110❤9🙉7

Signed zhinese words

24 Sept 2026, 16:25 UTC≈19,000 views110 reactionsread 27 September 2026

王者荣耀,有没有那种明透就能百分百上分的英雄 不吃手法的,玩玄策老虎队友一个比一个能送😭不用考虑行为的问题 只要明透就行

👍94❤12🔥4

Signed zhinese words

24 Sept 2026, 13:01 UTC≈19,600 views90 reactionsread 27 September 2026
Video

🎮三角洲Apex公益算法解密 已更新三角洲最新算法解密 不闪框 不漏人 不遁地 不协议 Apex自研队列明文MRA算法解密 动态解密算法 防止对局内二次加密 ✨点我验证Apex算法解密真实性 😀官方频道:@ApexZPD

👍65❤19🤓3😍3

24 Sept 2026, 09:36 UTC≈23,500 views208 reactionsread 27 September 2026

三角洲云更新 14:35 on Sep 24, 2026 UpdateLog: 在设置-UI新增"显示图标"开关。 文字模式不再要音量键,直接点击文字即可召出菜单 优化自瞄 修复长弓大小地图 拷打国服最新加密 扳机加入长按和连点模式 修复扳机开镜模式的问题 加入自救和救援倒计时和进度条显示 在设置-字体中加入人物文字阴影开关,默认开 物资-物资的编辑按钮中 可设置价值单位 原数值 k w 默认原数值 优化cpu占用 加入第一次使用的配置向导 加入全图剩余人物显示 没有更新国际服 台湾服解密 云更新 https://t.me/time_pd/822 驱动频道 @time_pd_driver

👍133❤64🔥8👎3

24 Sept 2026, 04:44 UTC≈20,000 views182 reactionsread 27 September 2026
Photo

Photo, posted without a caption

👍110😱40🤩17❤7👎4🕊4

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

@TIMEPD edited 4 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
12 August 2026
Most recent edit
23 September 2026

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

22 Sept 2026, 16:10 UTCFinal Results4,200 voters approx.

更新什么新的游戏比较好

  1. 暗区35%
  2. 王者30%
  3. 怕不急14%
  4. 瓦手22%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 96 most recent posts we hold, published 27 July 2026 to 26 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“时间&频道(无广)” (@TIMEPD), 32,107 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/TIMEPD.

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.