Telegram RegisterThe public register of Telegram
Telegram profile photo for 灵车漂移

Channel

灵车漂移

@Hearse_Drifting

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

10,411subscribers

+12 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001317151537
TypeChannel
Username@Hearse_Drifting
Created5 August 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/Hearse_Drifting

Growth

10,39910,41110,4056 August 2026 — 10,399 subscribers6 August 2026 — 10,405 subscribers9 August 2026 — 10,402 subscribers10 August 2026 — 10,405 subscribers11 August 2026 — 10,402 subscribers13 August 2026 — 10,404 subscribers14 August 2026 — 10,406 subscribers16 August 2026 — 10,411 subscribers6 August 202616 August 2026
8 measurements spanning 10 days, net +12. 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 10,397–10,413 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 02:0610,411+5
14 Aug 2026, 12:5710,406+2
13 Aug 2026, 02:5610,404+2
11 Aug 2026, 23:2710,402-3
10 Aug 2026, 22:5810,405+3
9 Aug 2026, 23:3510,402-3
6 Aug 2026, 22:5410,405+6
6 Aug 2026, 04:0710,399first reading

Engagement

17 posts held, back to 21 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
40.1%
avg views ÷ 10,411 subscribers
Avg views / post
4,180
1 post measured
Reaction rate
0.478%
reactions ÷ views · ER floor
Posts in window
1
of 17 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 3 August 2026
Posts held17 (21 March 20263 August 2026)
Views total4,180
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 18: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

Video runtime
7m 25s
Average length
7m 25s

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.

Reaction mix

923 reactions across 17 posts, in 25 distinct kinds. The most used accounts for 16.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁15416.7%
😱10611.5%
🤯10411.3%
🔥10110.9%
🤣788.45%
🤨596.39%
👍475.09%
🥰475.09%
353.79%
😇323.47%
🤡283.03%
👨‍💻242.60%
👏222.38%
💩222.38%
🤔192.06%
👻111.19%
🗿111.19%
👎80.867%
💊50.542%
🍾30.325%
5 further kinds70.758%

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

Measured over the 17 most recent posts we hold, published 21 March 2026 to 3 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

3 Aug 2026, 14:06 UTC≈4,180 views20 reactionsread 15 August 2026

https://t.me/PixelHubUpdates/4549 Google 给您表演一个更新 SE 固件

🤯163😁1

Signed septs

1 Jul 2026, 06:10 UTC≈10,400 views48 reactionsread 15 August 2026

已经不值了,现在奸商卖到 50-80,买改好的紫光壳子或者正经卡都不要这么多钱

😁43👍5

Signed webRTCCat | Present Day, Present Time

26 Jun 2026, 12:04 UTC≈19,500 views92 reactionsread 15 August 2026

Steam Controller 自动充电 https://fixupx.com/fossprime/status/2070013003752251660

🤣78🔥7👻3👍2🥰2

Signed septs

25 Jun 2026, 09:01 UTC≈9,930 views39 reactionsread 15 August 2026
Video

Pixel硬件熔断机制?T0级eSIM重大故障提醒 自系统更新版本260305 以来,国内外已经遇到很多eSIM不可用的案例。 症状是无法添加或移除 eSIM 卡,并且检查 *#*#4636#*#* 显示可用 eUICC 字节数为 -1。 主要受影响的是Pixel9系列,包括:Pixel9、Pixel9a、Pixel9Pro、Pixel9Pro XL、Pixel9ProFold。在其他型号上还没遇到过。 这个问题可能出现在所有地区版本中,包括美国、日本、澳大利亚和欧洲版本。 一旦触发,是不可逆的存在,类似于eUICC芯片熔断。降级到之前的系统版本或升级到Android Beta版本都无法解决。即使刷入GrapheneOS或其他第三方ROM也无法修复此问题。 推测主要原因:在我手上坏了十几个不止了,基本可以确定最有可能导致此故障的操作:更新到 260305 版本(或更高版本),解锁 Bootloader,然后再重新锁定。这个流程下

👍17💩12😁91

Signed septs

21 Jun 2026, 05:17 UTC≈8,900 views55 reactionsread 15 August 2026
Forwarded from @rynif

https://www.youtube.com/watch?v=g-8S8zk4dn8 https://scr.verylazypixels.com/ 亲测确实能开

🤯28👏22🥰3🤔2

Signed septs

16 Jun 2026, 10:35 UTC≈12,100 views15 reactionsread 15 August 2026
Photo

来自群友 @MiGanQWQ 的投稿 DJI Cellular 模块(TD-LTE 无线数据终端) PDD价格:32 投稿人注:可以作为LTE网卡使用 ------------------ 贩子炒麻了,没买的别买了 ------------------ 设备相关信息可见: 说明书 支持网页 论坛帖子中提到该模块中使用EG25-G(Cat.4 LTE模组) ------------------ 群友发现 讨论区群友找到的使用方法 模块拆解和天线优先顺序 切换模块VID&PID为移远设备 ------------------ 模块设备名可能为Baiwang(百旺),VID和PID为2CA3:4006,但是模块仍然为EG25-G DJI官方windows驱动 MODEM+AT+DM+NMEA端口驱动 EG25-G Linux驱动 EG25-G AT命令手册 ------------------ 模块默认工作模式为NDIS 若想要在平板

14😁1

Signed ꓕƎꓞuᴉꓞǝʌᴉsoldxƎ

19 May 2026, 01:24 UTC≈12,700 views18 reactionsread 15 August 2026

PD供电的3.5寸双盘硬盘盒 暂未正式发售 https://bilibilibb.com/BV1P79xBLENU

🤔171

Signed 无羽の翼 (「 • ̀ω•́ )「

14 May 2026, 12:47 UTC≈12,100 views96 reactionsread 15 August 2026
Forwarded from @laozhoubuluo_opcenter

2026 Linux 重置密码教程大全 - Dirty Cow (CVE-2016-5195) - Dirty Pipe (CVE-2022-0847) - io_uring UAF (CVE-2022-2602) - Copy Fail (CVE-2026-31431) - io_uring ZCRX freelist (CVE-2026-43121) - Dirty Frag (CVE-2026-43284 CVE-2026-43500) - Fragnesia (CVE-2026-46300) Ref: https://x.com/hsn8086k/status/2054798542062109001

🔥51😇31😁11💩21

Signed septs

12 May 2026, 10:55 UTC≈10,900 views69 reactionsread 15 August 2026

拦截猫App作者开发了个小硬件,解决 iPhone 骚扰电话拦截效果差的问题 硬件会模拟蓝牙耳机协议,通过蓝牙通道获取来电号码,再结合配置的规则进行识别与处理。 缺点:拦截距离 5-8 米,随身携带很麻烦,很适合固定场所 https://www.wolai.com/lanjiemao/3DiUSCMhTv2chPbvSruhKR

🤨59👎8👍2

Signed 无羽の翼 (「 • ̀ω•́ )「

11 May 2026, 00:58 UTC≈10,400 views63 reactionsread 15 August 2026
Photo

两块五一个的 35w PD 充电头 https://item.taobao.com/item.htm?id=1049741700232 #群友投稿

🔥43🤯10💊54😇1

Signed 无羽の翼 (「 • ̀ω•́ )「

6 May 2026, 09:21 UTC≈10,100 views61 reactionsread 15 August 2026
Forwarded from @CE_Observe

顺风车司机高速开智驾睡觉打呼噜,滴滴客服回应暂无技术手段实时监测 https://www.ithome.com/0/946/858.htm 滴滴出行客服工作人员表示,根据平台相关规定,顺风车默认是不允许使用智驾的,顺风车与滴滴快车等是不同的,顺风车司机多为兼职,与快车等营运车辆属性不同,目前平台暂无技术手段,无法实时监测司机是否违规使用智驾。如果乘客在订单期间发生任何问题,滴滴出行都会有专员跟进处理,乘客不用害怕。出现这种情况是他们监管不到位,导致出现危险驾驶情况,这个问题确实是他们的问题。 ———— 灵车漂移?

🤯47🤡10😁4

Signed septs

21 Apr 2026, 16:57 UTC≈14,100 views96 reactionsread 15 August 2026
Photo

广东移动推出算力 Token 套餐,现限时免费尝鲜 但是 http:// 来源: 1. https://x.com/Lonely__MH/status/2046535666054353218 2. https://linux.do/t/topic/2008619 3. https://www.163.com/dy/article/KQN9S5T50511C93M.html

😁70🤡18💩42🤓2

Signed septs

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

Citation-graph rank

Citation-graph rank — 278,413 of 1,481,217entries 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 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“灵车漂移” (@Hearse_Drifting), 10,411 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Hearse_Drifting.

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.