Channel
@AimBuddy
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
107subscribers
+6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003850709312 |
|---|---|
| Type | Channel |
| Username | @AimBuddy |
| Created | Between 1 February 2026 and 6 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/AimBuddy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 11:34 | 107 | +3 |
| 15 Aug 2026, 01:23 | 104 | +3 |
| 9 Aug 2026, 10:32 | 101 | no change |
| 7 Aug 2026, 19:02 | 101 | first reading |
20 posts held, back to 6 April 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 1 pageof 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 20 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.
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.
33 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 57.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 57.6% | |
| 🔥 | 6 | 18.2% | |
| 👎 | 4 | 12.1% | |
| 👍 | 1 | 3.03% | |
| 😁 | 1 | 3.03% | |
| 🙏 | 1 | 3.03% | |
| 🥰 | 1 | 3.03% |
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 13 of the 20 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 33reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 6 April 2026 to 4 June 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.
I would now be working towards building models for multiple games including PUBGM, CODM and Standoff 2, hopefully this would improve adoption and get people to start self building model's themselves too. ~ @XCode
Signed XCode
Commit #c713b87 UX overhaul and critical APK installation fix. Added: Premium Compose-based Model Store UI replacing legacy Alert Dialogs. Features tabs for browsing available models from GitHub and managing installed models with options to download, switch, and delete models. Support for deleting downloaded/imported model files through the UI. Fixed: Fixed immersive landscape layout breaking/shifting by implement…
❤1
Signed XCode
All upcoming new releases would be released only on GitHub Releases · 1337Xcode/AimBuddy
Signed XCode
AimBuddy is almost nearing towards stable release, I highly hope that people would start contributing towards model development now that model marketplace has been integrated. ~ @XCode
❤5👍1🥰1🙏1
Signed XCode
Changed: Updated mermaid diagrams across docs/Architecture.md, docs/Performance.md, and docs/Training.md to reflect the 4-slot ring buffer, event-driven aim loop, Shizuku permission branch, and the new automate.py end-to-end pipeline. Touch backends rebuilt for true user+aim parallelism: uinput (root): removed EVIOCGRAB on the real touchscreen and the reader thread that mirrored events back through uinput. The aimbot…
Signed XCode
Commit #7f5fd40 Tooling, docs, and release-automation pass on top of 0.2.0-beta.1. Major feature release. Touch parity, streamer mode, Chinese UI, redesigned launcher, full training-pipeline overhaul, and a significant runtime memory/CPU pass. Added: Beginner-friendly Shizuku setup guide at docs/ShizukuSetup.md covering wireless-debugging pairing, ADB start, root start, permission grant, post-reboot behavior, OEM b…
❤1
Signed XCode
Least you could do is Star the repo and/or contribute towards the models (working on some by myself too) https://github.com/1337Xcode/AimBuddy
❤1👎1
Signed XCode
For users with a PC, I'll be releasing a better variant of Touch Aimbot for non-root that requires a one-time ADB setup (so you can skip Shizuku entirely) and it works closer to the uinput-based Aimbot. PS: also adding a slower fallback variant for people who have <Android 11
❤1👎1
Signed XCode
Almost wasted an hour trying to optimize latency on Aimbot xd and again this is first ever Aimbot to ever work on non root without touching game memory and externally. More insane stuff to come in upcoming updates
❤1👎1
Signed XCode
Commit #bf93b26 Changelog: - Implemented Touch Stimulation Aimbot for Non Rooted users - Fixed Aim Logic to reduce stuttering Known Bugs: - Touch is sometimes blocked when using Shizuku based Aimbot on Non Rooted devices (fix will be addressed in next update) Requires Shizuku setup and running before using the app: https://play.google.com/store/apps/details?id=moe.shizuku.privileged.api&hl=en-US Repo: https://git…
❤2👎1
Signed XCode
Non root users no longer need to use Mods and VMs anymore xd
🔥6❤1
Signed XCode
Cooking something for non rooted users 👀
❤3
Signed XCode
Showing the 12 most recent of 20 posts we hold for @AimBuddy. 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 — 304,083 of 1,621,754entries 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.
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 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“AimBuddy” (@AimBuddy), 107 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/AimBuddy.
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.