Telegram RegisterThe public register of Telegram
Telegram profile photo for HAMSTER CRYPTO CALLS

Channel

HAMSTER CRYPTO CALLS

@HamsterCryptoCalls

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

8,582subscribers

-1,498 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002083516081
TypeChannel
Username@HamsterCryptoCalls
DescriptionOnly dm : @Hamsterown and @HamsterCallsOwn partner : @OWNERSKYRIMCALLS Partner : https://docs.rogerpad.finance Channel : https://t.me/HamsterCryptoCalls
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live11 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/HamsterCryptoCalls

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
@takkycall/323418 Apr 2026, 07:03 UTC@HamsterCryptoCalls/801 · this entry18 Apr 2026, 07:04 UTC1.00under a minute
@takkycall/323511 May 2026, 13:01 UTC@HamsterCryptoCalls/805 · this entry11 May 2026, 13:01 UTC1.00under a minute
@takkycall/323927 May 2026, 17:05 UTC@HamsterCryptoCalls/809 · this entry27 May 2026, 17:05 UTC1.00under a minute
@HamsterCryptoCalls/811 · this entry3 Jun 2026, 17:19 UTC@takkycall/32413 Jun 2026, 17:19 UTC1.00under a minute
@takkycall/324812 Aug 2026, 20:22 UTC@HamsterCryptoCalls/816 · this entry12 Aug 2026, 20:22 UTC1.00under a minute
@HamsterCryptoCalls/821 · this entry28 Sept 2026, 11:00 UTC@takkycall/325528 Sept 2026, 11: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
@takkycall13 (8/8 hand-verifiable sample passed)1.00under a minute@takkycall (11–2)

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. 4 of the 11 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 17 comparable posts for this entry, running 12 April 2026 to 11 November 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 @takkycall. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 12 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

8,58210,0809,33112 August 2026 — 10,080 subscribers12 August 2026 — 10,074 subscribers14 August 2026 — 10,008 subscribers15 August 2026 — 9,970 subscribers18 August 2026 — 9,853 subscribers21 August 2026 — 9,790 subscribers24 August 2026 — 9,727 subscribers28 August 2026 — 9,674 subscribers31 August 2026 — 9,621 subscribers3 September 2026 — 9,549 subscribers7 September 2026 — 9,512 subscribers11 September 2026 — 9,449 subscribers15 September 2026 — 9,413 subscribers25 September 2026 — 9,356 subscribers4 October 2026 — 9,180 subscribers10 October 2026 — 9,085 subscribers14 October 2026 — 9,050 subscribers17 October 2026 — 9,025 subscribers20 October 2026 — 8,998 subscribers24 October 2026 — 8,965 subscribers26 October 2026 — 8,940 subscribers30 October 2026 — 8,898 subscribers1 November 2026 — 8,841 subscribers4 November 2026 — 8,765 subscribers7 November 2026 — 8,699 subscribers11 November 2026 — 8,582 subscribers12 August 202611 November 2026
26 measurements spanning 91 days, net -1,498. 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 8,357–10,305 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
11 Nov 2026, 13:518,582-117
7 Nov 2026, 23:068,699-66
4 Nov 2026, 22:518,765-76
1 Nov 2026, 21:568,841-57
30 Oct 2026, 02:018,898-42
26 Oct 2026, 23:498,940-25
24 Oct 2026, 07:168,965-33
20 Oct 2026, 23:518,998-27
17 Oct 2026, 15:399,025-25
14 Oct 2026, 10:069,050-35
10 Oct 2026, 20:169,085-95
4 Oct 2026, 21:569,180-176
25 Sept 2026, 08:189,356-57
15 Sept 2026, 04:569,413-36
11 Sept 2026, 22:179,449-63
7 Sept 2026, 21:229,512-37
3 Sept 2026, 00:199,549-72
31 Aug 2026, 02:239,621-53
28 Aug 2026, 00:129,674-53
24 Aug 2026, 22:039,727first reading

Engagement

32 posts held, back to 25 March 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 41 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.26%
avg views ÷ 8,582 subscribers
Avg views / post
709
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
4
of 32 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 11 November 2026
Posts held32 (25 March 2026 – 11 November 2026)
Views total1,417
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 01:07 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
313
Videos
54
Links
440

Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
46s
Average length
23s

Measured directly from 2 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 4 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 12:23 UTCviews —

HAMSTER CRYPTO CALLS pinned «$JOB is now available on Bitget Onchain officially a part-time employee of Bitget, still waiting to find out what my responsibilities are bitget.com/on-chain/sol/9 Pq7aLAbhDG2tTnS22cm6kuysZVcZpLFE368HWuypump https://x.com/dogwifjob_sol/status/21202897…»

11 Nov 2026, 12:23 UTC707 viewsread 13 November 2026

$JOB is now available on Bitget Onchain officially a part-time employee of Bitget, still waiting to find out what my responsibilities are bitget.com/on-chain/sol/9 Pq7aLAbhDG2tTnS22cm6kuysZVcZpLFE368HWuypump https://x.com/dogwifjob_sol/status/2120289716952240439?a=R10gl_yCz0uqrg0JCaA&s=20

31 Oct 2026, 10:49 UTC710 viewsread 13 November 2026
Photo

Aegis AI is building the next generation of AI-powered blockchain intelligence on Base, helping users analyze tokens, track wallets, monitor liquidity, and identify on-chain risks with greater confidence. Project is audited. Relevant links: Presale link: https://www.pinksale.finance/launchpad/base/0xF08d4D691Eb187D13251616e80745F46291BF9F1 TG : https://t.me/AegisonBase Website: https://aegisonbase.io/

29 Sept 2026, 19:49 UTC690 viewsread 13 November 2026
Photo

Hi HamsterCall Fam! There's a team behind the M32 project. Marketing is active. MC +300k now That’s where $M32 enters the picture. Powered by MPP32, $M32 is building payment rails that let AI agents discover and pay for services on Solana through a single And now things are getting interesting… Mario Nawfal’s Roundtable just posted about it — and the $M32 team is hitting the Roundtable this Friday. This isn’t just …

28 Sept 2026, 11:00 UTC697 viewsread 13 November 2026
Photo

Nearpad Creator fees are swept through NEAR Intents into Zcash or Monero and handed to everyone holding. Hold a coin launched here and earn. No wrapper, no bridge. https://www.geckoterminal.com/solana/pools/8N2XJYyVBMrd4B5LUTd5pFe3uWwp5h4cWib9AxTxbHxv?utm_sourcekobascalls https://nearpad.tech https://x.com/nearpadtech 6uPEdkU2xPg1iyfLzV1ssUwvve8nndA2sd6nBFrb1n58

25 Sept 2026, 07:50 UTC735 viewsread 13 November 2026
Photo

DOKYO Hello Hamstercall family! I've connected you with a fantastic project. An experienced team and excellent marketing. Success for this project will be easy. DOKYO is bringing something different to the Solana memecoin scene. Built around one simple idea: the only enemy in the room is your own fear. The lore, characters, and community are already taking shape, giving $DOKYO an identity beyond just another ticke…

15 Sept 2026, 08:21 UTC729 viewsread 13 November 2026
Photo

Aegis AI is building the next generation of AI-powered blockchain intelligence on Base, helping users analyze tokens, track wallets, monitor liquidity, and identify on-chain risks with greater confidence. Project is audited. Not a big softcap, curious to see how the raise will end up being. Relevant links: Presale link: https://www.pinksale.finance/launchpad/base/0xF08d4D691Eb187D13251616e80745F46291BF9F1 TG : ht…

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

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

“HAMSTER CRYPTO CALLS” (@HamsterCryptoCalls), 8,582 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/HamsterCryptoCalls.

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.