Telegram RegisterThe public register of Telegram

Channel

. . n𐐫ᧉ𑜀ׁı ınẜ𐐫

@noemiflood

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

203subscribers

+37 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003931072689
TypeChannel
Username@noemiflood
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/noemiflood

Growth

166203184.57 August 2026 — 166 subscribers8 August 2026 — 173 subscribers8 August 2026 — 173 subscribers15 August 2026 — 203 subscribers7 August 202615 August 2026
4 measurements spanning 8 days, net +37. 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 160–209 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 19:15203+30
8 Aug 2026, 14:30173no change
8 Aug 2026, 05:31173+7
7 Aug 2026, 08:17166first reading

Engagement

16 posts held, back to 7 August 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
7.30%
avg views ÷ 203 subscribers
Avg views / post
14.8
16 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
16
of 16 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 8 August 2026
Posts held16 (7 August 20268 August 2026)
Views total237
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 14: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.

Recent posts

8 Aug 2026, 11:22 UTC19 viewsread 8 August 2026
Forwarded from @sakura_flood01Photo

А𑀝𑀝𐌏ЦИАЦИИ Ф𐌡УД𐌏В ʙᥱдущᥙᥔ : #йеджи ᴛᥱⲙᥲ : ᥴᥱκρᥱᴛ 𐌿РАВИ𐌡А : ① быᴛь ᴨᴏдᴨиᴄᴀныʍ нᴀ инɸᴏ бᴇɜ дᴀᴧьнᴇйɯᴇй ᴏᴛᴨиᴄᴋи ② ᴩᴨ ʙ инɸᴏ(ᴄᴋᴩин ʙ ᴋᴏʍʍ|ᴄɜ нᴇ ᴏбьяɜᴀᴛᴇᴧьнᴏ) ③ ᴨᴏᴄᴛᴀʙиᴛь ᴩᴇᴀᴋ ④ ᴀʙᴀᴛᴀᴩᴋᴀ и юɜ ʙ ᴋᴏʍʍ учᴀᴄᴛниᴋи 𝟪/𝟣𝟧 #sakuraрп #сзрп

7 Aug 2026, 20:04 UTC39 viewsread 8 August 2026

рпт конец начало если кого то пропустила – @vtkssx

7 Aug 2026, 20:03 UTC38 viewsread 8 August 2026
Forwarded from @Adrenaline2026flFile

ִᤳ۫⌒‌۫⌒۫ ◌⃘ ֺ۪ 𓈒 ꒰ ੭୧ ꒱ִ 𓈒 ○‌ִ ۫⌒‌۫⌒‌ ִ۫ᤳ 𝒜𝑑𝑟𝑒𝑛𝑎𝑙𝑖𝑛𝑒 𝑓𝑙𝑜𝑜𝑑 нуждается в ответственной администрации!! Админ по нью 0/2 ︶︶︶ ⊹ ︶︶︶ ୨♡୧ ︶︶︶ ⊹ ︶︶︶ Монтажёр 2/3 ︶︶︶ ⊹ ︶︶︶ ୨♡୧ ︶︶︶ ⊹ ︶︶︶ Админ по строчкам 0/1 ︶︶︶ ⊹ ︶︶︶ ୨♡୧ ︶︶︶ ⊹ ︶︶︶ Админ чат 0/1 •───────•°•❀•°•───────•

7 Aug 2026, 20:03 UTC17 viewsread 8 August 2026
Forwarded from @Adrenaline2026fl

Закажите пожалуйста у меня аватарки и баннеры 🥺🥺 https://t.me/avatarsbanner #сзрп

7 Aug 2026, 20:02 UTC15 viewsread 8 August 2026
Forwarded from @nightverse1

союзы, я надеюсь на что не отписалась от никого. Мне кажется что я вышла откуда-то случайно, можете проверить пожалуйста. #сзрп #nvsrp

7 Aug 2026, 20:01 UTC13 viewsread 8 August 2026
Forwarded from @chaerinfo

52 ➤ ➤ 200 #𝖼𝗁𝖾𝗋𝗂𝗋𝗉

7 Aug 2026, 20:01 UTC12 viewsread 8 August 2026
Forwarded from @chaerinfo

ищем союзы 1:1 пж, писать @yo_una #𝖼𝗁𝖾𝗋𝗂𝗋𝗉

7 Aug 2026, 20:00 UTC10 viewsread 8 August 2026
Forwarded from @jubilant_flood

Простите, но у меня уже очень много союзов. Но закрывать набор я не буду! Но хочу ввести новое правило: ВСЕ РП — только В ЛС. Скоро у меня начнётся учёба и появится больше дел, поэтому я не смогу одна всё это разбирать. 1. Все РП — в ЛС. 2. Буду искать администраторов по союзам. Умоляю, без разрывов!🙏 И, пожалуйста, проверьте, есть ли вы в папке.👇 ПАПКА РП ПАПКА ВЗ Если нету напишите в коммы👇 #jubi_rp #сз

7 Aug 2026, 19:58 UTC12 viewsread 8 August 2026
Forwarded from @riwweXD1nfoPhoto

🔳 ˚𖥔⁺𝅄 🤩𝑙𝑢𝑡𝑡𝑒𝑟 𝑓𝑓𝑙𝑜𝑜𝑑 .. 🌸 🤩 . Navîg𐐼tion 🤩 🔵 🤩⏜ְ꤮ 💎 𝑹ꪮles ˛˛ ֺ ִ 𝑹ules 😇 ❤️ 𝇄˖ ִ۫* 𝅄ׄ ⓘ 𝖿𝖺𝗆𝖾 𝗂𝗌 𝖺 𝗀𝗎𝗇, 𝖺𝗇𝖽 𝖨 𝗉𝗈𝗂𝗇𝗍 𝗂𝗍 𝖻𝗅𝗂𝗇𝖽 🤩 🤩 ֹ 𝆬ׄ ꕮ . ˒˓ 𝗆𝗒 𝗐ᦅ𝗋𝗅𝖽 𝆺ִ𝅥𝆬ׄ 🤩.. 𝑷ūrges 🗝 ׁ 𝅄 🤩 𝑹est 🤩. uniᡣ𐭩ns ➿🎀 🤩𝐀dꩇׁׅ֪݊iัns 🤩 𝚩ꪮᨵׁׅׅst 🕯.ೃ 🎀 initials

7 Aug 2026, 19:58 UTC11 viewsread 8 August 2026
Forwarded from @zivertfloo1

У нас прошла небольшая чистка, я очень разочарована Баны: Джису, ын че, Жизель, у остальных не было подписаны роли Варны: - Ищем Ньюшек #сзрп

7 Aug 2026, 19:57 UTC10 viewsread 8 August 2026
Forwarded from @nivarafloodPhoto

Привет нивары, к сожалению или к счастью мы берем рест, на сколько не знаю, у нас сейчас проблемы с аккаунтом флуда, из за этого нету нью+актива, как только все наладится мы вернемся, я это решила сама, так что да, ждите, с любовью нивары, и пожалуйста давайте без разрывов, рп таймы может будут но точно не от меня, покаа #nvrp #сзрп

Showing the 12 most recent of 16 posts we hold for @noemiflood. 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 — 34,403 of 1,480,688entries 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

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

“. . n𐐫ᧉ𑜀ׁı ınẜ𐐫” (@noemiflood), 203 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/noemiflood.

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.