Telegram RegisterThe public register of Telegram
Telegram profile photo for Aureli Flood Info

Channel

Aureli Flood Info

@aureliiflood

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

27subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003953666689
TypeChannel
Username@aureliiflood
CreatedBetween 1 April 2026 and 10 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/aureliiflood

Growth

2713 Aug 2026, 07:31 — 27 subscribers13 Aug 2026, 11:47 — 27 subscribers13 Aug 2026, 07:3113 Aug 2026, 11:47
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 26–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:4727no change
13 Aug 2026, 07:3127first reading

Engagement

20 posts held, back to 10 June 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 12 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
33s
Average length
11s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

13 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 46.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5255955997867925485646.2%
custom 5255734437684991920430.8%
custom 5271763152554473200215.4%
custom 526923949849081349817.69%

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 8 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 13reactions 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 10 June 2026 to 12 June 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

12 Jun 2026, 11:34 UTC113 views2 reactionsread 13 August 2026

Бля я так испугалась не пугайте так

custom 52559559978679254852

12 Jun 2026, 11:34 UTC107 viewsread 13 August 2026
Photo

🪻THE END??… Нет конечно)) просто нам нужны очень много союзов и активных нью мы всем будем рады!! И так же припоминаю нью эра будет 20 числа🤫🫰🏻 Всех любим) надеюсь мы не упадем вниз! Всех любим💜💋 #сзрп

12 Jun 2026, 07:47 UTC104 viewsread 13 August 2026
Video

硬 𓂃୧ 〢꒰ New Era ੭ ੭ ⻝ . ໒ 🏸꒱ 𝟤:𝟢𝟴 ₊𑁭ᰍ 🍃🌼ooming soon @ 20.06.2026 . . こ物 Id oform - Not ours

11 Jun 2026, 19:24 UTC167 views1 reactionsread 13 August 2026

#Вонён Всем здравствуйте. Я узнала причину почему Дженни удалила флуд. Я беру пока что флуд на себя потом когда Дженни сможет одам ей обратно. Напишите мне в лс я через пару минут отвечу и отправлю ссылку. {Если вы не зайдете в течения трех дней то убираю вашу роль с инфо!} #сзрп

custom 52559559978679254851

11 Jun 2026, 18:14 UTC125 views1 reactionsread 13 August 2026
Photo

#Вонён Прошло почти пять часов но она так и не ответила. Это очень грустно понимать то что с вероятностью 99% нашего флуда больше не будет. Один из союзов писал чтобы я взяла на себя флуд но я даже не знаю если справлюсь. Ну и я не очень хочу забирать этот флуд на себя все таки Дженни много чего делала для флуда. Надеюсь до завтра мы все узнаем. Если нет будем ждать дальше. Всем заранее споки нули #сзрп

custom 52717631525544732001

11 Jun 2026, 13:20 UTC195 views2 reactionsread 13 August 2026
Photo

#Вонён Всем здравствуйте я бы никогда не хотела это писать но Дженни удалила флуд. Она никому не отвечает поэтому причину мы не знаем. Лучше ей не писать сейчас. Может она выйдет на связь и объяснит. Я думаю что союзы надо расторгнуть хотя я бы не хотела этого делать. Надеюсь вечером она все объяснит и мы будем знать что делать дальше. #сзрп

custom 52557344376849919202

10 Jun 2026, 21:00 UTC172 views4 reactionsread 13 August 2026
Video

#Вонён Дорогая наша влд Дженни с днём рождения тебя! Мы тебя очень очень сильно любим и ценим. Надеюсь этот флуд закроется не скоро и все у нас будет хорошо! Желаю тебе счастья, здоровья, любви и много крутых нью! Ты очень крутой влд. Даже в ресте ты усердно работаешь для нашего флуда. А вот и поздравления от наших админов(не всех) Ироха дженни,с днем рождения!я желаю тебе всего наилучшего,ты лучший владелец:3 Вонх

custom 52557344376849919202custom 52559559978679254851custom 52717631525544732001

10 Jun 2026, 18:50 UTC53 viewsread 13 August 2026
Forwarded from @oopsflo0dVideo

🌸 Neω ѕωeeт Uηιση 🤩Me & Yσυ

Showing the 12 most recent of 20 posts we hold for @aureliiflood. 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,405,312 of 1,481,217entries 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.

Forward network

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.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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

“Aureli Flood Info” (@aureliiflood), 27 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/aureliiflood.

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.