Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Neftis l Трейдинг, крипта, Web3

Channel

Crypto Neftis l Трейдинг, крипта, Web3

@metaneftis

Not marked by Telegram, checked 23 September 2026

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

1,107,550subscribers

+48,691 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1001556723943
TypeChannel
Username@metaneftis
DescriptionКанал в формате личного блога, пишу только свои мысли, выкладываю крипто проекты, DeFi инструменты, трейдинг, инвестирование. Ничего и никому не советую и не раздаю инвест-приказов. Для связи @rollsroyceadv
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 October 2026
Measurements held50
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/metaneftis

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@cryptodaily/112123 Aug 2026, 16:31 UTC@metaneftis/1782 · this entry4 Aug 2026, 06:40 UTC1.0014 hours
@cryptodaily/112154 Aug 2026, 13:01 UTC@metaneftis/1784 · this entry4 Aug 2026, 14:08 UTC1.0066 minutes
@cryptodaily/112225 Aug 2026, 17:02 UTC@metaneftis/1789 · this entry5 Aug 2026, 17:19 UTC1.0017 minutes
@cryptodaily/112276 Aug 2026, 15:03 UTC@metaneftis/1795 · this entry6 Aug 2026, 16:13 UTC1.0071 minutes
@cryptodaily/112327 Aug 2026, 14:16 UTC@metaneftis/1799 · this entry7 Aug 2026, 16:18 UTC0.992.0 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@cryptodaily5 (5/5 hand-verifiable sample passed)1.0071 minutes@cryptodaily (5–0)

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. 2 of the 5 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 22 comparable posts for this entry, running 3 August 2026 to 7 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 @cryptodaily. That is a statement about our reading window, not a claim of authorship.

Views and reactions moved apart

On 49 of the 97 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0609 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/20174 Oct 2026, 12:58 UTC30 minutes15,500 → 18,100at least +2,5001,796 → 1,822at most +36+152.1
/20174 Oct 2026, 12:58 UTC35 minutes18,100 → 22,000at least +3,8001,822 → 1,848at most +36+231.3
/20174 Oct 2026, 12:58 UTC24 minutes23,700 → 30,000at least +6,2001,848 → 1,848at most +10+377.3
/20174 Oct 2026, 12:58 UTC61 minutes30,000 → 35,500at least +5,4001,848 → 1,848at most +10+328.6
/204713 Oct 2026, 21:16 UTC64 minutes5,370 → 6,820at least +1,4401,964 → 1,964at most +10+87.6
/204713 Oct 2026, 21:16 UTC35 minutes8,740 → 10,400at least +1,5601,965 → 1,965at most +10+94.9
/204713 Oct 2026, 21:16 UTC59 minutes10,400 → 21,100at least +10,6001,965 → 1,965at most +10+645.1
/204713 Oct 2026, 21:16 UTC66 minutes21,100 → 25,400at least +4,2001,965 → 1,965at most +10+255.6
/20133 Oct 2026, 08:02 UTC31 minutes14,000 → 16,600at least +2,5001,565 → 1,565at most +10+152.1
/20133 Oct 2026, 08:02 UTC64 minutes20,800 → 25,900at least +5,0001,565 → 1,565at most +10+304.3
/20133 Oct 2026, 08:02 UTC59 minutes25,900 → 32,500at least +6,5001,565 → 1,565at most +10+395.6
/20092 Oct 2026, 09:44 UTC45 minutes18,000 → 22,100at least +4,0001,806 → 1,806at most +10+243.4
/20092 Oct 2026, 09:44 UTC55 minutes25,600 → 33,100at least +7,4001,806 → 1,806at most +10+450.3
/20184 Oct 2026, 20:37 UTC60 minutes15,000 → 17,700at least +2,6001,234 → 1,232at most +8+158.2
/20184 Oct 2026, 20:37 UTC65 minutes18,900 → 23,200at least +4,2001,232 → 1,231at most +9+255.6
/20298 Oct 2026, 08:15 UTC60 minutes10,100 → 16,300at least +6,1001,608 → 1,608at most +10+371.2
/20298 Oct 2026, 08:15 UTC66 minutes16,300 → 21,400at least +5,0001,608 → 1,608at most +10+304.3
/20329 Oct 2026, 08:15 UTC59 minutes15,500 → 19,200at least +3,6001,475 → 1,475at most +10+219.1
/20329 Oct 2026, 08:15 UTC59 minutes19,900 → 24,300at least +4,3001,475 → 1,475at most +10+261.7
/204613 Oct 2026, 15:48 UTC60 minutes8,570 → 10,300at least +1,6302,028 → 2,028at most +10+99.2
/204613 Oct 2026, 15:48 UTC31 minutes10,300 → 15,100at least +4,7002,028 → 2,028at most +10+286.0
/205817 Oct 2026, 06:50 UTC61 minutes19,400 → 23,000at least +3,5002,236 → 2,236at most +10+213.0
/205817 Oct 2026, 06:50 UTC39 minutes23,000 → 26,900at least +3,8002,236 → 2,236at most +10+231.3
/205917 Oct 2026, 13:31 UTC46 minutes9,160 → 10,900at least +1,640754 → 754at most +1+99.8
/205917 Oct 2026, 13:31 UTC39 minutes14,400 → 17,700at least +3,200754 → 754at most +1+194.7

Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).

What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.

Recorded under the keys clone_copy · view_reaction_decoupling, last confirmed 27 October 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

1,057,7681,107,5501,082,6597 August 2026 — 1,058,859 subscribers7 August 2026 — 1,058,859 subscribers8 August 2026 — 1,057,768 subscribers9 August 2026 — 1,060,956 subscribers10 August 2026 — 1,060,527 subscribers11 August 2026 — 1,060,870 subscribers12 August 2026 — 1,060,200 subscribers13 August 2026 — 1,060,767 subscribers14 August 2026 — 1,062,219 subscribers16 August 2026 — 1,062,117 subscribers17 August 2026 — 1,062,891 subscribers18 August 2026 — 1,064,449 subscribers19 August 2026 — 1,063,865 subscribers20 August 2026 — 1,064,329 subscribers21 August 2026 — 1,064,344 subscribers23 August 2026 — 1,064,128 subscribers24 August 2026 — 1,065,270 subscribers25 August 2026 — 1,065,929 subscribers26 August 2026 — 1,065,794 subscribers27 August 2026 — 1,066,075 subscribers28 August 2026 — 1,066,774 subscribers29 August 2026 — 1,067,063 subscribers31 August 2026 — 1,071,024 subscribers31 August 2026 — 1,071,030 subscribers1 September 2026 — 1,071,284 subscribers3 September 2026 — 1,073,939 subscribers4 September 2026 — 1,074,240 subscribers7 September 2026 — 1,074,648 subscribers10 September 2026 — 1,075,726 subscribers12 September 2026 — 1,076,785 subscribers14 September 2026 — 1,078,817 subscribers15 September 2026 — 1,079,951 subscribers18 September 2026 — 1,080,648 subscribers30 September 2026 — 1,087,440 subscribers5 October 2026 — 1,090,695 subscribers10 October 2026 — 1,099,899 subscribers13 October 2026 — 1,100,780 subscribers15 October 2026 — 1,102,037 subscribers15 October 2026 — 1,100,484 subscribers17 October 2026 — 1,104,291 subscribers17 October 2026 — 1,104,377 subscribers18 October 2026 — 1,105,089 subscribers19 October 2026 — 1,105,475 subscribers20 October 2026 — 1,105,322 subscribers21 October 2026 — 1,106,378 subscribers23 October 2026 — 1,106,789 subscribers23 October 2026 — 1,107,009 subscribers24 October 2026 — 1,105,992 subscribers25 October 2026 — 1,107,537 subscribers26 October 2026 — 1,107,550 subscribers7 August 202626 October 2026
50 measurements spanning 80 days, net +48,691. 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,050,301–1,115,017 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 50
Measured (UTC)SubscribersChange
26 Oct 2026, 22:061,107,550+13
25 Oct 2026, 18:491,107,537+1,545
24 Oct 2026, 22:201,105,992-1,017
23 Oct 2026, 20:311,107,009+220
23 Oct 2026, 00:041,106,789+411
21 Oct 2026, 22:271,106,378+1,056
20 Oct 2026, 14:411,105,322-153
19 Oct 2026, 17:471,105,475+386
18 Oct 2026, 21:011,105,089+712
17 Oct 2026, 22:281,104,377+86
17 Oct 2026, 01:211,104,291+3,807
15 Oct 2026, 23:271,100,484-1,553
15 Oct 2026, 00:201,102,037+1,257
13 Oct 2026, 16:301,100,780+881
10 Oct 2026, 00:161,099,899+9,204
5 Oct 2026, 20:411,090,695+3,255
30 Sept 2026, 11:571,087,440+6,792
18 Sept 2026, 04:351,080,648+697
15 Sept 2026, 23:171,079,951+1,134
14 Sept 2026, 06:371,078,817first reading

Engagement

298 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 165 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.05%
avg views ÷ 1,107,550 subscribers
Avg views / post
33,800
97 posts measured
Reaction rate
6.23%
reactions ÷ views · ER floor
Posts in window
97
of 298 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 27 October 2026
Posts held298 (3 August 2026 – 27 October 2026)
Views total3,279,800
Reactions total204,326
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Oct 2026, 08:46 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.

What this channel posts

Photos
≈1,290
Videos
≈58
Links
≈859

Lifetime counters from Telegram’s own channel header, read 26 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 37s
Average length
24s

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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 97 of this channel’s own posts over the last 30 days: across 94 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 6.6 hours of being posted; a typical post has already reached 29.3% of its 24-hour view count within the first hour, and 51.9% within the first six; the median 24-hour reach across those posts is 27,050 views — 2.44% of this channel’s own subscriber count (90th percentile 45,070).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/208827 Oct 2026, 00:46 UTC1030 minutes – 8.0 hours old18,500 views ~3,403 reactions60 minutes: 8,219 interp. → 3.0 hours: 11,800 → 6.0 hours: 15,400still climbing at last readingnot yet at 24h1.6 hoursprovisional — final view count still climbing
/208726 Oct 2026, 17:14 UTC2036 minutes – 16 hours old35,400 views ~3,129 reactions60 minutes: 7,508 interp. → 3.0 hours: 11,600 → 6.0 hours: 21,278 interp. → 12 hours: 33,600still climbing at last readingnot yet at 24h5.6 hoursprovisional — final view count still climbing
/208626 Oct 2026, 10:10 UTC2922 minutes – 23 hours old37,600 views ~4,179 reactions60 minutes: 9,540 interp. → 3.0 hours: 11,049 interp. → 6.0 hours: 13,200 → 12 hours: 16,400still climbing at last readingnot yet at 24h14 hoursprovisional — final view count still climbing
/208526 Oct 2026, 01:04 UTC3180 minutes – 32 hours old42,000 views ~4,076 reactions3.0 hours: 19,200 → 6.0 hours: 24,100 → 12 hours: 35,300 → 24 hours: 41,500still climbing at last reading41,500measured3.9 hours
/208425 Oct 2026, 16:45 UTC3476 seconds – 40 hours old44,700 views ~1,917 reactions60 minutes: 8,213 interp. → 3.0 hours: 15,926 interp. → 6.0 hours: 26,347 interp. → 12 hours: 39,900 → 24 hours: 43,800still climbing at last reading43,800measured5.1 hours
/208325 Oct 2026, 10:16 UTC399 minutes – 46 hours old34,400 views ~2,313 reactions60 minutes: 7,750 → 3.0 hours: 10,900 → 6.0 hours: 14,500 → 12 hours: 27,300 → 24 hours: 30,400 → 2 days: 34,400still climbing at last reading30,400measured6.7 hours
/208224 Oct 2026, 22:28 UTC483 minutes – 2 days old36,700 views ~2,017 reactions60 minutes: 8,141 interp. → 3.0 hours: 11,000 → 6.0 hours: 14,600 → 12 hours: 20,500 → 24 hours: 30,000 → 2 days: 36,200still climbing at last reading30,000measured9.0 hours
/208124 Oct 2026, 16:30 UTC5140 minutes – 3 days old31,800 views ~1,793 reactions60 minutes: 7,827 interp. → 3.0 hours: 9,200 → 6.0 hours: 14,100 → 12 hours: 22,700 → 24 hours: 24,800 → 2 days: 30,700still climbing at last reading24,800measured7.4 hours

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

772,095 reactions across 298 posts, in 69 distinct kinds. The most used accounts for 10.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍83,03310.8%
❤60,2517.80%
🔥56,7627.35%
💯38,6185.00%
🤔33,4764.34%
👏29,0273.76%
⚡28,9013.74%
🙏28,6223.71%
👀27,4093.55%
👌24,6523.19%
🏆24,0693.12%
🐳23,1903.00%
✍20,2942.63%
🙉18,2072.36%
🤝16,9372.19%
🤯16,8002.18%
🌚16,1802.10%
🍾15,7662.04%
😁15,5532.01%
🤩13,2651.72%
49 further kinds181,08323.5%

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

Measured over the 298 most recent posts we hold, published 3 August 2026 to 27 October 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

27 Oct 2026, 00:46 UTC≈18,500 views3,403 reactionsread 27 October 2026
Photo

🥇 Хотел ускорить перевод крипты, а отправил монеты скамеру Представьте: вы переводите деньги на другой кошелёк, но они всё не доходят. Решаете доплатить комиссию, чтобы перевод прошёл быстрее. Подтверждаете, а деньги уходят мошеннику. Так потерял деньги пользователь кошелька для хранения биткоина Electrum. Разработчики подтвердили атаку. Вот как она работала: 😮 Человек отправлял деньги, но сервер мошенника задерж…

👍1,390🤡390🌚359🐳270🤔243❤232👎219😱144

26 Oct 2026, 17:14 UTC≈35,400 views3,129 reactionsread 27 October 2026
Photo

🎮 Майнеры молча скупают железо За последние 30 дней хэшрейт биткоина вырос на 11% и снова пробил отметку в 1 зеттахэш. Звучит как заклинание, да? Сейчас объясню на пальцах. Хэшрейт — это общая мощность всех компьютеров, которые добывают биткоин. Чем больше машин включено в сеть, тем выше хэшрейт. А теперь главное: эти машины стоят бешеных денег. Плюс электричество, аренда, охлаждение. Просто так их никто не покуп…

👍734💯609🏆521👌332🤯286🙏206🔥160⚡153

26 Oct 2026, 10:10 UTC≈37,600 views4,179 reactionsread 27 October 2026

😮 Минус 10% от хая. Хватит или будет глубже? Биткоин за выходные сходил под $80К. Ликвидаций на $547 млн, почти все в лонгах. Из ETF за две недели вынесли около $910 млн 👌 Добавьте новости с Ближнего Востока и ФРС на этой неделе. В чатах снова пессимизм. Давайте посмотрим спокойно. На фактах. Есть интересная закономерность. Чем глубже была медвежка, тем сильнее потом трясёт в бычке. Как пружина: чем сильнее её сжа…

🔥1,860💯1,200👍450❤220🤔212😱119🤗53👌30

26 Oct 2026, 01:04 UTC≈42,000 views4,076 reactionsread 27 October 2026
Photo

😮 Горит Париж - Гори и Ledger В России впервые зафиксированы случаи продажи аппаратных криптокошельков Ledger со встроенными шпионскими модулями. Что произошло Где нашли: Скомпрометированный кошелек (Ledger Nano X) приобрели через российский маркетплейс (Ozon). В чем суть модификации: Внутрь корпуса устройства злоумышленники встроили миниатюрную дополнительную плату с антенной, заменили аккумулятор и добавили скр…

👍1,350💯785🔥564❤414🙏412👌247😁143🤩78

25 Oct 2026, 16:45 UTC≈44,700 views1,917 reactionsread 27 October 2026
Photo

🥇 Самая дорогая земля в мире В 2014 году миллиардер Чамат Палихапития купил участок у озера Тахо. Заплатил 2 739 биткоинов. Тогда это было $1,6 млн. Сегодня эти монеты стоили бы около $220 млн. Обычный кусок земли с соснами 🌲 А на этой неделе Чамат заявил: биткоин упрётся в потолок, потом его взломает искусственный интеллект, и цена уйдёт в ноль. Звучит страшно, и кажется, что “наверное этот опытный инвестор что-…

👻649👀403😁234🤔222👍145🎃84💯77🎅45

25 Oct 2026, 10:16 UTC≈34,400 views2,313 reactionsread 27 October 2026
Photo

🥇 Дежавю: где-то я это уже видел Смотрю на график биткоина и ловлю себя на мысли: это же 2023 год. Прямо под копирку. Напомню, как было тогда. Биток вырвался из диапазона, нарисовал новый недельный максимум… и пошёл вниз. Многие сразу решили: всё, бычка отменяется. А я тогда писал, что бычий рынок начался. Мне крутили у виска и смеялись. Что сделала цена? Вернулась к верхней границе старого диапазона, потрогала е…

🔥803💯464👍243🤓211❤171🤔96✍85🎉71

24 Oct 2026, 22:28 UTC≈36,700 views2,017 reactionsread 27 October 2026

🥇 Прибыль по сетке и прибыль по тренду: в чём разница и по какой цифре оценивать бота Откройте любого работающего сеточного бота на Pionex, и увидите несколько цифр прибыли. Прибыль по сетке зелёная и растёт, а рядом PnL по тренду, который бывает красным. Из-за него и общий итог иногда уходит в минус. Отсюда и стресс: бот вообще зарабатывает или нет? Участница нашего челленджа Станислава как раз так понервничала но…

✍507🔥330🤩278🌚248🏆150🕊140🍾111👻96

24 Oct 2026, 16:30 UTC≈31,800 views1,793 reactionsread 27 October 2026

🎰 КРИПТОРЫНОК МОЖЕТ РАСТИ ДАЖЕ БЕЗ НОВЫХ ПОКУПАТЕЛЕЙ Звучит странно, но для сильного движения цены не всегда нужен огромный приток свежих денег. Иногда достаточно, чтобы продавцов стало значительно меньше. Именно поэтому рынок может месяцами стоять на месте, а затем резко вырасти без каких-либо громких новостей. Разберёмся, как это работает. Представьте, что Bitcoin несколько недель торгуется около $80 000. Каж…

❤740✍374🏆243🙏139🔥83🎉52🗿41💊40

24 Oct 2026, 09:56 UTC≈29,900 views1,550 reactionsread 27 October 2026
Photo

💴 Ловушка перед выборами 3 ноября в США промежуточные выборы в Конгресс. И у биткоина есть одна хитрая привычка, связанная с этой датой. Посмотрите на картинку. Это прошлые выборы. Видите закономерность? За 20–30 дней до выборов рынок рассказывает толпе какую-то историю. И эта история почти всегда оказывается ЛОЖНОЙ. Как это работает: 📈 Перед выборами все радуются, цена ползёт вверх. После выборов рынок разворач…

😁576🙏293❤225👍163🤷86🐳83👌52☃32

23 Oct 2026, 23:23 UTC≈34,600 views2,143 reactionsread 27 October 2026

💴 У РЫНКА ЕСТЬ ПАМЯТЬ. И ОНА МОЖЕТ СТОИТЬ МИЛЛИАРДЫ Представьте, что Bitcoin несколько месяцев торговался около $100 000, а затем упал до $80 000. Теперь каждый раз, когда цена начинает восстанавливаться, в районе $100 000 появляются продавцы. Почему? Не обязательно потому, что актив стал слишком дорогим. Просто огромное количество людей когда-то покупало его именно там. И теперь они ждут возможности выйти хотя…

👍663❤457👌279✍166🙉145🎉115🕊111🤣84

23 Oct 2026, 17:44 UTC≈30,200 views1,707 reactionsread 27 October 2026

⚫️ НЕФТЬ ВЫШЕ $115. РЫНОК ГОТОВИТСЯ К НОВОМУ УДАРУ ПО ИРАНУ На мировых рынках снова усиливается напряжённость. Фондовые индексы снижаются, нефть торгуется выше $115, а инвесторы опасаются новой эскалации конфликта на Ближнем Востоке. Главный риск — возможный удар США и Израиля по Ирану. Участники рынка допускают, что военная операция может произойти в ближайшее время, в том числе после закрытия американских торго…

🙏398😐330✍252👍243👻154🌚90💋73😨68

23 Oct 2026, 12:30 UTC≈38,200 views3,909 reactionsread 27 October 2026

😏Крупное Обновление бота Рынок вернулся в активную фазу после летней спячки, бот снова усыпан сигналами, а значит это время для большого обновления, чтобы быть быстрее всех Что было изменено/добавлено: - Оптимизация алгоритмов доставки и получения связок. Самый быстрый режим также остается за Автотрейдером, но теперь есть возможность получения связок по API и в тарифе Трейдер (функционал получения связок через ТГ …

🤝939🙏692👍629❤414🔥351🏆250🌚210🤩170

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

Posts edited after publishing

@metaneftis edited 9 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
17 September 2026
Most recent edit
24 September 2026

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.

Domains linked from posts

5 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

x.com6 posts · 3 August 2026 – 7 August 2026 · example post
www.cnbc.comregistrable domain: cnbc.com1 post · 5 August 2026 – 5 August 2026 · example post
www.coinglass.comregistrable domain: coinglass.com1 post · 6 August 2026 – 6 August 2026 · example post
www.macrumors.comregistrable domain: macrumors.com1 post · 4 August 2026 – 4 August 2026 · example post
mobilesyrup.com1 post · 4 August 2026 – 4 August 2026 · example post

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

“Crypto Neftis l Трейдинг, крипта, Web3” (@metaneftis), 1,107,550 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/metaneftis.

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.