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 · Citations · Cite this entry

18,668subscribers

+10,014 since we began measuring on 7 August 2026

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

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 live30 August 2026
Measurements held20
Confirmed unchanged1 time, most recently 30 August 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

18,700 average views per post against 18,668 subscribers — an engagement rate of 100.3%. Across the 2,744 registered channels in the same cohort — 10,003–31,596 subscribers, posting mainly in Chinese — the middle half sit between 1.72% and 10.7%, with a median of 4.27%.

What this was computed from
Window30 days (31 July 2026 30 August 2026)
Posts measured45 of 45 published in the window (1 exact, 44 rounded by Telegram)
Views totalled842,321
Mature posts only107.8% over 41 posts read at least 24h after publication
Subscribers18,668 measured 30 August 2026
Cohortb10000:zho · 2,744 channels · p10 0.558% · p25 1.72% · p50 4.27% · p75 10.7% · p90 22.4%
Position in cohort99.745th percentile · 23.5× the cohort median
Uncertainty±0.022% 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 30 August 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,65418,66813,6617 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 subscribers7 August 202630 August 2026
20 measurements spanning 22 days, net +10,014. 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 7,152–20,170 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
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,870+293
20 Aug 2026, 09:1213,577+301
19 Aug 2026, 11:3413,276+405
18 Aug 2026, 09:3312,871+364
17 Aug 2026, 12:1712,507+508
16 Aug 2026, 05:4711,999+647
14 Aug 2026, 16:4811,352+595
13 Aug 2026, 04:5810,757+334
12 Aug 2026, 04:5310,423+355
11 Aug 2026, 06:1110,068+1,351
8 Aug 2026, 00:518,717+63
7 Aug 2026, 17:318,654first reading

Engagement

61 posts held, back to 27 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 46 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
96.7%
avg views ÷ 18,668 subscribers
Avg views / post
18,100
49 posts measured
Reaction rate
0.365%
reactions ÷ views · ER floor
Posts in window
49
of 61 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 30 August 2026
Posts held61 (27 July 202630 August 2026)
Views total884,694
Reactions total3,227
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 20:00 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
16
Videos
5
Links
2

Lifetime counters from Telegram’s own channel header, read 30 August 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
1m 34s
Average length
31s

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

3,868 reactions across 61 posts, in 30 distinct kinds. The most used accounts for 64.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2,49864.6%
85722.2%
👎771.99%
😭721.86%
🤣411.06%
🖕401.03%
👏360.931%
💩280.724%
😍270.698%
🤡260.672%
😱250.646%
🤔250.646%
😁240.62%
🔥130.336%
🍌120.31%
🤩120.31%
🥰110.284%
😎100.259%
😢80.207%
🐳60.155%
10 further kinds200.517%

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 61 of the 61 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 3,868reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 61 most recent posts we hold, published 27 July 2026 to 30 August 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

30 Aug 2026, 09:25 UTC≈5,220 views86 reactionsread 30 August 2026
Photo

二改者(汐楠)已经找我抱歉并删除,此事告一段落

👍6511🤣8😁2

30 Aug 2026, 08:55 UTC≈5,210 views68 reactionsread 30 August 2026

Posted without readable text

👍40🤣223👏3

30 Aug 2026, 07:47 UTC≈7,690 views85 reactionsread 30 August 2026
Photo

要点比脸吗,二改给我名字都删了还不跟我说,死全家了吧 你前面还塞过后门远控 真是不要脸至极 改个module prop就是你的东西了吗

👍7110😱2👎1😎1

30 Aug 2026, 03:54 UTC≈6,660 views59 reactionsread 30 August 2026

推送了正式版云更新 三角洲 更新日期:2026/8/30 11:54 UpdateLog: 改一下水印位置 更改低分辨率设备的ui和字体显示大小

👍4312😁4

29 Aug 2026, 13:09 UTC≈8,740 views102 reactionsread 30 August 2026

你动资本蛋糕了😱😱😱芭比Q了

👍888👎4😇2

Signed 落花

29 Aug 2026, 13:04 UTC≈8,760 views128 reactionsread 30 August 2026

服务器又被cc了 空悲切

👍78😭30😱125😍2👎1

27 Aug 2026, 15:41 UTC≈13,100 views92 reactionsread 30 August 2026
Video

妈妈再也不担心我没有硫磺炸不死服霸了

👍4832🖕8😍4

26 Aug 2026, 16:44 UTC≈18,300 views105 reactionsread 30 August 2026
File

伪装DrmID模块,可过八宝粥设备标记导致的协议。

👍8519😁1

26 Aug 2026, 14:14 UTC≈16,700 views83 reactionsread 30 August 2026

解密没效果的重启一下手机

👍6411💩4😍4

26 Aug 2026, 13:56 UTC≈16,900 views136 reactionsread 30 August 2026

推送了正式版云更新 三角洲 更新日期:2026/8/26 21:56 UpdateLog: 加入udp解包解密,三服通用 Warning:不保证稳定性和安全性 自行测试稳定性

👍9034🐳4💩4😁4

Showing the 12 most recent of 61 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 3 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
30 August 2026

Citation-graph rank

Citation-graph rank — 470,496 of 1,627,068entries 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

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

“时间&频道(无广)” (@TIMEPD), 18,668 subscribers as measured 30 August 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.