udah saat nya melamar jadi software engineer nya google ini

Channel
Jaa
@JaaGabu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,784subscribers
+156 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002699297862 |
|---|---|
| Type | Channel |
| Username | @JaaGabu |
| Created | Between 1 April 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 29 October 2026 |
| On Telegram | t.me/JaaGabu |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 43% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Oct 2026, 14:05 | 1,784 | +8 |
| 26 Oct 2026, 13:04 | 1,776 | +9 |
| 23 Oct 2026, 03:29 | 1,767 | +10 |
| 20 Oct 2026, 03:19 | 1,757 | +3 |
| 17 Oct 2026, 02:17 | 1,754 | +5 |
| 14 Oct 2026, 08:27 | 1,749 | +1 |
| 10 Oct 2026, 21:22 | 1,748 | +10 |
| 5 Oct 2026, 00:18 | 1,738 | +19 |
| 26 Sept 2026, 05:17 | 1,719 | +27 |
| 17 Sept 2026, 00:01 | 1,692 | +4 |
| 13 Sept 2026, 03:18 | 1,688 | +11 |
| 8 Sept 2026, 23:01 | 1,677 | +14 |
| 3 Sept 2026, 12:00 | 1,663 | +1 |
| 31 Aug 2026, 04:14 | 1,662 | +12 |
| 24 Aug 2026, 18:04 | 1,650 | +11 |
| 20 Aug 2026, 20:53 | 1,639 | +5 |
| 18 Aug 2026, 01:43 | 1,634 | -2 |
| 15 Aug 2026, 08:43 | 1,636 | +4 |
| 11 Aug 2026, 17:11 | 1,632 | +1 |
| 8 Aug 2026, 11:02 | 1,631 | first reading |
Engagement
20 posts held, back to 27 June 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 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 04s
- Average length
- 32s
Measured directly from 2 videos 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
26 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 53.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 53.8% | |
| 🎉 | 3 | 11.5% | |
| 😱 | 3 | 11.5% | |
| 👎 | 2 | 7.69% | |
| 🔥 | 2 | 7.69% | |
| 👍 | 1 | 3.85% | |
| 👏 | 1 | 3.85% |
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 26 reactions 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 27 June 2026 to 5 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
Bentar ya gua lagi sibuk bantuin pahrez buat update nya nanti lah kalo ini project dah selesai, kalian tau lah ini aplikasi apa
dah smooth kah?
❤3
rekor 10k user, gilak gak nyangka banyak yang pake ini plugin axvision, thanks buat semuanya yang udah make hehe🤧
🎉3
QIUNIXNew Gen, UI nya dari axvision wkwkw biasa lah mungkin gua rangkai lebih baik lagi di sini, btw kenapa bentuk logo nya sama karena gua terinpirasi dari karya game corner pahrez ntah kenapa bagus kalo pake filosofi mata hewan
❤2
What's new? - Speed-X Version 2.4.4 - UI Stable - Added Feature Gamer/Battery (Stable) - Added SPEEDXMODE (Shizuku) - Added Reboot Device (Shizuku) - Added RGB MODE - Added S-X MODE (Floating) - Added FPS selection 45/60/90/120/144 (Support) - Added Feature Frame-Graphics - Added Feature Crosshair-X - Added Gyro-X - Added Permission allow Automatic (Shizuku) - Add smooth animation to the application - Add Features G…
❤3🔥1
tapi gua bisa sih bikin versi offline cuma fitur nya terbatas dan gak bakal sama kayak yang di webui online
gimana ya gua bikin webui online tuh karena biar pemeliharaan nya lebih enak dan juga misal ada bug yang muncul di web ui nya bisa langsung gua benerin tanpa perlu update versi plugin lagi dan lagi pula ya kalo ku bikin offline juga bakal bikin file plugin nya bengkak dan gua gak mau itu, soal nya webui gua udah bukan html,css,js biasa gua pake framework jadi ya bakal berat
pake internet kalo buka web ui
👎1
perasaan bisa dah😑
👎1
Update Plugin AxVision | v1047-070726-S Build Date: 07-07-2026 Developer: @Reiieja Credit: @reljawa | @dcx400 | @HoyoSlave | @Kzuyoo Installation Support: AxManager Download Change Log: - Indonesia - English Note: Jika anda menemukan sebuah bug segera hubungi @Reiieja
❤1👏1
ui baru nya si tanpa update kalian bisa rasain tapi buat fitur baru nya belum bisa di rasain
Showing the 12 most recent of 20 posts we hold for @JaaGabu. 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.
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.
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 29 October 2026 — this entry's latest reading, not the date you are reading this.
“Jaa” (@JaaGabu), 1,784 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/JaaGabu.
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.