Channel

GoAndroid

@officialgoandroid

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

1,889subscribers

-18 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	-1001420166461
Type	Channel
Username	@officialgoandroid
Created	Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	27 August 2026
Measurements held	7
Confirmed unchanged	1 time, most recently 27 August 2026
On Telegram	t.me/officialgoandroid

Growth

7 measurements spanning 19 days, net -18. 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 1,886–1,910 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
27 Aug 2026, 02:54	1,889	-2
23 Aug 2026, 17:03	1,891	-3
17 Aug 2026, 18:15	1,894	-1
14 Aug 2026, 16:16	1,895	-4
11 Aug 2026, 16:52	1,899	-8
8 Aug 2026, 11:05	1,907	no change
7 Aug 2026, 22:48	1,907	first reading

Engagement

20 posts held, back to 2 September 2025 — 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 20 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share	Share, drawn
❤	3	75.0%
👍	1	25.0%

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 5 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 4reactions 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 2 September 2025 to 20 April 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

20 Apr 2026, 17:09 UTC273 views1 reactionsread 7 August 2026

👍1

20 Apr 2026, 17:09 UTC264 viewsread 7 August 2026

20 Apr 2026, 17:09 UTC251 viewsread 7 August 2026

20 Apr 2026, 17:09 UTC221 viewsread 7 August 2026

20 Apr 2026, 17:09 UTC190 viewsread 7 August 2026

20 Apr 2026, 10:47 UTC185 views0 reactionsread 7 August 2026

20 Apr 2026, 10:47 UTC164 viewsread 7 August 2026

20 Apr 2026, 10:47 UTC143 viewsread 7 August 2026

20 Apr 2026, 10:47 UTC149 viewsread 7 August 2026

20 Apr 2026, 10:47 UTC143 viewsread 7 August 2026

19 Apr 2026, 21:52 UTC162 viewsread 7 August 2026

19 Apr 2026, 21:52 UTC158 viewsread 7 August 2026

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

Citation-graph rank — 573,086 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

GChromecast Hub
@gchromecast · 755 posts

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

Named by 5 registered channels — 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.

Android App Updates[Regular Update Info]
@androidappupdates · 2920 posts Oppo Update Hub
@oppoupdatehub · 2520 posts Realme Updates Hub
@realmeupdateshub · 3320 posts Samsung Updates Hub
@samsungphoneupdates · 3020 posts Huawei Updates
@huaweiupdatesnew · 141 post

Names

Channels on the register whose handles appear in this channel's posts.

Android App Updates[Regular Update Info]
@androidappupdates · 2915 posts GChromecast Hub
@gchromecast · 7515 posts Huawei Updates
@huaweiupdatesnew · 1415 posts Oppo Update Hub
@oppoupdatehub · 2515 posts Phone Wallpapers
@qhdwallpaperhub · 15315 posts Realme Updates Hub
@realmeupdateshub · 3315 posts Samsung Updates Hub
@samsungphoneupdates · 3015 posts Xiaomi Firmware Updates
@xiaomiredmiupdates · 1915 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.

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

“GoAndroid” (@officialgoandroid), 1,889 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/officialgoandroid.

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.