Telegram RegisterThe public register of Telegram
Telegram profile photo for may.crypto {🦅}

Channel

may.crypto {🦅}

@maycrypto

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

17,032subscribers

-526 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001517285523
TypeChannel
Username@maycrypto
Descriptionдневник интернет-капиталиста про новые деньги, мышление игрока и выход за нормисные рамки автор: @may_adm менеджер MiT: @lemilenik канал содержит информацию о продуктах и услугах автора
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held37
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/maycrypto

Topic

Education — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 53% 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.

No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.

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
@may_crypto7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (6–1)

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 1 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 40 comparable posts for this entry, running 4 August 2026 to 3 September 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).

Recorded under the key clone_source, 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

17,03217,55817,2956 August 2026 — 17,558 subscribers7 August 2026 — 17,549 subscribers8 August 2026 — 17,546 subscribers9 August 2026 — 17,537 subscribers10 August 2026 — 17,523 subscribers11 August 2026 — 17,527 subscribers12 August 2026 — 17,515 subscribers12 August 2026 — 17,514 subscribers14 August 2026 — 17,494 subscribers15 August 2026 — 17,483 subscribers16 August 2026 — 17,479 subscribers18 August 2026 — 17,482 subscribers19 August 2026 — 17,480 subscribers20 August 2026 — 17,476 subscribers22 August 2026 — 17,474 subscribers23 August 2026 — 17,468 subscribers25 August 2026 — 17,466 subscribers26 August 2026 — 17,467 subscribers26 August 2026 — 17,465 subscribers27 August 2026 — 17,456 subscribers28 August 2026 — 17,453 subscribers30 August 2026 — 17,442 subscribers31 August 2026 — 17,443 subscribers1 September 2026 — 17,440 subscribers2 September 2026 — 17,436 subscribers3 September 2026 — 17,416 subscribers5 September 2026 — 17,411 subscribers8 September 2026 — 17,400 subscribers11 September 2026 — 17,379 subscribers13 September 2026 — 17,373 subscribers14 September 2026 — 17,372 subscribers16 September 2026 — 17,357 subscribers18 September 2026 — 17,344 subscribers25 September 2026 — 17,346 subscribers4 October 2026 — 17,281 subscribers8 October 2026 — 17,269 subscribers15 November 2026 — 17,032 subscribers6 August 202615 November 2026
37 measurements spanning 101 days, net -526. 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 16,953–17,637 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 37
Measured (UTC)SubscribersChange
15 Nov 2026, 13:5617,032-237
8 Oct 2026, 22:1717,269-12
4 Oct 2026, 08:1617,281-65
25 Sept 2026, 17:2017,346+2
18 Sept 2026, 23:4117,344-13
16 Sept 2026, 12:3717,357-15
14 Sept 2026, 15:5917,372-1
13 Sept 2026, 04:5717,373-6
11 Sept 2026, 03:3617,379-21
8 Sept 2026, 03:3517,400-11
5 Sept 2026, 00:0117,411-5
3 Sept 2026, 10:4617,416-20
2 Sept 2026, 04:3417,436-4
1 Sept 2026, 05:5517,440-3
31 Aug 2026, 02:5817,443+1
30 Aug 2026, 00:4717,442-11
28 Aug 2026, 23:1417,453-3
27 Aug 2026, 23:0417,456-9
26 Aug 2026, 23:5717,465-2
26 Aug 2026, 01:1517,467first reading

Engagement

101 posts held, back to 4 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 57 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.9%
avg views ÷ 17,032 subscribers
Avg views / post
3,220
20 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 101 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 15 November 2026
Posts held101 (4 August 2026 – 15 November 2026)
Views total64,360
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 13:58 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
≈3,160
Videos
≈535
Links
≈1,410

Lifetime counters from Telegram’s own channel header, read 15 November 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 07s
Average length
17s

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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 20 posts held from the last 30 days (5.00%) 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).

15 Nov 2026, 12:23 UTC≈1,300 viewsread 15 November 2026
Photo

как же хорошо щас

Signed https://may

15 Nov 2026, 11:06 UTC≈1,600 viewsread 15 November 2026

мысль такая пришла что легко быть пессимистом и пораженцем. для этого не требуется ни духа, ни характера а вот быть оптимистом при любой ситуации - это хардскилл

Signed https://may

15 Nov 2026, 09:22 UTC≈1,970 viewsread 15 November 2026

марафон ИИ 7.0 марафон ИИ 7.0 марафон ИИ 7.0 приятного просмотра

Signed https://may

13 Nov 2026, 13:53 UTC≈2,860 viewsread 15 November 2026

по upscale закинут всем по $1000 кто зарегался в тот день. сейчас у них много техработ из-за акций к черной пятнице, поэтому проявите чутка терпения, господа

Signed https://may

13 Nov 2026, 11:36 UTC≈3,050 viewsread 15 November 2026
Photo

эту тему с фото покупаешь, варишь в моке, пьешь, включаешь техно (меняй минимал на эйфорик), подрубаешь Claude Code и рвешь пределы. удачи

Signed https://may

13 Nov 2026, 10:08 UTC≈3,000 viewsread 15 November 2026
Photo

не унывайте пацаны

Signed https://may

13 Nov 2026, 08:31 UTC≈3,040 viewsread 15 November 2026
Photo

буквально сейчас бычий рынок возможностей. накопление перед взлетом и всеобщей эйфорией, будто мы в марте 2024

Signed https://may

10 Nov 2026, 17:06 UTC≈3,550 viewsread 15 November 2026

тут и тут еще есть счета бесплатные

Signed https://may

10 Nov 2026, 12:37 UTC≈3,710 viewsread 15 November 2026

на 1 и 2 еще есть места + время работаем

Signed https://may

10 Nov 2026, 11:08 UTC≈4,480 viewsread 15 November 2026

🚨 ЗАБИРАЙ $3000! абсолюнто бесплатно в каждом из этих 3 сервисов для проп-трейдинга* ты можешь получить депозит в $1000. *это когда трейдер торгует на финансовых рынках на деньги компании. если сделки приносят прибыль, трейдер обычно получает её часть. 2 - Upscale. заходим на сайт Upscale и регистрируемся. в течение ~30 часов будет поступление счета на $1000. раздача счетов ограничена временем. 2 - HashHedge. з…

Signed https://may

Showing the 12 most recent of 101 posts we hold for @maycrypto. 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 recorded as deleted after publishing

We recorded 4 posts on @maycrypto as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
14 August 2026
Most recent seen missing
14 August 2026
Median time before seen missing
46 hours
Seen missing in the last 30 days
0

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 13 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

DanieL Finance Team🤑
@nftdaniel · 18,906
Telegram ranks this channel #8 of 62 here — alongside 61 others — read 4 October 2026
TTC | TimeToCrypto
@nftTTC · 33,644
Telegram ranks this channel #8 of 73 here — alongside 72 others — read 2 September 2026
Ворк в крипте, только хардкор
@workIncrypts · 32,861
Telegram ranks this channel #13 of 75 here — alongside 74 others — read 3 September 2026
ꜱᴇɪɴᴀʀᴜᴋɪʀᴏ
@seinarukiro · 77,891
Telegram ranks this channel #14 of 68 here — alongside 67 others — read 22 September 2026
Banlife теперь в Telegram
@banlife_crypto · 21,270
Telegram ranks this channel #15 of 78 here — alongside 77 others — read 24 September 2026
BIG BALLS BIRDS
@big_balls_birds · 19,049
Telegram ranks this channel #16 of 69 here — alongside 68 others — read 30 September 2026
ТЕМКА В СХЕМКЕ
@TVS_TEAM · 37,205
Telegram ranks this channel #16 of 70 here — alongside 69 others — read 31 August 2026
Crypto Abuzik
@CryptoAbuzik · 20,655
Telegram ranks this channel #18 of 74 here — alongside 73 others — read 23 September 2026
moni talks [крипта]
@moni_talks · 24,471
Telegram ranks this channel #22 of 81 here — alongside 80 others — read 15 September 2026
Коля флипает
@sol_TOP · 39,987
Telegram ranks this channel #22 of 58 here — alongside 57 others — read 30 August 2026
Steamify - Фарми скины CS2
@steamify · 37,993
Telegram ranks this channel #22 of 68 here — alongside 67 others — read 29 August 2026
Крипту⚡️Фармим
@cryptfarm · 19,291
Telegram ranks this channel #24 of 82 here — alongside 81 others — read 1 October 2026
Cryptobiznes
@crypt_biznes · 27,012
Telegram ranks this channel #25 of 74 here — alongside 73 others — read 11 September 2026
👁‍🗨Deki Gang💰
@DekiGang · 39,286
Telegram ranks this channel #25 of 74 here — alongside 73 others — read 30 August 2026
Альфа Шефа
@chiefsalpha · 37,055
Telegram ranks this channel #32 of 77 here — alongside 76 others — read 30 August 2026
CRYPTON | Крипта, ИИ, Финансы
@crypton_off · 57,654
Telegram ranks this channel #32 of 85 here — alongside 84 others — read 22 August 2026
криптапиражок
@cryppi · 29,990
Telegram ranks this channel #37 of 73 here — alongside 72 others — read 7 September 2026
Алекс о Крипте
@alexincrypta · 16,918
Telegram ranks this channel #43 of 54 here — alongside 53 others — read 3 October 2026
Фруто Сrypto Няня
@frutocrypto · 19,437
Telegram ranks this channel #44 of 49 here — alongside 48 others — read 22 September 2026
Свидетели крипты
@fomobas · 25,564
Telegram ranks this channel #44 of 83 here — alongside 82 others — read 15 September 2026
Крипто HeadHunter | WEB 3 Jobs
@cryptoheadhunter · 20,850
Telegram ranks this channel #46 of 82 here — alongside 81 others — read 28 September 2026
одиссея kekius maximus
@doge1 · 582,914
Telegram ranks this channel #47 of 79 here — alongside 78 others — read 8 August 2026
sad cat
@sadcatgamble · 27,604
Telegram ranks this channel #48 of 54 here — alongside 53 others — read 10 September 2026
CRYPTOGEN
@CRYPTOGENNNNNNN · 20,013
Telegram ranks this channel #49 of 74 here — alongside 73 others — read 27 September 2026

This channel appears in 40 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“may.crypto {🦅}” (@maycrypto), 17,032 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/maycrypto.

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.