Photo, posted without a caption

Channel
车速过快🚦开车娱乐搞笑沙雕
@chesgk
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
5,119subscribers
-35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001312318383 |
|---|---|
| Type | Channel |
| Username | @chesgk |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/chesgk |
Topic
Memes & entertainment — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 08:16 | 5,119 | -1 |
| 12 Sept 2026, 02:00 | 5,120 | -13 |
| 7 Sept 2026, 22:16 | 5,133 | -9 |
| 2 Sept 2026, 11:04 | 5,142 | -3 |
| 30 Aug 2026, 13:54 | 5,145 | +3 |
| 25 Aug 2026, 00:03 | 5,142 | +1 |
| 21 Aug 2026, 18:37 | 5,141 | +3 |
| 18 Aug 2026, 20:16 | 5,138 | -3 |
| 16 Aug 2026, 02:36 | 5,141 | +1 |
| 12 Aug 2026, 19:54 | 5,140 | -6 |
| 10 Aug 2026, 03:31 | 5,146 | -8 |
| 7 Aug 2026, 06:00 | 5,154 | no change |
| 7 Aug 2026, 05:50 | 5,154 | first reading |
Engagement
23 posts held, back to 27 June 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 8 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 23 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 6m 52s
- Average length
- 46s
Measured directly from 9 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
12 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 50.0% | |
| 😁 | 6 | 50.0% |
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 6 of the 23 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 27 June 2026 to 10 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
Photo, posted without a caption
Video, posted without a caption
❤1
Photo, posted without a caption
发明这个的简直是个天才
Photo, posted without a caption
Video, posted without a caption
Video, posted without a caption
重生之后
Photo, posted without a caption
Photo, posted without a caption
❤2
一千万以内最好的狗
😁1
Showing the 12 most recent of 23 posts we hold for @chesgk. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@meitian · 28,692
Telegram ranks this channel #1 of 20 here — alongside 19 others — read 9 September 2026
@aimeinv88 · 23,360
Telegram ranks this channel #2 of 20 here — alongside 19 others — read 18 September 2026
@z055q · 55,875
Telegram ranks this channel #9 of 43 here — alongside 42 others — read 19 August 2026
@ruheyushadiaoxiangchu · 28,742
Telegram ranks this channel #13 of 44 here — alongside 43 others — read 9 September 2026
@onlychigua · 200,649
Telegram ranks this channel #17 of 48 here — alongside 47 others — read 14 August 2026
@pdsss · 54,442
Telegram ranks this channel #19 of 51 here — alongside 50 others — read 23 August 2026
@tuigsc · 69,020
Telegram ranks this channel #19 of 48 here — alongside 47 others — read 21 August 2026
@ay2028 · 79,466
Telegram ranks this channel #31 of 57 here — alongside 56 others — read 18 August 2026
@cgbg8 · 107,027
Telegram ranks this channel #31 of 59 here — alongside 58 others — read 15 August 2026
@pingrangTV · 29,178
Telegram ranks this channel #38 of 45 here — alongside 44 others — read 8 September 2026
@goworkbitch · 24,812
Telegram ranks this channel #42 of 52 here — alongside 51 others — read 15 September 2026
@DNYQWCG · 79,837
Telegram ranks this channel #44 of 57 here — alongside 56 others — read 19 August 2026
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“车速过快🚦开车娱乐搞笑沙雕” (@chesgk), 5,119 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/chesgk.
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.