Telegram RegisterThe public register of Telegram
Telegram profile photo for xendr4xGSI

Channel

xendr4xGSI

@xendr4xGSI

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

24subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1004303718275
TypeChannel
Username@xendr4xGSI
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live13 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/xendr4xGSI

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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 why it has no browse page of its own yet.

Growth

2310262.58 August 2026 — 24 subscribers17 August 2026 — 32 subscribers25 August 2026 — 40 subscribers1 September 2026 — 73 subscribers10 September 2026 — 88 subscribers19 September 2026 — 102 subscribers3 October 2026 — 23 subscribers3 October 2026 — 23 subscribers13 October 2026 — 24 subscribers248 August 202613 October 2026
9 measurements spanning 67 days. 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 11–114 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 16:3624+1
3 Oct 2026, 09:2223no change
3 Oct 2026, 09:2123-79
19 Sept 2026, 12:39102+14
10 Sept 2026, 22:3688+15
1 Sept 2026, 03:0373+33
25 Aug 2026, 05:1240+8
17 Aug 2026, 10:1332+8
8 Aug 2026, 03:4824first reading

Engagement

20 posts held, back to 20 September 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.

ERR · 30 days
170.0%
avg views ÷ 24 subscribers
Avg views / post
40.8
20 posts measured
Reaction rate
3.13%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 4 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 September 2026
Posts held20 (20 September 2026 – 22 September 2026)
Views total816
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Oct 2026, 09:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

7 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥457.1%
❤228.6%
🤮114.3%

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 4 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 7 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 20 September 2026 to 22 September 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

22 Sept 2026, 16:12 UTC47 views2 reactionsread 3 October 2026

OriginOS 7 Ported from PD2609 Android version : 17 Android SDK : 37 Incremental : 260919185055 Bitness : N/A Device name : PD2609 Device codename : PD2609 Platform : common (MTK) Manufacturer : vivo Brand : vivo Fingerprint : vivo/PD2609/PD2609:17/CP2A.260605.016/260919185055:user/release-keys Build type : user Build tags : release-keys Build ID : CP2A.2606…

❤1🔥1

20 Sept 2026, 14:14 UTC89 views4 reactionsread 3 October 2026

RealmeUI 7 From Realme GT5 Pro Android version : 16 Android SDK : 36 Incremental : RMX3888_16.0.10.500(CN01) Bitness : 64_32 Device name : ossi Device codename : ossi Platform : pineapple Manufacturer : oplus Brand : oplus Fingerprint : oplus/ossi/ossi:16/BP2A.250605.015/1786096021158:user/release-keys Build type : user Build tags : release-keys Build ID : …

🔥3🤮1

20 Sept 2026, 09:23 UTC62 views1 reactionsread 3 October 2026

ColorOS PLK110_17.0.0.100(SP09CN01) Ported from OnePlus 15 Android version : 17 Android SDK : 37 Incremental : PLK110_17.0.0.100(SP09CN01) Bitness : 64_32 Device name : ossi Device codename : ossi Platform : canoe Manufacturer : oplus Brand : oplus Fingerprint : qti/qssi/qssi:17/CP2A.260605.016/1789230075256:user/release-keys Build type : user Build tags : release…

❤1

20 Sept 2026, 09:23 UTC56 viewsread 3 October 2026

ColorOS PLK110_17.0.0.100(SP09CN01) Ported from OnePlus 15 Android version : 17 Android SDK : 37 Incremental : 1789230075256 Bitness : 64_32 Device name : ossi Device codename : ossi Platform : canoe Manufacturer : oplus Brand : oplus Fingerprint : qti/qssi/qssi:17/CP2A.260605.016/1789230075256:user/release-keys Build type : user Build tags : release-keys Build ID…

20 Sept 2026, 09:23 UTC49 viewsread 3 October 2026

HyperOS OS4.0.11.0.XPNCN Ported from Xiaomi 18 Fold Build info Android version : 17 Android SDK : 37 Incremental : OS4.0.11.0.XPNCNXM Bitness : 64-only Device name : lhasa Device codename : lhasa Platform : xring_o3_asic Manufacturer : Xiaomi Brand : Xiaomi Fingerprint : Xiaomi/lhasa/lhasa:17/CP2A.260605.005/OS4.0.11.0.XPNCN:user/release-keys Build type : user Build tags : release-keys Build ID : CP2A.260605.005 Buil…

20 Sept 2026, 09:23 UTC43 viewsread 3 October 2026

OriginOS 6 Ported from iQOO Neo9 Android version : 16 Android SDK : 36 Incremental : compiler260716112036 Bitness : 64_32 Device name : PD2338 Device codename : PD2338 Platform : kalama Manufacturer : vivo Brand : vivo Fingerprint : vivo/PD2338/PD2338:16/TP1A.220624.014/compiler260716112036:user/release-keys Build type : user Build tags : release-keys Build ID …

20 Sept 2026, 09:23 UTC41 viewsread 3 October 2026

WearOS Ported from Google Pixel Watch 4 Android version : 17 Android SDK : 37 Incremental : 15396605 Bitness : 32-only Device name : menari_btwifi Device codename : menari_btwifi Platform : monaco Manufacturer : Google Brand : google Fingerprint : google/menari_btwifi/menari_btwifi:17/CP2A.260603.001.S1/15396605:user/release-keys Build type : user Build tags : rel…

20 Sept 2026, 09:23 UTC40 viewsread 3 October 2026

OriginOS 6 Ported from iQOO 11 Android version : 16 Android SDK : 36 Incremental : compiler260723121343 Bitness : 64_32 Device name : qssi Device codename : qssi Platform : kalama Manufacturer : vivo Brand : vivo Fingerprint : vivo/PD2243/PD2243:16/BP2A.250605.031.A3/compiler260723121343:user/release-keys Build type : user Build tags : release-keys Build ID …

20 Sept 2026, 09:23 UTC35 viewsread 3 October 2026

Android GO Ported from OUKITEL C17 Mini GO Android version : 16 Android SDK : 36 Incremental : NNNNN20260805 Bitness : 64_32 Device name : C17_Mini_go_EEA Device codename : C17_Mini Platform : ums512 Manufacturer : OUKITEL Brand : OUKITEL Fingerprint : OUKITEL/C17_Mini_go_EEA/C17_Mini:16/BP2A.250605.031.A3/NNNNN20260805:user/release-keys Build type : user Build tags …

20 Sept 2026, 09:23 UTC33 viewsread 3 October 2026

AOSP ENG Ported from Xiaomi 15 Android version : 15 Android SDK : 35 Incremental : 241202.1.VOCCNXM.FACTORY Bitness : 64-only Device name : dada Device codename : dada Platform : sun Manufacturer : Xiaomi Brand : Xiaomi Fingerprint : Xiaomi/dada/dada:15/AQ3A.240812.002/241202.1.VOCCNXM.FACTORY:userdebug/test-keys Build type : userdebug Build tags : test-keys Build…

20 Sept 2026, 09:23 UTC34 viewsread 3 October 2026

MyUI Ported from Motorola Edge 40 Pro Android version : 16 Android SDK : 36 Incremental : 6262a5 Bitness : 64_32 Device name : rtwo_g Device codename : msi Platform : kalama Manufacturer : motorola Brand : motorola Fingerprint : motorola/rtwo_g/msi:16/W1TR36M-W1-ST34/6262a5:user/release-keys Build type : user Build tags : release-keys Build ID : W1TR36M-W1-…

20 Sept 2026, 09:23 UTC32 viewsread 3 October 2026

MyUI Ported from Motorola Edge 40 Pro Android version : 16 Android SDK : 36 Incremental : 6262a5 Bitness : 64_32 Device name : rtwo_g Device codename : msi Platform : kalama Manufacturer : motorola Brand : motorola Fingerprint : motorola/rtwo_g/msi:16/W1TR36M-W1-ST34/6262a5:user/release-keys Build type : user Build tags : release-keys Build ID : W1TR36M-W1-…

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

Mentions

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.

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

“xendr4xGSI” (@xendr4xGSI), 24 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/xendr4xGSI.

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.