Channel
@TomyJan_Channel
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,568subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001781771239 |
|---|---|
| Type | Channel |
| Username | @TomyJan_Channel |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/TomyJan_Channel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 05:48 | 3,568 | -3 |
| 9 Aug 2026, 15:14 | 3,571 | -1 |
| 6 Aug 2026, 22:27 | 3,572 | +1 |
| 6 Aug 2026, 09:04 | 3,571 | first reading |
22 posts held, back to 31 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 3 pagesof Telegram’s post history, 20 posts per page.
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 8 of 21 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 22 (31 July 2026 – 7 August 2026) |
| Views total | 8,587 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:08 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.
16 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 62.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 10 | 62.5% | |
| 🤣 | 5 | 31.3% | |
| ❤ | 1 | 6.25% |
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 8 of the 22 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 24reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 31 July 2026 to 7 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.
sub2api 曝 OAuth 高危漏洞，仅凭邮箱即可接管账户 sub2api v0.1.171 及之前版本存在一个 CVSS 8.8 的高危 OAuth 账户接管漏洞。攻击者仅需知道受害者注册邮箱，无需密码或验证码、无需用户交互，即可通过接口将自己的 OAuth 身份绑定到受害者账户，完全控制其 API 密钥、账单余额与订阅配额。 攻击者利用 pending session 流程中 existingUser 分支不校验密码和验证码的缺陷，将目标用户 ID 设为受害者后完成 OAuth 身份绑定。此后攻击者每次 OAuth 登录均会解析为受害者账户。 Github Issues 🌸 在花频道 · 茶馆水群 · 投稿通道
Signed TomyJan | Fatal Error
SyncTV 发布了使用 Rust 重构的 1.0.0 版本
Signed TomyJan | Fatal Error
明天的秋茶活动汇总 1. 沪上阿姨：10点开启，提供2万杯奶茶福利 2. 麦当劳：10点30分开启，放出100万杯“多汁柠柠”饮品 3. 茶百道：12点开启，提供2万杯免单福利 4. 爷爷不泡茶：全天活动，提供2万杯桂花系列奶茶 5. 蜜雪冰城：全天活动，提供10万杯黄桃霸果饮品 6. 书亦烧仙草：全天活动，提供2万杯新品，部分新品0.1元即可购买 7. 幸运咖：全天活动，提供1000杯苹果系列饮品 8. 霸王茶姬：全天活动，提供10万杯饮品，还有0.01元的宠物季·成品兑换券 9. 益禾堂：全天活动，提供1万杯新品 10. CoCo都可：全天活动，抽10万杯凤梨可乐达，该款饮品还有买一送一福利 11. 奈雪的茶：全天活动，提供500杯饮品，还可抽取单杯饮品免单券
Signed TomyJan | Fatal Error
ITDOG 端点接入自动化了, 但是只给了脚本没给 Docker , 所以我糊了个 Docker 镜像, 有需要进 github.com/TomyJan/itdog-agent Tip:一个月 80 块钱喔, 仍有很多地区有缺口可接入喔
Signed TomyJan | Fatal Error
https://dazui.is-a.dog/
Signed TomyJan | Fatal Error
麦当劳甜筒, 今天过期, 有需要速领 1美团黑钻黑金会员送你麦当劳圆筒冰淇淋❤️复制整条信息，打开👉美团👈 http:/💰s1NDM2ZmJhZTY💰
❤1
Signed TomyJan | Fatal Error
via 豆达虫
Signed TomyJan | Fatal Error
Photo, posted without a caption
Signed TomyJan | Fatal Error
小飞棍来咯
Signed TomyJan | Fatal Error
https://api.reizeiin.xyz/
Signed TomyJan | Fatal Error
能看出来小米很高兴...
🤣5
Signed TomyJan | Fatal Error
Photo, posted without a caption
Signed TomyJan | Fatal Error
Showing the 12 most recent of 22 posts we hold for @TomyJan_Channel. 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 — 79,816 of 1,345,403entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“听荼蘼逼逼 | 多打点🤡” (@TomyJan_Channel), 3,568 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/TomyJan_Channel.
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.