Channel
@PersonalCodingHub
On this record: Growth · Engagement · Posts · Citations · Cite this entry
357subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001179739452 |
|---|---|
| Type | Channel |
| Username | @PersonalCodingHub |
| Created | 12 January 2021 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/PersonalCodingHub |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 06:52 | 357 | -2 |
| 7 Aug 2026, 01:01 | 359 | no change |
| 7 Aug 2026, 00:53 | 359 | first reading |
20 posts held, back to 8 April 2022 — 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 5 February 2023. An engagement rate over an empty window would be a number about nothing.
This exact same source is being sold by people. This source was very easy to update to begin with! Don't buy it from people who can't update the source by themselves or those who don't even understand the way the sock works. All they are doing is updating a leaked source which was not fully perfect. I made lots of changes afterwards and made it even more smoother. If you want an updated source, contact me! I am rea…
People are selling this now and claiming it as their own when I did this like months ago 😂 Instead of buying from their channels, support the real developer who actually built it ✌️ If you want something different and more stable than Desi, contact me @sagarshah1729
Any type of Source Updates for 2.4 is available for External sources. Bullet Track, SDK, CameraCache based ESP Sources, Desi source etc with ESP disappear fixes. @sagarshah1729
int bones[] = { 5,4,1,11,32,12,33,63,62,52,56,53,57,54,58 }; struct D3DMatrix getOMatrixLite(uintptr_t boneAddr) { float oMat[10]; pvm(boneAddr, &oMat, sizeof(oMat)); rot.X = oMat[0]; rot.Y = oMat[1]; rot.Z = oMat[2]; rot.W = oMat[3]; tran.X = oMat[4]; tran.Y = oMat[5]; tran.Z = oMat[6]; scale.X = oMat[7]; scale.Y = oMat[8]; scale.Z = oMat[9]; return ToMatrixWithScale(tran, scale, rot); } Skeleton Fix For Pubg L…
After 5 hours of building, it booted! ❤️
Dream PC Build ♥️✨
I am back! If you need anything for external PUBG/BGMI, I can help! ❤️ @sagarshah1729
To everyone who is messaging me in DMs, I am sorry, I am inactive since 3-4 days due to College's Final Year Project. Will be more busy for some time, so please wait and sorry for not responding to you guys.
Just completed Mild FOV Aimbot and Bullet Track (Camera Cache) with FOV Options! Ignore the lag here, it is due to very high ping (300+ due to VPN). Bugs in BT for now: - Only working while Hip Fire, works like FOV Aimbot during ADS - While shooting enemy, the ESP draw renders a fake Player @sagarshah1729
32Bit Personal ESP Source Update done! ❤️ No ViewMatrix or ViewWorld needed. Just GName and GWorld :)
Source updated for 64bit! So now, 32 and 64bit, both are available! ❤️ @sagarshah1729
Kuroyama Bullet Track for External with all FOV Features done! ❤️🙌 @sagarshah1729
Showing the 12 most recent of 20 posts we hold for @PersonalCodingHub. 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Coding Hub” (@PersonalCodingHub), 357 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/PersonalCodingHub.
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.