Channel
NEW FLOOD SERVICE | Флуд почт | NEW BOT @Flood_email_bot👉
@flood_service
On this record: Topic · Growth · Engagement · Cite this entry
3,714subscribers
+101 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001176535620 |
|---|---|
| Type | Channel |
| Username | @flood_service |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/flood_service |
Topic
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 09:37 | 3,714 | -13 |
| 30 Sept 2026, 05:37 | 3,727 | -8 |
| 19 Sept 2026, 12:39 | 3,735 | +8 |
| 14 Sept 2026, 15:00 | 3,727 | -1 |
| 11 Sept 2026, 07:58 | 3,728 | +3 |
| 6 Sept 2026, 23:24 | 3,725 | no change |
| 6 Sept 2026, 04:22 | 3,725 | +2 |
| 2 Sept 2026, 06:58 | 3,723 | -5 |
| 29 Aug 2026, 22:04 | 3,728 | -3 |
| 27 Aug 2026, 08:33 | 3,731 | +9 |
| 24 Aug 2026, 01:47 | 3,722 | +17 |
| 20 Aug 2026, 15:28 | 3,705 | +39 |
| 17 Aug 2026, 11:57 | 3,666 | +12 |
| 14 Aug 2026, 02:08 | 3,654 | +24 |
| 10 Aug 2026, 09:37 | 3,630 | +15 |
| 6 Aug 2026, 23:56 | 3,615 | +2 |
| 6 Aug 2026, 17:40 | 3,613 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“NEW FLOOD SERVICE | Флуд почт | NEW BOT @Flood_email_bot👉” (@flood_service), 3,714 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/flood_service.
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.