Telegram RegisterThe public register of Telegram
Telegram profile photo for HomieFroxy

Channel

HomieFroxy

@HomieFroxy_channel

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

21subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001988604206
TypeChannel
Username@HomieFroxy_channel
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live28 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/HomieFroxy_channel

Growth

1921207 August 2026 — 19 subscribers11 August 2026 — 19 subscribers28 August 2026 — 21 subscribers7 August 202628 August 2026
3 measurements spanning 21 days, net +2. 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 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 06:5221+2
11 Aug 2026, 17:1619no change
7 Aug 2026, 17:4919first reading

Engagement

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

Recent posts

19 Jun 2026, 06:51 UTC45 viewsread 11 August 2026

🚨 Maintenance Update: Services Restored & Compensation Info Great news! Most of our servers are now fully fixed and back online. We are wrapping up the final checks, but the vast majority of affected nodes are now stable and running normally. Regarding Compensation: As promised, we will be issuing a 1.5x compensation multiplier for the downtime. Note: This bonus is currently being processed and will be automatically

11 Jun 2026, 14:57 UTC57 viewsread 11 August 2026

🚨 Maintenance We are currently performing emergency maintenance on some nodes. Affected nodes may be temporarily unavailable during this period. We sincerely apologize for any inconvenience. Once the issue is resolved, compensation will be automatically credited to your account based on the affected duration. Please rest assured. Feel free to reach out if you have any questions. Thank you for your patience and sup

5 Jun 2026, 16:59 UTC43 viewsread 11 August 2026

🌟Update Please refresh your subscription to sync the new node. Updated Nodes: 🇺🇸Homiefroxy 🇯🇵Japan

4 Jun 2026, 01:22 UTC41 viewsread 11 August 2026

Done 🚨 Scheduled Maintenance: Impacted Node: 🇯🇵Japan-03v6 🇯🇵Japan-02 🇯🇵Japan-02v6 Maintenance Window: Date: June 4, 2026 Time: 09:00 - 12:00 (UTC+9)

4 Jun 2026, 01:16 UTC37 viewsread 11 August 2026

🌟Update Please refresh your subscription to sync the new node. Updated Nodes: 🇩🇪DE-Germany01 🇮🇳01For downloadx0.01 🇯🇵Japan-03-TEST

2 Jun 2026, 09:26 UTC45 viewsread 11 August 2026

✅ Update — servers are back! Most of our servers have recovered and things are stable again. 🎉 To get the latest working config, please reset/update your subscription in your client app (re-import or refresh the subscription URL). This pulls the newest server list so you're back online smoothly. As an apology for the downtime, we've added compensation to your account: ⏳ +5 days subscription extension 📦 +25GB extra d

31 May 2026, 05:25 UTC39 viewsread 11 August 2026

🚨 heads up — several of our servers got banned and are currently down. we're already on it and working to get replacements up ASAP. shouldn't be too long! sorry for the trouble, hang tight 🙏

29 May 2026, 14:51 UTC41 viewsread 11 August 2026

⚠️ Service Alert: Taiwan Server Issues We are currently experiencing connectivity issues affecting all Taiwan servers. Impacted Nodes: 🇹🇼 Taiwan-01 🇹🇼 Taiwan-02 Status: Investigating 🔍 We will post an update as soon as service is restored. Thank you for your patience!

28 May 2026, 13:48 UTC43 viewsread 11 August 2026

☀️ Summer Vacation Special: 10% OFF All Plans! 🌊 (Active starting June 1st) School is out, the sun is up, and it's time for our Summer Vacation Sale! We’re kicking off the season with a flat 10% discount across all packages and all billing cycles. * 📉 Discount: 10% OFF * 📦 Eligible Packages: All Packages * ⏳ Eligible Periods: Monthly, Quarterly, Half-Year, and Yearly Promo Code: Summer2026

9 May 2026, 15:56 UTC45 viewsread 11 August 2026

Restored Nodes: 🇸🇬 Singapore-02 🇸🇬 Singapore-02v6

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

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

“HomieFroxy” (@HomieFroxy_channel), 21 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/HomieFroxy_channel.

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.