Channel
@perfectpanel
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,346subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001472024576 |
|---|---|
| Type | Channel |
| Username | @perfectpanel |
| 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 | 28 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/perfectpanel |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 03:20 | 2,346 | +32 |
| 18 Sept 2026, 12:16 | 2,314 | +13 |
| 14 Sept 2026, 09:57 | 2,301 | +4 |
| 10 Sept 2026, 14:17 | 2,297 | -1 |
| 5 Sept 2026, 08:21 | 2,298 | +13 |
| 1 Sept 2026, 14:15 | 2,285 | +2 |
| 29 Aug 2026, 17:54 | 2,283 | +5 |
| 26 Aug 2026, 13:52 | 2,278 | -22 |
| 20 Aug 2026, 09:34 | 2,300 | +5 |
| 17 Aug 2026, 13:54 | 2,295 | -24 |
| 13 Aug 2026, 22:28 | 2,319 | -5 |
| 11 Aug 2026, 03:46 | 2,324 | -22 |
| 8 Aug 2026, 13:34 | 2,346 | -7 |
| 7 Aug 2026, 20:17 | 2,353 | no change |
| 7 Aug 2026, 19:01 | 2,353 | first reading |
20 posts held, back to 29 April 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.
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 August 2026. An engagement rate over an empty window would be a number about nothing.
893 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 396 | 44.3% | |
| 🔥 | 230 | 25.8% | |
| 👍 | 144 | 16.1% | |
| 👏 | 46 | 5.15% | |
| 🎉 | 39 | 4.37% | |
| 👌 | 38 | 4.26% |
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 20 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 893 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 29 April 2026 to 4 August 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.
Edit user method in Admin API v2 ⚙️ We’ve added a new Edit user method to Admin API v2. It lets you edit panel user information through the API, similar to the Edit user action in the admin area. With this method, you can: • Add or update user contact and invoice details • Manage user access to payment methods • Manage user access to hidden services This makes it easier to build custom user management automations…
❤13👍9👌2
Updates and Platform filter in User App We've added an Updates page to the User App, allowing your users to stay informed about the latest service changes. The Updates module must be enabled to display this section. We've also added a platform filter to the New Order page. Users can quickly switch between platforms to find the services they need, while you can customize the list of platforms and the icon style. Yo…
❤9👍5🎉1
Custom llms.txt support You can now upload a custom llms.txt file for your panel's root directory. The llms.txt file provides AI systems with a structured description of your website’s content. Uploading this file can help AI crawlers navigate and understand your panel more accurately. The llms.txt file is not generated or updated automatically and must be maintained manually. We recommend uploading this file only…
❤15👍6🔥5🎉1👌1
Refill availability now syncs automatically with providers We've added automatic synchronization of Refill availability with providers. If Sync with provider is enabled, Refill availability is automatically updated whenever the provider enables or disables Refill for a service. This helps keep Refill availability aligned with the provider's Refill settings, reduces manual service maintenance, and helps ensure user…
❤20🔥16👌6
More order details in Admin API v2 Get order list method ⚙️ We’ve added a new optional "include" parameter to the Get order list method in Admin API v2. You can now request additional order details in bulk, without calling the Get order method for each order separately. With this update, you can include: • user_data — additional data entered by the user when creating the order • last_update — the date and time of …
🔥11❤3👍3👌2
Users can now cancel drip-feed orders Your users can now cancel active Drip-feed orders using the Cancel button on the Drip-feed page. This allows them to stop a Drip-feed as soon as it is no longer needed—for example, if the link is incorrect, the account has been blocked, the post has been removed, or the selected service is not working as expected. Users no longer need to contact panel support and wait for an a…
❤21👍3🔥3
Faster access to orders from Tickets We've improved how Order IDs are detected in ticket messages. The system now scans the entire ticket message and automatically adds links to valid Order IDs. Each detected Order ID is verified to belong to the user who created the ticket and opens in the correct admin section — Orders, Subscriptions, or Drip-feed. This helps support staff access the right order faster while mak…
❤27🔥11👍10👏2👌1
Negative margin filter for services We’ve added a new Negative margin filter to the Services section in the admin panel. This filter helps you quickly identify services that may be priced below their provider cost and are being sold at a loss. Find it in the Services section of your admin panel, under the Rate filter.
❤27👍5🔥5👏3
WeChat, Line, and KakaoTalk integrations New messenger buttons are now available: WeChat, Line, and KakaoTalk. You can add them to your panel so users have more ways to contact your support directly from the panel. WeChat and Line buttons open a small window with a QR code and a chat link. This makes it easier for users to open the chat from desktop or mobile. KakaoTalk opens the configured chat link in a new wind…
❤18👍9👏6🎉1
Automatic language selection for panel visitors 🌐 We've added automatic language detection for multilingual panels. New visitors will now automatically see the panel in their browser language, if that language is enabled on the panel. This works automatically for all multilingual panels and helps users start using the panel in the right language without changing it manually.
❤36🔥13👌8🎉4👍4
Mass action for Deny link duplicates We've added a new mass action that lets you enable or disable the Deny link duplicates setting for multiple services at once. Instead of updating each service individually, you can apply the setting to all selected services in a single action. This helps reduce manual work when managing many services. The Deny link duplicates action is available in the Mass actions menu on the …
❤28🔥12👍9👌5
Cancel availability now syncs automatically with providers ✅ This update solves a long-standing problem that becomes more noticeable as provider and reseller networks grow. Previously, Cancel availability depended on service settings being enabled and maintained manually at every level of the chain. If one provider or reseller did not update the setting, Cancel could become unavailable further down the chain — even…
🔥36❤19👍8🎉4👌3👏2
Showing the 12 most recent of 20 posts we hold for @perfectpanel. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“Perfect Panel” (@perfectpanel), 2,346 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/perfectpanel.
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.