Telegram RegisterThe public register of Telegram
Telegram profile photo for ᥲnᥲvrin || +33

Channel

ᥲnᥲvrin || +33

@anavrinflood

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

12subscribers

-2 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-1003843035810
TypeChannel
Username@anavrinflood
CreatedBetween 1 February 2026 and 25 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live2 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/anavrinflood

Growth

12141310 August 2026 — 14 subscribers12 August 2026 — 14 subscribers18 August 2026 — 13 subscribers2 September 2026 — 12 subscribers10 August 20262 September 2026
4 measurements spanning 23 days, net -2. 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 12–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 04:5212-1
18 Aug 2026, 01:0713-1
12 Aug 2026, 02:0214no change
10 Aug 2026, 11:1514first reading

Engagement

16 posts held, back to 25 July 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 page of 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 16 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
56s
Average length
14s

Measured directly from 4 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.

Recent posts

29 Jul 2026, 11:28 UTC46 viewsread 12 August 2026

мы с совлд решили закрыть флуд. с союзами расторг,всем желаю удачи в дальнейшем развити!

27 Jul 2026, 13:30 UTC15 viewsread 12 August 2026
Forwarded from @livixx1nfo

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

27 Jul 2026, 13:30 UTC14 viewsread 12 August 2026
Forwarded from @banzyefllloPhoto

🎁 nᥱw ViDᥱo 。。`片思い 💎 id :: ??? cr » m𑄝kα 🖤 › αмбαсαдоры этой пᥱсни #bnzrp + рк

27 Jul 2026, 07:07 UTC10 viewsread 12 August 2026
Forwarded from @banzyefllloPhoto

🎁 nᥱw ViDᥱo 。。`片思い 💎 id :: нᥱ нαшα cr » w𑄝nhee🖤 › дαйтᥱ нью 🥺 #bnzrp + рк

26 Jul 2026, 12:03 UTC11 viewsread 12 August 2026
Forwarded from @banzyeflllo

🔴🔴🔴 🔴🔴🤩🔴26.О7.26🔴🔴🔴 сегодня бензинчикам исполнился месяц ! время очень быстро пролетело и уже целый месяц мы вместе, хоть в чате нас и мало 🥲 всем сз спасибо за большую поддержку, всех любим 🖤 также хочу поздравить аризону и шакальчиков !! если не сложно, то вы, сз, можете поставить иниц с поздравлениями ! нам с мокой будет очень приятно BNZHBD / BNZDAY #bnzrp + поздравления

25 Jul 2026, 07:37 UTC18 viewsread 12 August 2026
Forwarded from @yumi_flood005File

𝒩ew vide𑄜 ! ℐd :: ?? ℰdit𑄜r :: джию 𝒯ik 𝒯𑄜k :: umi.ld #сзрп #yumrp

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

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

“ᥲnᥲvrin || +33” (@anavrinflood), 12 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/anavrinflood.

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.