Telegram RegisterThe public register of Telegram
Telegram profile photo for tail -f /var/log/syslog/uz_abuse_list.log

Channel

tail -f /var/log/syslog/uz_abuse_list.log

@uz_abuse_list

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

125subscribers

+23 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003771250382
TypeChannel
Username@uz_abuse_list
CreatedBetween 1 February 2026 and 25 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/uz_abuse_list

Growth

102125113.57 August 2026 — 102 subscribers9 August 2026 — 102 subscribers16 August 2026 — 103 subscribers23 August 2026 — 122 subscribers9 September 2026 — 124 subscribers18 September 2026 — 125 subscribers7 August 202618 September 2026
6 measurements spanning 41 days, net +23. 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 99–128 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 07:56125+1
9 Sept 2026, 18:16124+2
23 Aug 2026, 19:03122+19
16 Aug 2026, 05:13103+1
9 Aug 2026, 10:16102no change
7 Aug 2026, 22:26102first reading

Engagement

12 posts held, back to 25 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 12 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
😁125.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 5 of the 12 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 25 May 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.

Recent posts

7 Aug 2026, 10:07 UTC655 viewsread 9 August 2026
Photo

JPKD2 / SGWSM1 / KRSK1 / MNUV1 7/8/2026 处理列表 处理账号 xigua666 对接的机场 :西瓜机场 坠机原因 是西瓜 欢迎支持大哥的机场,谢谢喵~ 处罚项目:对于这种傻逼直接删机没意思,名下的所有机器都被 sx 强制劫持到 https://xigua-96110.beihou.ru/

2 Jul 2026, 02:47 UTC330 viewsread 9 August 2026

不要尝试挑战 sx ,不是抓不到,只是暂时不想管

2 Jul 2026, 02:44 UTC342 viewsread 9 August 2026

https://t.me/uz_abuse_list/59 ITHK1 , KROC1 , SGRS1 , SGOC1 傻逼处理列表 坠机原因,拿去挂代理赚钱 用户 id daniuzhi 邮箱 [email protected] 曾登入 IP 地址 38.175.xxx.xxx - AS979 — NetLab Global 156.239.xxx.xxx - AS154321— CORENET CLOUD SDN. BHD. 240e:328:a902:: - AS17638 天津中国电信 43.255.xxx.xxx - AS42960 — VH Global Limited 181.214.xxx.xxx - AS211301 — Unesty Company 95.135.xxx.xxx - AS214677 — Matteo Martelloni trading as DELUXHOST 36.106.x

1 Jul 2026, 20:15 UTC276 viewsread 9 August 2026
Photo

操死你妈,哪一个畜生吧 SGRS1 拿去挂代理了,傻逼吧,免费机就是各种妖魔鬼怪 😅

23 Jun 2026, 16:04 UTC258 viewsread 9 August 2026
Photo

补一下 sx 在哪吒期间的数据,sgsh2 的某个小鸡,在某个时间,最高冲到 1.2w 的 tcp 连接

21 Jun 2026, 06:48 UTC238 viewsread 9 August 2026
Photo

21/6/2026 UKBT1 用户名 sxxxxxxx 已清退机场,坠机原因,机场太大被 iplark 收录

19 Jun 2026, 19:00 UTC≈1,260 views0 reactionsread 9 August 2026
Photo

再一次警告,SentinelX 不是跟你闹着玩的,此次抽查中,已封禁了 4个账号,还请各位,不要涉及非法网络攻击,文明上网,你我有责(这个只是部分数据) Uzumaru 这下子也是成为 ai 公司了

18 Jun 2026, 19:51 UTC236 views0 reactionsread 9 August 2026

SGRS1 10.111.111.12 462150 23: 401781 2323: 50473 8088: 9028 8372: 696 13139: 164 2280: 8 10.111.111.22 455441 23: 396314 2323: 49447 8088: 8978 8372: 697 443: 5 10.111.111.53 125891 23: 104446 2323: 12466 8088: 8883 80: 65 443: 31 KROC1 10.10.16.55 627341 23: 475104 8080: 86335 2323: 56493 8088: 8600 8372: 733 80: 47

7 Jun 2026, 17:25 UTC583 views3 reactionsread 9 August 2026
Photo

FROVH1 / JPNTT1 / MYTM1 / VNPT1 / KRSK1 8/6/2026 处理列表 处理账号 tha913803 对接的机场 :Yukihasu VPN / https://yukihasu01.vip/#/login / https://t.me/s/yuki_hasu 坠机原因 机场太大,被 iplark.com 收录 (不过 iplark 也真是司马了) 欢迎支持大哥的机场,谢谢喵~

3

25 May 2026, 11:04 UTC≈1,530 views0 reactionsread 9 August 2026
Photo

lucky0561 [email protected] 退款金额 3u 曾登入 ip (国外 ip) 45.78.54.42 - [HOSTING] AS25820 - IT7 Networks Inc - Japan 38.225.100.133 - [HOSTING] AS38001 - NewMedia Express Pte Ltd - Hong Kong 2406:ef80:2:5a34:49::a - [HOSTING] AS63473 - HostHatch, LLC - Singapore 142.91.99.218 - [HOSTING] AS59253 - LEASEWEB SINGAPORE PTE. LTD. - Singapore 曾登入 ip (国内 ip) 117.27.25.39 - [ISP] CHINANET Fujian province network - Zhangz

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

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

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

“tail -f /var/log/syslog/uz_abuse_list.log” (@uz_abuse_list), 125 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/uz_abuse_list.

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.