Telegram RegisterThe public register of Telegram

Channel

𝗔𝗕𝗬𝗦𝗦 𝗙𝗟𝗢𝗢𝗗 𝗜𝗡𝗙𝗢

@abyss_floood

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

76subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003588765935
TypeChannel
Username@abyss_floood
CreatedBetween 1 December 2025 and 8 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/abyss_floood

Growth

7610 Aug 2026, 15:16 — 76 subscribers10 Aug 2026, 15:30 — 76 subscribers10 Aug 2026, 15:1610 Aug 2026, 15:30
2 measurements taken within a single day. 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 75–77 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 15:3076no change
10 Aug 2026, 15:1676first reading

Engagement

20 posts held, back to 8 March 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
317.1%
avg views ÷ 76 subscribers
Avg views / post
241
1 post measured
Reaction rate
0.83%
reactions ÷ views · ER floor
Posts in window
1
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 July 2026
Posts held20 (8 March 202620 July 2026)
Views total241
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 15:30 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
8
Links
6

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

73 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 24.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1824.7%
custom 53638378153375467351621.9%
custom 51997645413024117421013.7%
❤‍🔥811.0%
custom 520178762981262022779.59%
💘79.59%
🔥68.22%
custom 519062728184799328511.37%

Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 73reactions 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 8 March 2026 to 20 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

20 Jul 2026, 12:31 UTC241 views2 reactionsread 10 August 2026

Обновилась информация! Наш ТТ акк теперь @abyssflood_tiktok

1❤‍🔥1

10 Jun 2026, 15:15 UTC358 views3 reactionsread 10 August 2026

────𝐹𝐿𝑂𝑂𝐷 𝐴𝐷𝑀𝐼𝑁𝐼𝑆𝑇𝑅𝐴𝑇𝐼𝑂𝑁 ──── Владелец: ФАННИ (+4 часа мск) Обязанности: Слежка за чатом/гч Контролировать список ролей Искать нью Следить на администрацией Вести активности Вести соть сети флуда Проводить чистки Решать конфликты Слежка за рестами Вливать нью Совлд: ЭСТЕС (+7 часов мск) Обязанности: Следить за чатом Следить за администрацией Проводить активности Решать конфликты Заменять влд в экстренных случая

1❤‍🔥1🔥1

10 Jun 2026, 15:15 UTC396 views3 reactionsread 10 August 2026

Админы по активу: Обязанности: Общение с участниками Определение неактив Создание интерактивов Поддержание актива в чате Монтажеры: ЛСС Обязанности: Создавать короткие видео для соц сетей флуда Кастомщики: ЧЖУСИНЬ (+2 мск) Обязанности: Проводить кастомы внутри флуда/с союзами/другими флудами Админы по нью: ХАНАБИ Обязанности: Искать нью вливать их Админы по заключению союза: Обязанности: Искать и заключ

3

6 Jun 2026, 13:53 UTC327 views3 reactionsread 10 August 2026

!ВАЖНО! Дорогие, наши союзники мы изменили ссылку на инфо-флуд с @lskslaosoo на @abyss_floood. Просим обновить реквизиты

1❤‍🔥1💘1

30 May 2026, 10:03 UTC397 views7 reactionsread 10 August 2026
Photo

𐔌 ⁺ ﹒ 𝗡𝗘𝗪 𝗨𝗡𝗜𝗢𝗡。˚ ✧ Новый союз! Сегодня мы закрепили союз с DRUGS. Очень надеемся на долгое и крепкое сотрудничество 𝐼𝑛𝑓𝑜: жми

🔥32❤‍🔥2

23 May 2026, 11:02 UTC404 views2 reactionsread 10 August 2026

ⳄⲀⳂⳘⲦⲀ🌟 Ⳝⲉⲥⲥⲙⲉⲣⲧυⲉ— Ⲅⲟⲥⲡⲟⲇⲥⲧⲃⲟ ⲗьⲇⲁ— Ⲇⲣⲉⲃⲏяя ⲕυⲣⲁⲥⲁ— Ⳅⲁⳃυⲧⲏыύ ⲱⲗⲉⲙ— Ⲕυⲣⲁⲥⲁ ⲅⲣⲩⳝⲟύ ⲥυⲗы— Ⲕⲣыⲗья ⲕⲟⲣⲟⲗⲉⲃы— Ⲏⲁⲡⲗⲉⳡⲏυⲕ ⲏⲁⲕⲁⳅⲁⲏυя— Ⲟⲣⲁⲕⲩⲗ— Ⲡⲣⲟⲕⲗяⲧыύ ⲱⲗⲉⲙ— Ⲥυяюⳃⲁя ⳝⲣⲟⲏя— Ⲱυⲡⲟⲃⲁⲏⲏⲁя ⳝⲣⲟⲏя— Ⲱⲧⲟⲣⲙⲟⲃⲟύ ⲡⲟяⲥ— Ⳃυⲧ Ⲁⲫυⲏы—

💘2

23 May 2026, 11:02 UTC359 views2 reactionsread 10 August 2026

ⲤⲎⲀⲢЯⲮⲈⲎⳘЯ📌 ⲘⲀⲄⳘЯ🌟 Ⳝⲟⲯⲉⲥⲧⲃⲉⲏⲏыύ ⲙⲉⳡ—@SXRsado Ⲯⲉⳅⲗ ⲙⲟⲗⲏυύ— Ⲯⲉⳅⲗ ⲥⲏⲉⲯⲏⲟύ ⲕⲟⲣⲟⲗⲉⲃы— Ⳅⲁⳡⲁⲣⲟⲃⲁⲏⲏыύ ⲧⲁⲗυⲥⲙⲁⲏ— Ⲕⲟⲏцⲉⲏⲧⲣυⲣⲟⲃⲁⲏⲏⲁя эⲏⲉⲣⲅυя— Ⲕⲣⲟⲃⲁⲃыⲉ ⲕⲣыⲗья— Ⲡⲁⲗⲟⳡⲕⲁ ⲅⲉⲏυя— Ⲡыⲗⲁюⳃυύ ⲯⲉⳅⲗ—@freastles Ⲣⲁύⲥⲕⲟⲉ ⲡⲉⲣⲟ— Ⲥⲃяⳃⲉⲏⲏыύ ⲕⲣυⲥⲧⲁⲗⲗ— Ⲥⲧⲁⲣⲗυⲩⲙⲟⲃⲁя ⲕⲟⲥⲁ— Ⲫⲗяⲅⲁ Ⲟⲁⳅυⲥⲁ— Ⲫⲟⲏⲁⲣь ⲯⲉⲗⲁⲏυύ— Ⳡⲁⲥы ⲥⲩⲇьⳝы—

🔥2

23 May 2026, 11:02 UTC391 views2 reactionsread 10 August 2026

ⲠⲈⲢⲈⲆⲂⳘⲮⲈⲎⳘⲈ🌟 Ⳝⲟⲧυⲏⲕυ ⲇⲉⲙⲟⲏⲁ— Ⲙⲁⲅυⳡⲉⲥⲕυⲉ ⳝⲟⲧυⲏⲕυ— Ⲡⲣⲟⳡⲏыⲉ Ⲥⲁⲡⲟⲅυ— Ⲥⲁⲡⲟⲅυ ⲃⲟυⲏⲁ— Ⲥⲁⲡⲟⲅυ Ⳅⲁⲕⲗυⲏⲁⲧⲉⲗя— Ⲥⲁⲡⲟⲅυ ⲥⲡⲉⲱⲕυ— Ⲥⲁⲡⲟⲅυ-ⲥⲕⲟⲣⲟⲭⲟⲇы— ⲀⲦⲀⲔⲀ🌟 Ⳝⲉⲥⲕⲟⲏⲉⳡⲏⲁя ⳝυⲧⲃⲁ— Ⲃⲉⲧⲉⲣ ⲡⲣυⲣⲟⲇы— Ⲅⲟⲃⲟⲣяⳃυύ ⲥ ⲃⲉⲧⲣⲟⲙ— Ⲅⲩⳝυⲧⲉⲗьⲏыύ ⲡⲩⲗⲉⲙⲉⲧ— Ⳅυⲙⲏяя ⲕⲟⲣⲟⲏⲁ— Ⳅⲗⲟⳝⲏыύ ⲣыⲕ— Ⳅⲟⲗⲟⲧⲟύ ⲙⲉⲧⲉⲟⲣ— Ⳅⲟⲗⲟⲧⲟύ ⲡⲟⲥⲟⲭ— Ⲕⲗυⲏⲟⲕ ⲟⲧⳡⲁяⲏυя— Ⲕⲗυⲏⲟⲕ ⲥⲉⲙυ ⲙⲟⲣⲉύ— Ⲕⲟⲅⲧυ Ⲭⲁⲁⲥⲁ— Ⲕⲟⲡьⲉ Ⲃⲉⲗυⲕⲟⲅⲟ ⲇⲣⲁⲕⲟⲏⲁ— Ⲕⲟⲥⲁ ⲕⲟⲣⲣⲟⳅυυ— Ⲙⲉⳡ ⲟⲭⲟⲧⲏυⲕⲁ ⲏⲁ ⲇⲉⲙⲟⲏⲟⲃ— Ⲙυⲙⲟⲗⲉⲧⲏⲟⲉ ⲃⲣⲉⲙя— Ⲡⲣⲟⲏⳅⲁюⳃυύ ⲏⲉⳝ

❤‍🔥2

23 May 2026, 11:02 UTC361 views2 reactionsread 10 August 2026

ⲆⲢⲨⲄⳘⲈ🌟 Ⲃⲁⳅⲟⲏ— Ⲕⲣⲁⳝ-ⲡⲁⲇⲁⲗьⳃυⲕ— Ⲕⲣⲁⲥⲏыύ ⳝⲁⲫⲫ— Ⲕⲣυⲡ— Ⲕⲩⲥⲧ— Ⲗⲁⲃⲟⲃыύ ⲅⲟⲗⲉⲙ— Ⲗⲟⲣⲇ—@CANNIBALLLEBAL Ⲣⲟⲅⲁⲧⲁя яⳃⲉⲣυцⲁ— Ⲥυⲏυύ ⳝⲁⲫⲫ— Ⲧⲣⲟⲏ— Ⳡⲉⲣⲉⲡⲁⲭⲁ—@Gaywin_0 ЭⲪⲪⲈⲔⲦЫ🌟 Ⳝⲗⲁⲅⲟⲥⲕⲗⲟⲏⲏⲟⲥⲧь— Ⲃⲇⲟⲭⲏⲟⲃⲉⲏυⲉ— @vortexxx_dr Ⲃⲥⲡыⲱⲕⲁ— Ⲕⲣⲟⲃⲁⲃⲟⲉ Ⲃⲟⳅⲙⲉⳅⲇυⲉ— Ⲗⲉⲇяⲏⲟⲉ Ⲃⲟⳅⲙⲉⳅⲇυⲉ— Ⲙⲁⲥⲕυⲣⲟⲃⲕⲁ— Ⲟⲅⲏⲉⲏⲏыύ ⲱⲁⲣ— Ⲟⲥⲧⲣыύ ⲩⲇⲁⲣ— Ⲟцⲉⲡⲉⲏⲉⲏυⲉ— Ⲟⳡυⳃⲉⲏυⲉ— Ⲡⲗⲁⲙⲉⲏⲏⲟⲉ ⲃⲟⳅⲙⲉⳅⲇυⲉ— Ⲡⲟⲟⳃⲣⲉⲏυⲉ— Ⲥⲡⲣυⲏⲧ— Ⲧⲉⲗⲉⲡⲟⲣⲧ— Ⳃυⲧ—

💘2

23 May 2026, 11:02 UTC366 views3 reactionsread 10 August 2026

ⲤⲦⲢⲈⲖⲔⳘ🌟 ⳝⲉⲁⲧⲣυⲥ— ⳝⲣⲟⲩⲇυ— ⳝⲣⲩⲏⲟ— ⲃⲁⲏⲃⲁⲏ—@miya1704 ⲅⲣⲉύⲏⲇⲿⲉⲣ— υⲕⲥυя— υⲣυⲧⲉⲗь— ⲕⲗⲁⲩⲇ—@Surrt ⲕυⲙⲙυ— ⲕⲗυⲏⲧ—@dan0_6chik ⲕэⲣⲣυ— ⲗⲉύⲗⲁ—@flayarebzyyxx ⲗⲉⲥⲗυ — ⲙⲉⲗυⲥⲥⲁ— ⲙυя—@HAWAYU_CHIPSO ⲙⲟⲥⲕⲟⲃ— ⲏⲁⲧⲁⲏ— ⲟⳝⲥυⲇυя—@Kateridze_X ⲣⲟⲇⲿⲉⲣ— ⲡⲟⲡⲟⲗь υ ⲕⲩⲡⲁ— ⲭⲁⲏⲁⳝυ—@itsglnsyy

3

23 May 2026, 10:47 UTC412 views2 reactionsread 10 August 2026

ⲨⳜⳘЙЦЫ🌟 ⲁⲗⲩⲕⲁⲣⲇ— ⲁⲣⲗⲟⲧⲧ—@Ocarin191 ⳝⲉⲏⲉⲇⲉⲧⲧⲁ— ⲅⲟⲥⲥⲉⲏ—@YrymuMl ⲇⲿⲟύ—@Benedetta333 ⲇⲿⲩⲗυⲁⲏ— υⲏь— ⲕⲁⲣυⲏⲁ— ⲭυⲣⲁⲣⲁ— ⲗⲁⲏⲥⲉⲗⲟⲧ— ⲗυⲏⲅ— ⲗⲥⲥ—@Manadalor ⲏⲁⲧⲁⲗья— ⲏⲟⲗⲁⲏ— ⲥⲁⳝⲉⲣ—@puumpk1n ⲥⲩ ⲉ—@Well_Le4ar ⲫⲁⲏⲏυ—@ASYA_B_POCCUU ⲭⲁⲏⳅⲟ—@COHb1Y ⲭⲁⲣⲗυ— ⲭⲁяⳝⲩⲥⲁ—@Amd_pentium ⲭⲉⲗⲕⲁⲣⲧ— эύⲙⲟⲏ—@space_wiw

2

23 May 2026, 10:47 UTC397 views2 reactionsread 10 August 2026

ⳜⲞЙЦЫ🌟 ⲁⲗⲇⲟⲥ— ⲁⲣⲅⲩⲥ—@D3kzter ⲁⲗьⲫⲁ— ⲁⲩⲗⲩⲥ — ⳝⲁⲇⲁⲏⲅ— ⳝⲉύⲏ—@Molikleee ⲅⲃυⲏⲉⲃⲣⲁ —@i1mharu ⲇⲁⲣυⲩⲥ— ⳅυⲗⲟⲏⲅ— υⲕⲥ. ⳝⲟⲣⲅ— ⲕⲩⲥⲁⲕⲁ— ⲗⲁⲡⲩ-ⲗⲁⲡⲩ— ⲗⲉⲟⲙⲟⲣⲇ—@DrTenmma ⲗⲩⲕⲁⲥ— ⲙⲁⲣⲧυⲥ— ⲙⲁⲱⲁ— ⲧⲁⲙⲩⳅ— ⲧэⲣυⳅⲗⲁ— ⳡⲩ— ⲙυⲏⲥυⲧⲧⲁⲣ— ⲣⲩⳝυ—@Shadow_1aloha ⲥⲁⲏ— ⲥυⲗьⲃⲁⲏⲏⲁ— ⲫⲟⲃυⲩⲥ— ⲫⲣⲉⲇⲣυⲏ— ⲫⲣⲉύя— ⲭⲁⲗυⲇ— ⳡυⳡυ—@Kush_chek ⳡⲟⲏⲅ—@BlooDverizon ⲥⲟⲣⲁ—@Musye777 эⲥⲙⲉⲣⲁⲗьⲇⲁ—

2

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

Citation-graph rank

Citation-graph rank — 942,074 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 registered channels — 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.

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.

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

“𝗔𝗕𝗬𝗦𝗦 𝗙𝗟𝗢𝗢𝗗 𝗜𝗡𝗙𝗢” (@abyss_floood), 76 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/abyss_floood.

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.