Telegram RegisterThe public register of Telegram
Telegram profile photo for [BOT] Gemini Pixel Extractor

Bot

[BOT] Gemini Pixel Extractor

@GeminiPixel1_bot

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

20,549monthly users

-28,822 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID8853665898
TypeBot
Username@GeminiPixel1_bot
First recorded11 August 2026
Last confirmed live9 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/GeminiPixel1_bot

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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

20,54957,74639,147.57 August 2026 — 49,371 monthly users8 August 2026 — 52,987 monthly users11 August 2026 — 55,864 monthly users11 August 2026 — 55,864 monthly users13 August 2026 — 56,484 monthly users14 August 2026 — 57,439 monthly users17 August 2026 — 57,746 monthly users20 August 2026 — 57,607 monthly users23 August 2026 — 56,846 monthly users25 August 2026 — 51,771 monthly users27 August 2026 — 45,224 monthly users30 August 2026 — 36,023 monthly users2 September 2026 — 30,539 monthly users5 September 2026 — 26,776 monthly users9 September 2026 — 20,549 monthly users7 August 20269 September 2026
15 measurements spanning 33 days, net -28,822. 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 14,969–63,326 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
9 Sept 2026, 01:2020,549-6,227
5 Sept 2026, 16:3726,776-3,763
2 Sept 2026, 09:1630,539-5,484
30 Aug 2026, 13:1436,023-9,201
27 Aug 2026, 16:0845,224-6,547
25 Aug 2026, 17:2851,771-5,075
23 Aug 2026, 05:1256,846-761
20 Aug 2026, 16:4457,607-139
17 Aug 2026, 12:2357,746+307
14 Aug 2026, 16:4457,439+955
13 Aug 2026, 05:1856,484+620
11 Aug 2026, 20:1155,864no change
11 Aug 2026, 03:5755,864+2,877
8 Aug 2026, 07:0152,987+3,616
7 Aug 2026, 12:0149,371first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 20 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.

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

“[BOT] Gemini Pixel Extractor” (@GeminiPixel1_bot), 20,549 monthly users as measured 9 September 2026. Telegram Register, tgregister.com/channel/GeminiPixel1_bot.

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.