Telegram RegisterThe public register of Telegram
Telegram profile photo for FlameProxies.com

Channel

FlameProxies.com

@flameproxies

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

1,386subscribers

+110 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002200547802
TypeChannel
Username@flameproxies
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/flameproxies

Growth

1,2761,3861,3318 August 2026 — 1,276 subscribers8 August 2026 — 1,280 subscribers11 August 2026 — 1,308 subscribers14 August 2026 — 1,349 subscribers18 August 2026 — 1,352 subscribers21 August 2026 — 1,354 subscribers25 August 2026 — 1,358 subscribers28 August 2026 — 1,368 subscribers31 August 2026 — 1,378 subscribers3 September 2026 — 1,381 subscribers8 September 2026 — 1,386 subscribers8 August 20268 September 2026
11 measurements spanning 32 days, net +110. 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,260–1,403 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 23:561,386+5
3 Sept 2026, 19:171,381+3
31 Aug 2026, 06:021,378+10
28 Aug 2026, 07:441,368+10
25 Aug 2026, 00:341,358+4
21 Aug 2026, 04:571,354+2
18 Aug 2026, 00:511,352+3
14 Aug 2026, 22:461,349+41
11 Aug 2026, 13:061,308+28
8 Aug 2026, 20:521,280+4
8 Aug 2026, 05:311,276first reading

Engagement

16 posts held, back to 1 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 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 16 posts for this entry, the most recent from 25 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

34 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 35.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1235.3%
🔥1132.4%
926.5%
🎉25.88%

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 9 of the 16 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 34 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 1 April 2026 to 25 July 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

25 Jul 2026, 00:13 UTC600 views11 reactionsread 8 August 2026
Photo

📣 Recent Update Notice 🚨 We recently rolled out an update to our website which temporarily affected certain features, including traffic usage display and a few other functions. ✔ Everything is now fully back to normal. ❤️‍🔥 We appreciate your patience while this was being handled. 🎁 To make it up to you, we’re offering a limited-time discount on all plans: 🟢 Use code FIX30 for 30% off 🟢 Valid for the next 24 hour

👍6🎉2🔥21

11 Jun 2026, 13:05 UTC≈1,010 views6 reactionsread 8 August 2026
Photo

📣 New Release: Proxy Connector Extension 🚀 We’ve officially released the FlameProxies Proxy Connector Extension. 🟢This extension allows you to easily connect and manage your proxies directly in your browser with a smoother and more streamlined workflow. 🔗 Install here: https://chromewebstore.google.com/detail/proxy-extension/fnplddojckpmckjnnjlllajgghjbjokk ✔ Quick setup ✔ Easy proxy switching ✔ Built for perform

👍6

30 May 2026, 15:09 UTC958 views4 reactionsread 8 August 2026
Photo

📣 The recent update with VAT caused issues with creating checkouts and orders for several users. The problem has now been fully resolved. 🚀 To thank you for your patience, we’re offering a discount code valid on all plans (one use per user). ✔️ Use code DRAGON25 for 25% off your next purchase. 🙏 Thank you for your patience. 🔥 Need help or have questions? Contact our support team anytime at 👉 @FlameProxiesSupport

🔥31

29 May 2026, 21:18 UTC865 viewsread 8 August 2026
Photo

📣 Another week, another update. ✔️ VAT has now been added to payments. If you select “Save for future purchases,” you will only need to enter your details once. 🇪🇺 Please note that VAT applies only to EU customers. If you are located outside the EU, VAT will not be charged. This is checked via a one-time IP check, so if your IP is outside of EU, you will not be charged for VAT for any future purposes. 🚀 More upda

22 May 2026, 17:01 UTC811 viewsread 8 August 2026
Photo

📣 Another week, another update. ✔️ This week, we rolled out several performance improvements based on user feedback, including major speed optimizations across US regions and Latin America. As part of this, we also deployed new gateways throughout LATAM to deliver a more reliable and consistent experience. ⚡️ Starting today, users in Latin America will notice a major improvement in both speed and overall performan

14 May 2026, 22:37 UTC814 views5 reactionsread 8 August 2026
Photo

📣 We've just released our new Customer API, allowing you to manage and integrate your proxies programmatically with ease. 🔗 Get started here: https://flameproxies.com/dashboard/api-docs ⚡️ We've also boosted performance across all USA and nearby regions, delivering faster speeds and improved reliability. 🚀 More performance upgrades are on the way — stay tuned! 🔥 Need help or have questions? Contact our support t

🔥5

2 May 2026, 16:02 UTC905 views2 reactionsread 8 August 2026
Photo

📢 We've rolled out major performance upgrades across our network, delivering faster and more stable proxies starting now. ✔️ We've also deployed new gateway infrastructure in regions where proxies are typically restricted, improving accessibility and success rates globally. 🔥 Need help or have questions? Contact our support team anytime at 👉 @FlameProxiesSupport & discord.gg/flameproxy

2

8 Apr 2026, 10:11 UTC≈1,300 views2 reactionsread 8 August 2026
Photo

📢 If you're having issues with your proxy or it's not working for a specific use case, head over to your proxy generator and switch the "Pool" to Performance or Ultra. Try both to see which works best, then stick with that one! 🙂 🔥 Need help or have questions? Contact our support team anytime at 👉 @FlameProxiesSupport

2

5 Apr 2026, 02:18 UTC≈1,210 views1 reactionsread 8 August 2026
Photo

📢 Join our official community Discord to stay updated, grab exclusive discounts, and take part in giveaways 🎉 🔗 https://discord.gg/flameproxy 🔥 Need help or have questions? Reach out to our support team anytime 👉 @FlameProxiesSupport

1

3 Apr 2026, 11:19 UTC≈1,130 viewsread 8 August 2026
Photo

✔️ We are updating our proxies currently, if you have any issues or questions please contact our support team! 🔥 Need help or have questions? Contact our support team anytime at 👉 @FlameProxiesSupport

2 Apr 2026, 17:41 UTC≈1,050 viewsread 8 August 2026
Photo

✔️ The issue above has now been resolved. You can now continue to use the website as usual. ℹ️ Please note: If the proxy you are using does not suffice for your use-case, you can change the pool. At FlameProxies we have 3 pools which you can choose between: Standard, Performance and Ultra. Try out all pools and continue using the one which is best for your needs! 🔥 Need help or have questions? Contact our support t

2 Apr 2026, 12:10 UTC776 viewsread 8 August 2026
Photo

🚨 We have a minor issue on the website where the "purchase" button currently does not work, which happened after a smaller updated we pushed to the dashboard. This will be fixed in around 15 minutes. We advice you to not make purchases until then. 🔥 Need help or have questions? Contact our support team anytime at 👉 @FlameProxiesSupport

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

Forward network

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.

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

“FlameProxies.com” (@flameproxies), 1,386 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/flameproxies.

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.