Telegram RegisterThe public register of Telegram
Telegram profile photo for <Coding/>

Channel

<Coding/>

@JARVIS_CODING

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

228subscribers

-3 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-1001467962253
TypeChannel
Username@JARVIS_CODING
Created10 April 2020 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded7 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/JARVIS_CODING

Growth

228231229.57 August 2026 — 231 subscribers7 August 2026 — 231 subscribers15 August 2026 — 230 subscribers23 August 2026 — 228 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net -3. 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 228–231 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 01:04228-2
15 Aug 2026, 04:25230-1
7 Aug 2026, 07:02231no change
7 Aug 2026, 06:48231first reading

Engagement

18 posts held, back to 14 May 2024 — 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 18 posts for this entry, the most recent from 11 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 May 2026, 05:43 UTC183 viewsread 7 August 2026
File

❄️ Recursive pointer scannner ( Breadth-First Search )

15 Mar 2026, 08:53 UTC240 viewsread 7 August 2026
Forwarded from @akatsukix1

✅ Software breakpoint hooking technique in Android for bullet track :- #include <jni.h> #include <signal.h> #include <ucontext.h> #include <asm/sigcontext.h> #include <sys/mman.h> #include <unistd.h> #include <android/log.h> #include <cstring> uintptr_t target_function_address = 0x0; void* dobby_trampoline = nullptr; void dummy_proxy() { LOGI("If you see this, the trap failed!"); } void swbp_sigtrap_hand…

6 Nov 2025, 15:06 UTC304 viewsread 7 August 2026
Forwarded from @CHICKENDINNER_TMFile

⭐️ 4.1~GLOBAL_Offsets32BIT.h 🟢 GWORLD = GWorld)+0x38)+0x58; 🟢GNAME = GNames) + 0x88; 🟢VMATRIX = GWorld) - 0x7c; ☄️ All offsets updated and correct for external esp

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

Republishes

Channels on the register whose posts this channel has forwarded.

暁 Akatsuki パラダイス
@akatsukix1 · 2,2612 postsChicken Dinner ™
@CHICKENDINNER_TM · 7281 post

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.

暁 Akatsuki パラダイス
@akatsukix1 · 2,2611 post

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

“<Coding/>” (@JARVIS_CODING), 228 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/JARVIS_CODING.

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.