Telegram RegisterThe public register of Telegram

Channel

Pixel Gemini

@PixelGemini

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

67,340subscribers

+1,882 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003968315407
TypeChannel
Username@PixelGemini
Description欢迎来到 Pixel Gemini! 频道:t.me/PixelGemini 群组:t.me/PixelGeminiGroup 机器人:t.me/redeem_gemini_bot
CreatedBetween 1 April 2026 and 18 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/PixelGemini

Growth

65,45867,34066,3997 August 2026 — 65,458 subscribers7 August 2026 — 65,458 subscribers8 August 2026 — 65,668 subscribers9 August 2026 — 66,170 subscribers10 August 2026 — 66,618 subscribers11 August 2026 — 66,422 subscribers12 August 2026 — 66,658 subscribers14 August 2026 — 67,340 subscribers7 August 202614 August 2026
8 measurements spanning 6 days, net +1,882. 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 65,176–67,622 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 03:2667,340+682
12 Aug 2026, 19:2366,658+236
11 Aug 2026, 18:5266,422-196
10 Aug 2026, 17:4166,618+448
9 Aug 2026, 16:2466,170+502
8 Aug 2026, 14:2165,668+210
7 Aug 2026, 19:3065,458no change
7 Aug 2026, 19:2865,458first reading

Engagement

20 posts held, back to 18 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof 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 4 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
4
Links
5

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
3m 37s
Average length
54s

Measured directly from 4 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

443 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 56.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
25156.7%
👎5913.3%
🤣296.55%
🍌265.87%
🤡153.39%
😭143.16%
🖕122.71%
👍112.48%
🔥71.58%
🤔71.58%
😁40.903%
🤯40.903%
🆒30.677%
😈10.226%

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 18 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 443reactions 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 18 April 2026 to 4 June 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

4 Jun 2026, 01:41 UTC≈84,900 views120 reactionsread 14 August 2026

📢 THÔNG BÁO KHÔI PHỤC DỊCH VỤ 🇻🇳 Tiếng Việt Kính gửi Quý khách hàng, Hệ thống đã được khắc phục thành công và toàn bộ dịch vụ hiện đã hoạt động bình thường trở lại. Đội ngũ kỹ thuật đã hoàn tất việc xử lý sự cố liên quan đến hệ thống proxy và đang tiếp tục theo dõi để đảm bảo dịch vụ vận hành ổn định. Xin chân thành cảm ơn Quý khách đã kiên nhẫn chờ đợi và thông cảm trong thời gian bảo trì. ━━━━━━━━━━━━━━ 🇬🇧 E

80🤣20🍌18🤔1😈1

3 Jun 2026, 19:29 UTC≈63,300 views37 reactionsread 14 August 2026

📢 THÔNG BÁO BẢO TRÌ DỊCH VỤ 🇻🇳 Tiếng Việt Kính gửi Quý khách hàng, Hiện tại dịch vụ đang được bảo trì tạm thời do hệ thống proxy đang có tỉ lệ lỗi cao, ảnh hưởng đến chất lượng và độ ổn định của dịch vụ. Đội ngũ kỹ thuật đang khẩn trương xử lý để khôi phục hoạt động trong thời gian sớm nhất. Mong Quý khách thông cảm vì sự bất tiện này và vui lòng chờ thông báo cập nhật tiếp theo. Xin cảm ơn! ━━━━━━━━━━━━━━ 🇬🇧

19🤡15🆒3

11 May 2026, 19:38 UTC≈51,900 views96 reactionsread 14 August 2026

Tiếng Việt Kính gửi Quý khách hàng, Chúng tôi thành thật xin lỗi vì sự cố máy chủ proxy đã khiến dịch vụ bị gián đoạn trong thời gian vừa qua. Đội ngũ kỹ thuật đã khẩn trương kiểm tra và hiện sự cố đã được khắc phục hoàn toàn, dịch vụ đã hoạt động ổn định trở lại. Chúng tôi rất tiếc về những bất tiện đã gây ra và chân thành cảm ơn sự thông cảm cũng như đồng hành của Quý khách. English Dear Valued Customer, We sincere

64😭14🍌8🤔6👍4

3 May 2026, 13:06 UTC≈47,800 views71 reactionsread 14 August 2026
Video

Instructions on using the "Verify sign-in" method

👎5612👍3

3 May 2026, 13:02 UTC≈41,800 views3 reactionsread 14 August 2026
Video

Instructions on using TwoFA and how to enable TwoFA.

2👍1

26 Apr 2026, 06:20 UTC≈32,800 views39 reactionsread 14 August 2026
Video

Troubleshooting the issue of not being able to click the "Start Trial" button on your phone. 1. You need to replace 'partner-eft-onboard' in the receiving URL with 'offer'. Example: https://one.google.com/partner-eft-onboard/9NH57Y98MEE76RN8GQQT?hl=en -> https://one.google.com/offer/9NH57Y98MEE76RN8GQQT?hl=en 2. Open Chrome, log in to your Google account, go to https://calm-firefly-a296.huynhhieultkck.workers.dev/

24🖕12😁3

25 Apr 2026, 03:55 UTC≈22,300 views6 reactionsread 14 August 2026

The redemption link in the format https://one.google.com/partner-eft-onboard/F4VRN77CFSEZV6YHV0FU is now working normally again. If you have the link 'https://one.google.com/offer/F4VRN77CFSEZV6YHV0FU', please change it to 'https://one.google.com/partner-eft-onboard/F4VRN77CFSEZV6YHV0FU' to claim your reward. Simply replace 'offer' with 'partner-eft-onboard'.

6

25 Apr 2026, 03:45 UTC≈20,600 views4 reactionsread 14 August 2026

We have updated the module and fixed the "Offer unavailable" error.

🤯4

24 Apr 2026, 11:11 UTC≈20,200 views7 reactionsread 14 August 2026
File

File, posted without a caption

🔥61

24 Apr 2026, 09:14 UTC≈18,500 views13 reactionsread 14 August 2026
Video

Video, posted without a caption

🤣94

23 Apr 2026, 19:59 UTC≈15,600 views8 reactionsread 14 August 2026

We would like to inform you that our Hosting provider will perform scheduled system maintenance. Time: 21:30 – 23:00 (UTC), April 23, 2026 Impact: The bot and related services may be temporarily offline during this period. All services will automatically resume once the maintenance is completed. We apologize for any inconvenience and appreciate your understanding. Thank you for your support! 🙏

7😁1

22 Apr 2026, 05:31 UTC≈14,300 views6 reactionsread 14 August 2026

Xin lưu ý: Hiện tại bot chỉ hỗ trợ duy nhất một phương thức nạp Credit thông qua bot @redeem_gemini_bot. Ngoài phương thức này, không có bất kỳ cách nạp nào khác. Mọi giao dịch thực hiện bên ngoài bot đều không được đảm bảo an toàn. Please note: The bot currently supports only one method to top up Credit, which is via @redeem_gemini_bot. There are no other supported methods. Any transactions made outside the bot are

4👍1🔥1

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

Names

Channels on the register whose handles appear in this channel's 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Pixel Gemini” (@PixelGemini), 67,340 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/PixelGemini.

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.