Telegram RegisterThe public register of Telegram
Telegram profile photo for ⌗ инɸᴏ🎐 !! - ꒰ 𝙌𝙐𝙀𝙍𝙀𝙉𝘾𝙄𝘼 𝙁𝙇𝘿 ⑅꒱੭ ┄ ꔛ

Channel

⌗ инɸᴏ🎐 !! - ꒰ 𝙌𝙐𝙀𝙍𝙀𝙉𝘾𝙄𝘼 𝙁𝙇𝘿 ⑅꒱੭ ┄ ꔛ

@querenciaflood

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

289subscribers

+71 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002694739904
TypeChannel
Username@querenciaflood
CreatedBetween 1 April 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/querenciaflood

Growth

216289252.59 August 2026 — 218 subscribers9 August 2026 — 216 subscribers16 August 2026 — 289 subscribers9 August 202616 August 2026
3 measurements spanning 8 days, net +71. 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 205–300 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 19:38289+73
9 Aug 2026, 10:32216-2
9 Aug 2026, 03:02218first reading

Engagement

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

ERR · 30 days
80.1%
avg views ÷ 289 subscribers
Avg views / post
231
5 posts measured
Reaction rate
3.85%
reactions ÷ views · ER floor
Posts in window
5
of 20 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. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held20 (25 June 20268 August 2026)
Views total1,157
Reactions total33
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 03:02 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.

Reaction mix

177 reactions across 13 posts, in 11 distinct kinds. The most used accounts for 27.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53732109243310719754827.1%
custom 54473682591605379852815.8%
custom 53348606545389505682313.0%
custom 54022174670009495472313.0%
custom 5334553104815784621126.78%
custom 5335043070389943957126.78%
custom 5334723056671686861105.65%
custom 536855988706636178773.95%
custom 537077639942875224973.95%
custom 533703855944030657342.26%
custom 537512986417931927731.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 13 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 177reactions 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 25 June 2026 to 8 August 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

8 Aug 2026, 16:49 UTC42 viewsread 9 August 2026

ммм сладкие не отписывайтесь будет конкурс на ) #) #))@

29 Jul 2026, 12:10 UTC206 views20 reactionsread 9 August 2026
Photo

💕💕💕

custom 537321092433107197511custom 53348606545389505684custom 54473682591605379854custom 53345531048157846211

26 Jul 2026, 11:36 UTC265 views4 reactionsread 9 August 2026

💭🪷🤩абор открыт, ждём вас, сладкие.. @QUERENCIAFLD_BOT🪷

custom 53732109243310719753custom 53345531048157846211

23 Jul 2026, 15:32 UTC386 views9 reactionsread 9 August 2026
Photo

🤍🤩😻🪷добрый день. 🤩нас на лайф канале проходит некий 🤩🪷🔀🔀🤍нонтайм 🤍🤍🤍 💭🪷🤩 сли у вас были/есть вопросы к владельцу или админам, то у вас есть возможность их задать здесь – анонтайм🪷

custom 53348606545389505685custom 53732109243310719752custom 54022174670009495472

10 Jul 2026, 10:08 UTC510 views19 reactionsread 9 August 2026

200🤍🌟

custom 54022174670009495478custom 53348606545389505683custom 53685598870663617872custom 53732109243310719752custom 53751298641793192772custom 54473682591605379852

25 Jun 2026, 09:03 UTC762 views8 reactionsread 9 August 2026

какие впечатления приф

custom 53732109243310719755custom 53685598870663617873

25 Jun 2026, 09:00 UTCviews —

⌗ инɸᴏ🎐 !! - ꒰ 𝙌𝙐𝙀𝙍𝙀𝙉𝘾𝙄𝘼 𝙁𝙇𝘿 ⑅꒱੭ ┄ ꔛ pinned a photo

25 Jun 2026, 09:00 UTC492 views20 reactionsread 9 August 2026
Photo

🤩🤩🪷🪦🤩🤩nitials 🐾🤩555 🤩🤩🤩🤩🤍🤍🤍🤍🤍 ᵇᵉˢᵗ ᶞʳᶰˢ 555 ᵒᶰᶫʸ ᶞʳᶰᶜ キュラ ᶞʳᶰˢ ᶞʳᶰˢ qrns ᶫᵒᵛᵉ ᶞʳᶰᶜ ᶠᵒʳᵛ ᶞʳᶰˢ ᵇᶦᵗᶜʰ ᶞʳᶰˢ レンシ ⁵⁵⁵ ᶫᵒᵛᵉ ⁵⁵⁵ 🤩🤩🤩🤩🤍🤍🤍🤍🤍

custom 54473682591605379855custom 53732109243310719753custom 54022174670009495473custom 53345531048157846212custom 53347230566716868612custom 53348606545389505682custom 53350430703899439572custom 53751298641793192771

25 Jun 2026, 09:00 UTC564 views18 reactionsread 9 August 2026
Photo

🥹🤩rns🥹🌸🌸▫️🤩ole list🪷🥹 🤩🔀 🎀в списке указаны 🤩🤩🤩только занятые роли 🔀 🤩🐾 admin 🤍 🪷 🪷🤩booking🤩🪷 🤍🤍 🤩исать @QUERENCIAFLD_BOT🪷 🤍🤍

custom 53370385594403065734custom 53347230566716868613custom 53732109243310719753custom 53348606545389505682custom 53350430703899439572custom 54022174670009495472custom 54473682591605379852

Showing the 12 most recent of 20 posts we hold for @querenciaflood. 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 — 106,949 of 1,550,220entries 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 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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“⌗ инɸᴏ🎐 !! - ꒰ 𝙌𝙐𝙀𝙍𝙀𝙉𝘾𝙄𝘼 𝙁𝙇𝘿 ⑅꒱੭ ┄ ꔛ” (@querenciaflood), 289 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/querenciaflood.

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.