Telegram RegisterThe public register of Telegram
Telegram profile photo for Pluto

Channel

Pluto

@plutouttahere

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

1,906subscribers

-25 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001655038663
TypeChannel
Username@plutouttahere
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held13
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/plutouttahere

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 46% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,9061,9311,918.56 August 2026 — 1,931 subscribers6 August 2026 — 1,931 subscribers7 August 2026 — 1,928 subscribers9 August 2026 — 1,927 subscribers12 August 2026 — 1,930 subscribers16 August 2026 — 1,926 subscribers19 August 2026 — 1,922 subscribers23 August 2026 — 1,923 subscribers26 August 2026 — 1,921 subscribers29 August 2026 — 1,919 subscribers4 September 2026 — 1,914 subscribers10 September 2026 — 1,907 subscribers13 September 2026 — 1,906 subscribers6 August 202613 September 2026
13 measurements spanning 39 days, net -25. 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 1,902–1,935 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 20:581,906-1
10 Sept 2026, 03:551,907-7
4 Sept 2026, 18:401,914-5
29 Aug 2026, 00:051,919-2
26 Aug 2026, 08:431,921-2
23 Aug 2026, 07:581,923+1
19 Aug 2026, 22:111,922-4
16 Aug 2026, 14:441,926-4
12 Aug 2026, 16:151,930+3
9 Aug 2026, 17:221,927-1
7 Aug 2026, 03:481,928-3
6 Aug 2026, 06:341,931no change
6 Aug 2026, 05:211,931first reading

Engagement

13 posts held, back to 12 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 2 pages 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 13 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

111 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 51.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5751.4%
1614.4%
🔥1311.7%
🤩98.11%
🖕76.31%
👎32.70%
😁32.70%
🍌21.80%
😭10.901%

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 13 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 111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 12 June 2026 to 3 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

3 Aug 2026, 15:28 UTC609 views14 reactionsread 7 August 2026
Photo

Пробил $100М волюма на экстендед за две с половиной недели 83.95% мейкер волюм 16.05% тейкер волюм 1.31% мейкер маркет шейр Купил новую лимитку Babolat x Lamborghini. Играть можно конечно но за такие деньги ее только на полку ставить. Готовлюсь к FIP Gold в Сербии через 3 неделю #summerMMute

🤩9🔥5

1 Aug 2026, 13:31 UTC718 views4 reactionsread 7 August 2026
Photo

Working on a weekend like usual Way off in the deep end like usual

4

30 Jul 2026, 13:21 UTC890 views3 reactionsread 7 August 2026

GRVT через час листится на всех биржах. Закраймили токены у комьюнити по максимуму. Вначале предложили выбрать получить токены на тге или с мультипликатором 2/3/4х но с локом. После дедлайна навесили 8 месяцев вестинг и тем кто выбрал 100% анлок на тге. Колзам тоже частичные вестинги влупили. Короче на тге токенов в рынке практически не будет, как и фьючей от бинанса. Варианта тут по идее два: Краймить график пока

😁2🔥1

28 Jul 2026, 09:15 UTC≈1,040 views9 reactionsread 7 August 2026
Photo

За прошлую неделю я сделал $50m мейкер волюма на экстендед. Это позволило мне достичь 1% 30d майкер маркет шейр и начать получать ребейты 0.004% за исполненные лимитные ордера. Были получены первые 925 бач + 5к поинтов + спред. В ближайших планах оптимизировать страты и достичь >5% мейкер маркет шейр. + сегодня запускаюсь на ondoperps там сейчас каждую неделю раздают по $175k ревардов + поинты summerMMute

🔥71😁1

17 Jul 2026, 17:00 UTC≈1,140 views6 reactionsread 7 August 2026
Photo

Сегодня забрал свою эзерфаевскую карту. Теперь я крутой.

6

1 Jul 2026, 11:21 UTC≈1,540 views2 reactionsread 7 August 2026
Photo

Выглядит как оверреакция на анонс OUSD. Слишком много времени еще должно пройти чтобы опенстандарт получил какой то трекшен. Пока только анонсы. Взял небольшой лонг Кстати, для тех кто торгует рва, там ондо по 100к бач разадают каждую неделю за объемы и тд https://app.ondoperps.xyz/?ref=CH89HM

👍2

26 Jun 2026, 18:09 UTC≈1,810 views27 reactionsread 7 August 2026
Photo

Это уже считается как кризис среднего возраста?

👍26😭1

18 Jun 2026, 11:01 UTC≈1,820 views21 reactionsread 7 August 2026
Photo

Fuck Plasma just use Etherfi Сегодня обсуждал со знакомым кто какие карты юзает и несмотря на всю прелесть вывода крипты в рб, я уже полгода юзаю в 99% времени эзерфаевские карты. За это время заблочили только одну карту(при блоке деньги с аккаунта вывести можно), с оплатой в рб/европе ни разу проблем не возникло. Снимать наличные можно даже в рб, кешбек 3% с каждой оплаты и для меня очень удобно, что я могу юзать

👍21

12 Jun 2026, 17:20 UTC≈1,540 views14 reactionsread 7 August 2026

Поинт получается вышел по по 2.1$ в среднем на не мейн акках. Онет

🖕7👎3🍌2👍2

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

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

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.

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

“Pluto” (@plutouttahere), 1,906 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/plutouttahere.

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.