Telegram RegisterThe public register of Telegram

Channel

PIFAGOR TRADE | Indicator Dima Дима Пифагор

@dimapifagor

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

965subscribers

-8 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-1001502088567
TypeChannel
Username@dimapifagor
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/dimapifagor

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@pifagortrade/339323 Jul 2026, 09:57 UTC@dimapifagor/1460 · this entry23 Jul 2026, 09:57 UTC1.00under a minute
@pifagortrade/339523 Jul 2026, 12:18 UTC@dimapifagor/1462 · this entry23 Jul 2026, 12:18 UTC1.00under a minute
@dimapifagor/1468 · this entry27 Jul 2026, 17:19 UTC@pifagortrade/340027 Jul 2026, 17:19 UTC1.00under a minute
@pifagortrade/340129 Jul 2026, 16:53 UTC@dimapifagor/1469 · this entry29 Jul 2026, 16:53 UTC1.00under a minute
@pifagortrade/340331 Jul 2026, 13:21 UTC@dimapifagor/1474 · this entry31 Jul 2026, 13:24 UTC1.004 minutes
@pifagortrade/34112 Aug 2026, 21:13 UTC@dimapifagor/1477 · this entry2 Aug 2026, 21:13 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@pifagortrade9 (8/8 hand-verifiable sample passed)0.98under a minute@pifagortrade (90)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 9 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 23 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @pifagortrade. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

9659739697 Aug 2026, 09:16 — 973 subscribers7 Aug 2026, 14:27 — 965 subscribers7 Aug 2026, 09:167 Aug 2026, 14:27
2 measurements taken within a single day, net -8. 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 964–974 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 14:27965-8
7 Aug 2026, 09:16973first reading

Engagement

17 posts held, back to 21 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
23.6%
avg views ÷ 965 subscribers
Avg views / post
228
17 posts measured
Reaction rate
43.2%
reactions ÷ views · ER floor
Posts in window
17
of 17 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 6 August 2026
Posts held17 (21 July 20266 August 2026)
Views total3,869
Reactions total1,671
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 09:16 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

1,671 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 14.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🐳24514.7%
🤩21412.8%
👍19311.5%
🔥19311.5%
💯1599.52%
🥰1519.04%
👏1478.80%
🎉1358.08%
🗿1287.66%
🆒1066.34%

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

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

6 Aug 2026, 12:59 UTC186 views73 reactionsread 7 August 2026

Для любителей торговать акциями, металлами и индексами! Теперь на Bybit доступны два способа торговли традиционными финансовыми инструментами: xStocks (Cпот) • 1:1 обеспечены реальными акциями • Торговля 24/7 TradFi Perpetuals (Фьючерсы) • Торговля акциями, металлами и другими TradFi-активами с кредитным плечом. Привычный формат бессрочных фьючерсов, также 24/7 В честь сезона акция Stock Earnings Season с призовым

👏19🗿16👍13🔥13🐳12

2 Aug 2026, 21:13 UTC227 views109 reactionsread 7 August 2026
Video

Один трейдер выложил у себя в канале скриншот c сегодняшнего моего видео, где было видно часть торгового журнала, с подписью типо: «фу какой ужасный результат, аахаха и он еще такое в видео палит». ну во первых тайн у меня почти нет, поэтому могу и в видео. Трейдинг это не только плюсы а во вторых вот тебе полная история за последние 2 месяца. Попробуй посчитать. Ну или в джпт закинуть. А -1r = 2300 подсказажет нач

🐳53🥰16🤩14🎉13👏13

2 Aug 2026, 13:03 UTC212 views102 reactionsread 7 August 2026

🎞 БУДЬТЕ ОСТОРОЖНЫ! РЫНОК ГОТОВИТ ЖЕСТОКУЮ ЛОВУШКУ!!! Всем привет! В сегодняшнем видео разберем: - Когда логичнее закрывать текущий шорт? - Почему Эфир пока лучше не покупать? - От каких зон можно будет искать лонг по BTC? - Какой сценарий по Биткоину сейчас выглядит идеальным? - Почему психология в трейдинге часто важнее самого анализа? И это ещё не всё. Переходите по ссылке, Вас ждёт много полезной информации. П

👍34👏18🔥18🎉16🤩16

31 Jul 2026, 13:40 UTC216 views66 reactionsread 7 August 2026
Voice message

Ваш шорт Боты Когда лонг

👍16🥰16💯14🔥11🎉9

31 Jul 2026, 13:24 UTC214 views108 reactionsread 7 August 2026
Photo

Привет! 👋 Напоминаю: всем моим рефералам по-прежнему доступен бесплатный канал с торговыми сигналами. Сдекли даются заранее в канале с четким стопом и тэйком. 🔥 Общий результат команды: +19.8% за месяц 🤖 Также продолжается работа над ботом для автоматического следования за трейдерами. сигналы @Pifagor_Indicator_bot

🔥52👏17🎉15🤩13🥰11

31 Jul 2026, 13:21 UTC211 views136 reactionsread 7 August 2026
Photo

Photo, posted without a caption

🥰34🐳29💯27👍25🔥21

29 Jul 2026, 21:12 UTC225 views102 reactionsread 7 August 2026
Video

Руками открытых сделок нет. Бот продолжает работу. За последние 2 дня 6 сделок, все положительные. @Pifagor_Indicator_bot ->автоматизация торговли Все сделки бота

🤩47🎉18👍14🆒12🔥11

29 Jul 2026, 16:53 UTC226 views59 reactionsread 7 August 2026
Photo

В каждом ролике за последний месяц я предупреждал про этот индикатор и говорил где стоит закрыть лонг и открыть шорт В том числе закрывал лонг сам Отработало. Статистически все так, как и должно было быть Можно обратить внимание, что индикатор часто переходил за нулевую зону несколько раз подряд при отскоках. Исходя из этого и некоторых других аргументов, я предполагаю, что обновление 68-70 еще возможно Хотя лонг

💯19👍12🤩10🥰10🔥8

27 Jul 2026, 17:19 UTC225 views105 reactionsread 7 August 2026

Друзья, есть какие то индикаторы, метрики, данные которыми вы пользуетесь и хотели бы видеть бесплатно у меня на платформе? напишите @pifagor_admin Постараюсь реализовать

👍52🆒15🔥13🗿13🥰12

25 Jul 2026, 14:50 UTC242 views102 reactionsread 7 August 2026
Voice message

@QRypto_Turtle_bot

💯45🐳16🆒16🤩13👏12

25 Jul 2026, 14:29 UTC251 views93 reactionsread 7 August 2026

Раньше пользовался @antarctic_wallet_bot когда в РФ прилетал, что бы криптой платить через сбп. Сейчас там все косо криво и ничего не работает. Кто из рф чем пользуетесь в что бы криптой оплачивать рестораны и пр? Напишите пожалуйста в ютубе в комнтариях. А то все переблочено, каменный век

🐳45🗿15🆒14🥰11👍8

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“PIFAGOR TRADE | Indicator Dima Дима Пифагор” (@dimapifagor), 965 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/dimapifagor.

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.