Telegram RegisterThe public register of Telegram

Channel

maybe flood 🔒

@maybeflood

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

75subscribers

+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-1002923618327
TypeChannel
Username@maybeflood
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/maybeflood

Growth

7510 Aug 2026, 19:46 — 75 subscribers11 Aug 2026, 06:01 — 75 subscribers10 Aug 2026, 19:4611 Aug 2026, 06:01
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 74–76 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 06:0175no change
10 Aug 2026, 19:4675first reading

Engagement

20 posts held, back to 21 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.

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 31 March 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

16 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 56.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5258447727439679915956.3%
custom 5395729150101179496318.8%
custom 5260504183550795705212.5%
custom 525838838387654416616.25%
custom 539987145278464869716.25%

Custom emoji. Every row above is a 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 6 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 16reactions 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 21 March 2026 to 31 March 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

31 Mar 2026, 10:20 UTC147 views2 reactionsread 10 August 2026

Во флуд никого не возьму, доллва не пишите мне больше пожалуйста 👌

custom 52584477274396799152

Signed 「✶」– Mayb3lL1n3.、🦮

31 Mar 2026, 10:18 UTC146 views3 reactionsread 10 August 2026

Интереснее ссор в вармах

custom 53957291501011794962custom 52584477274396799151

Signed 「✶」– Mayb3lL1n3.、🦮

31 Mar 2026, 10:18 UTC147 views2 reactionsread 10 August 2026

Мне так нравится читать комментарии под " дарьяша иди нахуй" ✋✋

custom 52584477274396799152

Signed 「✶」– Mayb3lL1n3.、🦮

30 Mar 2026, 19:31 UTC200 views2 reactionsread 10 August 2026

А дарьяша иди нахуй

custom 52605041835507957052

Signed 「✶」– Mayb3lL1n3.、🦮

30 Mar 2026, 19:17 UTC150 viewsread 10 August 2026

Дааа. Как камень с плеч после этого сообщения 🥳🥳

Signed 「✶」– Mayb3lL1n3.、🦮

30 Mar 2026, 19:15 UTC134 viewsread 10 August 2026

На самом деле я его закрываю потому что я хочу сделать свой роблокс сериал, а у меня уже нету на чем делать акки в тт, извинитесь

Signed 「✶」– Mayb3lL1n3.、🦮

30 Mar 2026, 19:14 UTC136 viewsread 10 August 2026

У вас есть час отговорить меня не закрывать флуд окончательно

Signed 「✶」– Mayb3lL1n3.、🦮

30 Mar 2026, 19:14 UTC208 views3 reactionsread 10 August 2026
Photo

–. The end ?? – да. У меня пропала мотивация вести этот флуд. Я очень его любила, но это был проект с джисоном который делал для флуда почти все. Йеджи - замена, она тоже многое делала ( спасибо ), но все же ч предпочитаю быть с джи. Я очень любила этот флуд, я помню каждый наш рейд. Помню когда нас слили в мяу. Помню все. Все хороше и плохое. После темной полосы всегда идет светлая которая у нас уже прошла. Темной

custom 52584477274396799153

Signed 「✶」– Mayb3lL1n3.、🦮

26 Mar 2026, 08:29 UTC108 viewsread 10 August 2026

Пошла в жопу

Signed 「✶」– Mayb3lL1n3.、🦮

25 Mar 2026, 19:07 UTC106 views4 reactionsread 10 August 2026

Я ну тоже не хочу писать потому что яюмы кому то пишем, а кому то нет

custom 52583883838765441661custom 52584477274396799151custom 53957291501011794961custom 53998714527846486971

Signed 「✶」– Mayb3lL1n3.、🦮

Showing the 12 most recent of 20 posts we hold for @maybeflood. 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 — 1,068,662 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“maybe flood 🔒” (@maybeflood), 75 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/maybeflood.

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.