Telegram RegisterThe public register of Telegram
Telegram profile photo for Satoshi Frame

Channel

Satoshi Frame

@SatoshiFrame

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Cite this entry

4,248subscribers

-384 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002879027383
TypeChannel
Username@SatoshiFrame
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held29
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/SatoshiFrame

Topic

Crypto & trading — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 the other topics.

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
@SatoshiFrame/2732 · this entry2 Aug 2026, 12:28 UTC@Trading_novin_tahlil/3622 Aug 2026, 12:28 UTC1.00under a minute
@SatoshiFrame/2735 · this entry3 Aug 2026, 13:29 UTC@Trading_novin_tahlil/3643 Aug 2026, 13:29 UTC1.00under a minute
@SatoshiFrame/2737 · this entry4 Aug 2026, 13:25 UTC@Trading_novin_tahlil/3674 Aug 2026, 13:25 UTC1.00under a minute
@SatoshiFrame/2741 · this entry5 Aug 2026, 16:46 UTC@Trading_novin_tahlil/3715 Aug 2026, 16:46 UTC1.00under a minute
@SatoshiFrame/2743 · this entry5 Aug 2026, 17:06 UTC@Trading_novin_tahlil/3735 Aug 2026, 17:06 UTC1.00under a minute
@SatoshiFrame/2749 · this entry7 Aug 2026, 04:00 UTC@Trading_novin_tahlil/3747 Aug 2026, 04:00 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@Trading_novin_tahlil13 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (7–6)

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 6 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 31 comparable posts for this entry, running 2 August 2026 to 11 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @SatoshiFrame — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

4,2354,6324,433.57 August 2026 — 4,632 subscribers7 August 2026 — 4,632 subscribers8 August 2026 — 4,623 subscribers11 August 2026 — 4,594 subscribers14 August 2026 — 4,564 subscribers17 August 2026 — 4,546 subscribers20 August 2026 — 4,523 subscribers24 August 2026 — 4,484 subscribers27 August 2026 — 4,453 subscribers30 August 2026 — 4,425 subscribers2 September 2026 — 4,400 subscribers6 September 2026 — 4,378 subscribers11 September 2026 — 4,361 subscribers15 September 2026 — 4,342 subscribers19 September 2026 — 4,331 subscribers30 September 2026 — 4,371 subscribers6 October 2026 — 4,387 subscribers12 October 2026 — 4,371 subscribers15 October 2026 — 4,356 subscribers18 October 2026 — 4,330 subscribers21 October 2026 — 4,311 subscribers24 October 2026 — 4,307 subscribers27 October 2026 — 4,293 subscribers29 October 2026 — 4,281 subscribers1 November 2026 — 4,279 subscribers4 November 2026 — 4,257 subscribers7 November 2026 — 4,248 subscribers10 November 2026 — 4,235 subscribers15 November 2026 — 4,248 subscribers4,2487 August 202615 November 2026
29 measurements spanning 100 days, net -384. 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 4,175–4,692 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
15 Nov 2026, 22:214,248+13
10 Nov 2026, 08:494,235-13
7 Nov 2026, 06:494,248-9
4 Nov 2026, 12:584,257-22
1 Nov 2026, 06:354,279-2
29 Oct 2026, 15:164,281-12
27 Oct 2026, 00:494,293-14
24 Oct 2026, 10:004,307-4
21 Oct 2026, 19:584,311-19
18 Oct 2026, 18:574,330-26
15 Oct 2026, 14:494,356-15
12 Oct 2026, 18:164,371-16
6 Oct 2026, 15:184,387+16
30 Sept 2026, 02:004,371+40
19 Sept 2026, 15:194,331-11
15 Sept 2026, 02:164,342-19
11 Sept 2026, 07:364,361-17
6 Sept 2026, 07:224,378-22
2 Sept 2026, 09:344,400-25
30 Aug 2026, 01:254,425first reading

Engagement

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

Reaction mix

92 reactions across 34 posts, in 5 distinct kinds. The most used accounts for 51.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥4751.1%
❤3335.9%
🤣66.52%
👍55.43%
custom 511656526952268020311.09%

Custom emoji. One 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 count beside it is Telegram’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 34 of the 45 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 92 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 45 most recent posts we hold, published 2 August 2026 to 11 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

11 Aug 2026, 20:00 UTC52 views3 reactionsread 12 August 2026

دوستان عزیز، تصمیم گرفتیم چند روزی از بازار فاصله بگیریم و فرصتی برای استراحت داشته باشیم. به همین خاطر تا روز سه‌شنبه فعالیتی نخواهیم داشت. از همراهی و درک شما ممنونیم؛ و البته ری‌اکشن‌هاتون هم مثل همیشه فراموش نشه ❤️ سه‌شنبه برمی‌گردیم و فعالیت رو طبق روال ادامه می‌دیم. 🏴

❤‍🔥3

11 Aug 2026, 04:29 UTC90 views1 reactionsread 12 August 2026
Photo

💵 #AVAXUSDT 1H 🤑 آواکس تو یک ساعته خودش، با ریجکت از مقاومت چهار ساعته 6.922$ یک ریزش شارپ و تجربه کرد و هم اکنون قیمت درون یک ساختار رنج قرار گرفته. 📊 خریدار ها اگه موفق به شکست مقاومت 6.570$ بشن قیمت میتونه تا لول مقاومتی چهار ساعته تو قیمت 6.922$ حرکت داشته باشه. 🐳 همچنین قیمت اگه موفق به شکست مقاومت 6.570$ نشه، شکست کف فعلی تو حمایت 6.421$ باعث کاهش قیمت تا لول حمایتی 6.100$ میشه. 🧮 اوسیلاتور rsi هم یک ساختار…

👍1

11 Aug 2026, 04:25 UTC78 views1 reactionsread 12 August 2026
Photo

💵 #BTCUSDT 1H 🤑 بیتکوین تو یک ساعته خودش با ریجکت از مقاومت 62260$ یک فشار فروش نسبتا خوبی و تجربه کرد. ⛏ فروشنده ها موفق به شکست کف 64725$ شدن و قیمت با ریزشی که داشت به روی یک حمایت کوتاه مدت تو قیمت 63878$ قرار گرفته. 🐳 فروشنده ها اگه موفق به شکست حمایت تازه ساخت فعلی تو قیمت 63878$ بشن قیمت میتونه تا لول بعدی حمایتی حرکت کنه. 🧲 همچنین قیمت اگه از این محدوده رنج فعلی حمایت بشه و به سمت بالا حرکت کنه، شکست مقاو…

👍1

11 Aug 2026, 04:21 UTC70 views1 reactionsread 12 August 2026

😉 سلام بچه ها صبحتون بخیر

❤‍🔥1

10 Aug 2026, 19:21 UTC87 viewsread 12 August 2026
Photo

💵 #ICPUSDT 4H UPD 🧲 ایسیپی تو چهار ساعته خودش موفق به شکست مقاومت 2.22$ شد و قیمت با شکست این مقاومت حدود 5 درصد پامپ شد. ⛏ قیمت با حجم خرید خوبی داره به سمت مقاومت چهار ساعته 2.356$ حرکت میکنه، شکست این مقاومت با افزایش حجم خرید میتونه باعث افزایش قیمت تا لول های بعدی مقاومتی بشه. 🐳 کندل چهار ساعته کنونی یه کندل بلو آف به حساب میاد و حدود 40 دقیقه تا کلوز کندلش زمان باقی هست. ⏳ قیمت احتمالا به زیر این مقاومت است…

10 Aug 2026, 19:17 UTC81 viewsread 12 August 2026

👼 تریگرش فعال شد و مقاومت چهار ساعته 2.220$ شکسته شد، بریم یه آپدیت از ICP داشته باشیم.

10 Aug 2026, 10:12 UTC94 views2 reactionsread 12 August 2026
Photo

💵 #NEOUSDT 4H 📍 نعو یک ساختار نزولی در تایم فریم های بالاتر خودش داره و همچنین تو چهار ساعته خودش پس از ریزش هایی که تجربه کرده به یک حمایت چهار ساعته رسیده. ⭐ قیمت با رسیدن به حمایت چهار ساعته 1.805$ مقداری حمایت شده، قیمت نعو هم اکنون در نزدیکی این حمایت قرار داره. 🐳 فروشنده ها اگه موفق به شکست حمایت چهار ساعته 1.805$ بشن قیمت میتونه تا لول بعدی حمایتی حرکت کنه. 🧮 همچنین قیمت اگه از این حمایت چهار ساعته یک حمای…

❤2

10 Aug 2026, 09:52 UTC93 views1 reactionsread 12 August 2026
Photo

💵 #ONDOUSDT 4H 💡 اوندو تو چهار ساعته خودش پس از ریزش هایی که داشت به روی یک حمایت چهار ساعته تو قیمت 0.3467$ قرار گرفته. ⛏ فروشنده ها اگر موفق به شکست حمایت چهار ساعته 0.3467$ بشن قیمت میتونه تا لول بعدی حمایتی حرکت داشته باشه. 🐳 همچنین قیمت اگه از حمایت چهار ساعته فعلی حمایت بشه و به سمت بالا حرکت کنه شکست مقاومت چهار ساعته 0.3682$ باعث افزایش قیمت تا لول بعدی مقاومتی میشه. 📊 حجم خرید و فروش اوندو تو سه روز اخیر…

❤1

10 Aug 2026, 08:20 UTC97 views2 reactionsread 12 August 2026
Photo

💵 #BTCUSDT 4H 🤑 بیتکوین تو چهار ساعته خودش با ساخت سقف و کف هایی بالاتر هم اکنون به زیر مقاومت 65260$ قرار گرفته و داره به این مقاومت ریکشن نشون میده. ⛏ خریدار ها اگه موفق به شکست این مقاومت چهار ساعته تو قیمت 65260$ بشن، قیمت میتونه تا لول بعدی مقاومتی حرکت کنه. 👼 همچنین قیمت اگه از این محدوده با فشار فروش ریجکت بشه، توی تایم فریم های پایینتر تریگر ورود شورت میتونیم پیدا کنیم، چون قیمت میتونه تا لول های بعدی حمای…

❤1❤‍🔥1

10 Aug 2026, 06:45 UTC93 views4 reactionsread 12 August 2026

😉 سلام بچه ها صبحتون بخیر

❤4

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

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

“Satoshi Frame” (@SatoshiFrame), 4,248 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/SatoshiFrame.

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.