AUSTRALIA 🇦🇺 IG SECURED HOTMAIL ASK AZA FOR 14k Dm @comrade_horpydex
Signed HORPYDEX

Channel
@Flyboyisback03
On this record: Topic · Growth · Engagement · Posts · Cite this entry
387subscribers
+20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003349719733 |
|---|---|
| Type | Channel |
| Username | @Flyboyisback03 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 29 October 2026 |
| On Telegram | t.me/Flyboyisback03 |
Hacking & security — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Oct 2026, 13:59 | 387 | +4 |
| 23 Oct 2026, 00:09 | 383 | +4 |
| 16 Oct 2026, 18:08 | 379 | +2 |
| 28 Sept 2026, 15:19 | 377 | +8 |
| 14 Sept 2026, 03:39 | 369 | +1 |
| 7 Sept 2026, 06:02 | 368 | -4 |
| 28 Aug 2026, 18:06 | 372 | +2 |
| 22 Aug 2026, 14:04 | 370 | -1 |
| 14 Aug 2026, 06:16 | 371 | +3 |
| 8 Aug 2026, 06:30 | 368 | no change |
| 7 Aug 2026, 21:07 | 368 | +1 |
| 7 Aug 2026, 18:31 | 367 | first reading |
10 posts held, back to 7 August 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 10 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
AUSTRALIA 🇦🇺 IG SECURED HOTMAIL ASK AZA FOR 14k Dm @comrade_horpydex
Signed HORPYDEX
Italy 🇮🇹 IG FULLY SECURED WITH 2FA Dm @su130403 10k
Signed Suplex CSR 🏆
Bolivia 🇧🇴 IG NO 2FA LOGIN AND USE Dm @su130403 7k
Signed Suplex CSR 🏆
Germany 🇩🇪 No 2fa Login & use 11k Dm @itz_medal
Signed 🥶
Hungary 🇭🇺 with mail access 16k @jefter_x
Signed HORPYDEX
Germany 🇩🇪 No 2fa Login & use 11k Dm @itz_medal
Signed 🥶
USA 🇺🇸 IG NO 2FA LOGIN AND USE Dm @su130403 8k
Signed Suplex CSR 🏆
South Korea 🇰🇷 IG NO 2FA LOGIN AND USE Dm @su130403 3k
Signed Suplex CSR 🏆
Germany 🇩🇪 No 2fa Login & use 10k Dm @itz_medal
Signed 🥶
Turkey 🇹🇷 IG FULLY SECURED WITH 2FA Dm @su130403 9k
Signed Suplex CSR 🏆
Showing the 10 most recent of 10 posts we hold for @Flyboyisback03. 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.
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 29 October 2026 — this entry's latest reading, not the date you are reading this.
“Fly boy is back🔝⚜️” (@Flyboyisback03), 387 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/Flyboyisback03.
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.