Channel
@limaxflood
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
203subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003758475214 |
|---|---|
| Type | Channel |
| Username | @limaxflood |
| Created | Between 1 February 2026 and 3 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/limaxflood |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 11:02 | 203 | no change |
| 9 Aug 2026, 07:16 | 203 | first reading |
20 posts held, back to 3 June 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 pageof Telegram’s post history, 20 posts per page.
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. It is computed over the 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 July 2026 |
|---|---|
| Posts held | 20 (3 June 2026 – 30 July 2026) |
| Views total | 515 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 07:16 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.
65 reactions across 7 posts, in 13 distinct kinds. The most used accounts for 18.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6023703856116930992 | 12 | 18.5% | |
| custom 5202136686099725588 | 10 | 15.4% | |
| custom 5296727954905131242 | 10 | 15.4% | |
| ❤ | 7 | 10.8% | |
| custom 5249263751626003095 | 6 | 9.23% | |
| custom 5339437393164398712 | 6 | 9.23% | |
| custom 5433826111312138892 | 4 | 6.15% | |
| custom 5422631674192101311 | 3 | 4.62% | |
| custom 5424892626581091101 | 2 | 3.08% | |
| custom 5983268740479851218 | 2 | 3.08% | |
| custom 5267289506029004946 | 1 | 1.54% | |
| custom 5424658391949671561 | 1 | 1.54% | |
| custom 5424777207924946177 | 1 | 1.54% |
Custom emoji. 12 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 7 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 65reactions 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 3 June 2026 to 30 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.
Океей,тогда чья это собственность? Скрины с подтверждением,что бот предлагал вам такое название не предоставлено,тогда почему я должна поверить ВАМ,что вы не крали название флуда,а я вам да? Также про оформу никто ниче не пиздел кстати. Оформа ваша, и никто не говорит,что вы скопировали нашу. Не распространяйте диз инфы и не пудрите мозги людям
❤7
Я не понимаю, с чего вы решили, что у вас что-то “крадут”. Название и оформление — это не ваша собственность. Мы вообще брали это у бота, а не у вас. У нас свой флуд и своя подача, так что прежде чем обвинять — разберитесь
Сука тока шо подруга сказала что есть какой то второе инфо лимакс флуда,не ведитесь на эту залупу,если найдите пишите мне
Я че то не поняла,хули уже два флуда крадут наше название и оформу флуда
Пока) Патент за нами
Channel name was changed to «🔒. 𝐿𝟙𝟚 . ⊹ . ݁ ℓι𝗆𝖺χ 𝖥𝙻𝙳 . ݁₊ HII»
🔒. 𝐿𝟙𝟚 . ⊹ . ݁ ℓι𝗆𝖺χ 𝖥𝙻𝙳 . ݁₊ HII pinned «Хай,у нас опять перенабор. Приму тех кого посчитаю нужным. Пишите в лс @kleeenz»
𑣲 ᥴᥱᴦ᧐дᥒя (27.06.26) дʙᥲ ᥰρᥱκρᥲᥴны᥊ ɸ᧘удᥲ ⲙᥱ & y᧐ᥙ ᤋᥲκ᧘ючᥙ᧘ᥙ дρужᥱᥴκᥙᥔ ᥴ᧐юᤋ ᥴ ᥰ᧐дᥰᥙᥴью 1:1 。ˊˎ- ⤿ Ø1 ᧐ᥕᥒ ༄.° ⤿ Ø2 ᧐ᥕᥒ ༄.° ➖➖➖➖➖➖➖➖➖➖➖ ❦ δᥲδy y᧐ᥙ’rᥱ jᥙsᴛ ⲙy ɗᥱsᴛiᥒy 。⚡︎ ⚡︎
Хай,у нас опять перенабор. Приму тех кого посчитаю нужным. Пишите в лс @kleeenz
🦷🎀🍥рошла чuсткa 🥹 ➿ ➿ ➿ ➿ ➿ ➿ ➿ ➿ Ban list : сана,хеин,минни,юци,чонгук,конхо,юха,субин,чевон,казуха,юджин,сонхун,дженни,джию,юна,тина,миен,сону,хаым,иан,сакура,мока,лисо,кай,момо,ироха,цуки,дахен,мартин,цзыйю,вонхи #сзрп комментарий : сюка.. нам надо активных нью.
custom 52021366860997255888custom 54226316741921013113custom 52967279549051312422custom 54248926265810911012custom 54246583919496715611custom 54247772079249461771
🦷🎀🍥рошла чuсткa 🥹 ➿ ➿ ➿ ➿ ➿ ➿ ➿ ➿ Ban list : ироха,черен,бомгю,наен,ынче,бахи,джису,розэ,дженни,конхо,стелла #сзрп
custom 52021366860997255881
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @limaxflood. 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 — 934,198 of 1,189,255entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“🔒. 𝐿𝟙𝟚 . ⊹ . ݁ ℓι𝗆𝖺χ 𝖥𝙻𝙳 . ݁₊ HII” (@limaxflood), 203 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/limaxflood.
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.