Telegram RegisterThe public register of Telegram
Telegram profile photo for [НАБОР В АДМ!] poolverine & spideypool cf 𖦹

Channel

[НАБОР В АДМ!] poolverine & spideypool cf 𖦹

@poolverinexspidypool

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

136subscribers

+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-1002912680547
TypeChannel
Username@poolverinexspidypool
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 live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/poolverinexspidypool

Growth

13610 Aug 2026, 13:01 — 136 subscribers10 Aug 2026, 17:24 — 136 subscribers10 Aug 2026, 13:0110 Aug 2026, 17:24
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 135–137 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:24136no change
10 Aug 2026, 13:01136first reading

Engagement

15 posts held, back to 17 February 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
48.5%
avg views ÷ 136 subscribers
Avg views / post
66.0
8 posts measured
Reaction rate
9.85%
reactions ÷ views · ER floor
Posts in window
8
of 15 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 30 July 2026
Posts held15 (17 February 202630 July 2026)
Views total528
Reactions total52
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 13:01 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

60 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 38.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2338.3%
custom 52944733719526449911626.7%
custom 52941271761137507661118.3%
🌚58.33%
🎉35.00%
🔥23.33%

Custom emoji. 2 of the rows above are 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 10 of the 15 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 60reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 17 February 2026 to 30 July 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

30 Jul 2026, 10:34 UTC48 views8 reactionsread 10 August 2026
Photo

Тв нсфв : › фд сдох 🥀 zhuazhua8949 в твиттере 𝜗ৎ #тейк | #спайдипулы @poolverinexspidypoolbot 𝜗ৎ 📎: я охуела

custom 52944733719526449916custom 52941271761137507662

29 Jul 2026, 09:00 UTC50 views10 reactionsread 10 August 2026
Photo

Твкв… лёгкое нсфв?? Как это обозвать📎📎 : › Работы от разных художников(ну оно и видно) но мне показалось это забавным. Типо, в чём его проблема?? Мужик почему ты облизываешь руки????? Кредиты: Первый: thefuzzyaya Второй: Lemlinu Оба из твиттера (ну или Х) 𝜗ৎ #тейк | #спайдипулверины @poolverinexspidypoolbot 𝜗ৎ

custom 52944733719526449915🎉3custom 52941271761137507662

26 Jul 2026, 13:31 UTC65 views7 reactionsread 10 August 2026
Photo

ФУ ПОЧЕМУ ПИТЕР ПОЛУЧИЛСЯ ТАКОЙ ДУШКОЙ 𝜗ৎ #тейк | #спайдипулверины @poolverinexspidypoolbot 𝜗ৎ

🌚51custom 52944733719526449911

26 Jul 2026, 12:12 UTC67 views2 reactionsread 10 August 2026

Как вы думаете кто из них храпит 𝜗ৎ #тейк | #спайдипулверины @poolverinexspidypoolbot 𝜗ৎ

2

22 Jul 2026, 16:32 UTC87 views4 reactionsread 10 August 2026

: › я хз покидайте хэдканоны свои что-ли Я начну(может быть ООС потому что я не так давно начала шарить за Паука): Мне кажется Питер и Логан как-то глупо вступили в отношения, чуть ли не случайно, но возражать не стали потому что ну... Как-будто это был единственный приемлемый вариант?? Питер вначале этих запутанных отношений немного побаивался Логана(хотя во многих комиксах они друг друга ненавидят, я думаю в этой в

4

22 Jul 2026, 15:05 UTC69 views8 reactionsread 10 August 2026
Photo

Тв полуголое тело(?) : › вы там тоже как бы оживляйтесь да 𝜗ৎ #тейк | #спайдипулверины @poolverinexspidypoolbot 𝜗ৎ

6🔥1custom 52941271761137507661

21 Jul 2026, 21:17 UTC68 views5 reactionsread 10 August 2026
File

Тв прямое упоминание нсфв : › что угодно лишь бы фандом был жив... 𝜗ৎ #тейк | #спайдипулверины @poolverinexspidypoolbot 𝜗ৎ

custom 52941271761137507665

21 Jul 2026, 20:34 UTC74 views8 reactionsread 10 August 2026
Photo

: › что угодно лишь бы фд был жив 𝜗ৎ #тейк | #спайдипулверины @poolverinexspidypoolbot 𝜗ৎ

4custom 52944733719526449913🔥1

15 Jul 2026, 10:14 UTC114 views7 reactionsread 10 August 2026
Photo

тв кровь. пульвериныы. @z3l3n01 𝜗ৎ #тейк #пулверины | @poolverinexspidypoolbot 𝜗ৎ Вовремя я выложила конешно📎📎📎

5custom 52941271761137507661custom 52944733719526449911

18 Feb 2026, 06:42 UTC268 viewsread 10 August 2026
Forwarded from @echoesoftomorrowPhoto

ᅠ 💋 Echoes of Tomorrow – ваш портал в неизведанное будущее вселенной.❤️Теории, прогнозы, возможные сюжетные линии, скрытые знаки и намёки на грядущие события.💋 😻 Обсуждаем, гадаем, фантазируем — вместе создаём будущее любимых героев в сети телеграм каналов. 💋 ᅠᅠ 🌧️🌧️🌧️🌧️🌧️ 😻💋😻 ᅠᅠ правила анкета вп пары ᅠ 💋 список персонажей ᅠ список ожидания 💋🤩 ᅠᅠ буст чат тик-ток вести ᅠᅠ

18 Feb 2026, 06:41 UTC230 viewsread 10 August 2026
Forwarded from @nightwingCFDAILYPhoto

🤩 😻❤️😻 navigation 🌟🤩🤩😻 🐦 anon bot mp rules hashtags boost 😻🤩😻😻 Это конфэшн и дэйлик, посвящённый Дику Грейсону {из DC} во всех этапах его жизненного пути:: Робин, Найтвинг, Бэтмен, Агент 37 и прочее.😻 💥 Подписывайтесь, здесь всё самое лучшее по Грейсону!🐶 🐦 credit😻@kkurensia on Tumblr😻

17 Feb 2026, 13:23 UTC198 viewsread 10 August 2026

`꒰📎꒱⁠ : Тейкитейкитейки 𝜗ৎ #щп | @poolverinexspidypoolbot 𝜗ৎ

Showing the 12 most recent of 15 posts we hold for @poolverinexspidypool. 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,220,337 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“[НАБОР В АДМ!] poolverine & spideypool cf 𖦹” (@poolverinexspidypool), 136 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/poolverinexspidypool.

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.