Telegram RegisterThe public register of Telegram

Channel

Алкогольные Рецепты \ Лучшие Коктейли

@best_cock

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

7,437subscribers

-1 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-1001734730072
TypeChannel
Username@best_cock
Description№ 4897911666 Разнообразные рецепты Коктейлей на любой вкус. По вопросам рекламы - @kami_vaL
CreatedBetween 1 January 2022 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/best_cock

Topic

Other / unclassifiable — 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 87% 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
@bar_recept/102619 Oct 2025, 12:41 UTC@best_cock/1009 · this entry19 Oct 2025, 12:41 UTC1.00under a minute
@bar_recept/102723 Oct 2025, 06:25 UTC@best_cock/1010 · this entry23 Oct 2025, 06:25 UTC1.00under a minute
@bar_recept/102929 Oct 2025, 11:06 UTC@best_cock/1012 · this entry29 Oct 2025, 11:06 UTC1.00under a minute
@bar_recept/10325 Nov 2025, 09:37 UTC@best_cock/1015 · this entry5 Nov 2025, 09:37 UTC1.00under a minute
@bar_recept/10337 Nov 2025, 19:37 UTC@best_cock/1016 · this entry7 Nov 2025, 19:37 UTC1.00under a minute
@bar_recept/10349 Nov 2025, 16:34 UTC@best_cock/1017 · this entry9 Nov 2025, 16:34 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@bar_recept12 (8/8 hand-verifiable sample passed)1.00under a minute@bar_recept (120)

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. None of the 12 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 13 comparable posts for this entry, running 19 October 2025 to 30 November 2025. 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 @bar_recept. 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

7,4377,4387,437.57 August 2026 — 7,438 subscribers7 August 2026 — 7,438 subscribers10 August 2026 — 7,437 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net -1. 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 7,437–7,438 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 10:087,437-1
7 Aug 2026, 08:007,438no change
7 Aug 2026, 07:507,438first reading

Engagement

20 posts held, back to 19 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof 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 20 posts for this entry, the most recent from 30 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
991
Videos
1
Links
4

Lifetime counters from Telegram’s own channel header, read 12 August 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.

Recent posts

30 Nov 2025, 18:21 UTC≈9,280 viewsread 12 August 2026

Канал временно не обслуживается, за рекламой обращаться к действующему сотруднику на других каналах @pinky_reklama

30 Nov 2025, 13:40 UTC≈7,190 viewsread 12 August 2026
Photo

Тигр Ингредиенты: Ром ямайский 20 мл Ром черный 20 мл Вермут сухой 20 мл Сок лайма 15 мл Оршад 10 мл Ликер вишня 10 мл Бенедиктин 1 бар.л Ангостура 4 дэш Приготовление: Шейк. Гарниш вишня и мята.

28 Nov 2025, 04:24 UTC≈7,760 viewsread 12 August 2026
Photo

Прованская прогулка Ингредиенты: Апероль 40 мл Априкот бренди 10 мл Сок персиковый 30 мл Сироп розмарин 10 мл Белок яйца Просекко Приготовление: Шейк. Долить просекко. Гарниш цветок.

25 Nov 2025, 10:00 UTC≈9,140 viewsread 12 August 2026
Photo

Горячий тодди с сидром Виски, сидр яблочный, сок лимона, гарниш яблоко

23 Nov 2025, 17:42 UTC≈9,260 viewsread 12 August 2026
Photo

Ингредиенты: • Джин бим хани — 40 мл • Пюре облепиха — 3 мл • Сок лимона — 2 мл • Сироп сахарный — 1 мл • Белок — 2 г Способ приготовления: 1 В шейкер со льдом вылейте джин бим хани, добавьте белок, выжмите сок из лимона, добавьте сахарный сироп и все тщательно взбейте. 2 Затем удалите лед с помощью стрейнера и снова взбейте. 3 Перелейте готовый коктейль в бокал и украсьте по своему усмотрению, например, лимо

21 Nov 2025, 15:05 UTC≈7,600 viewsread 12 August 2026
Photo

Италиан маргарита Текила, лимончелло, сок лайма, сок лимона, сироп агава, гарниш цветок

19 Nov 2025, 11:52 UTC≈7,140 viewsread 12 August 2026
Photo

Лаванда дрим Ингредиенты: Джин 60 мл Сок лимона 20 мл Сироп лаванда 15 мл Приготовление: Шейк. Гарниш вишня.

17 Nov 2025, 08:22 UTC≈7,110 viewsread 12 August 2026
Photo

Пряная тыква Бейлис, водка, калуа, сироп тыквенный пирог, гарниш молотая тыква, взбитые сливки и палочка корицы

15 Nov 2025, 06:35 UTC≈7,120 viewsread 12 August 2026
Photo

Хей мамбо Ингредиенты: Апероль 30 мл Мескаль 15 мл Текила 15 мл Фреш ананаса 40 мл Крем кокосовый 30 мл Сок лайма 15 мл Приготовление: Шейк. Гарниш слайс и лист ананаса.

13 Nov 2025, 09:11 UTC≈7,130 viewsread 12 August 2026
Photo

Манго и ванила физ Водка ваниль, манго, сок лайма, сироп ваниль, биттер ваниль, просекко, гарниш манго и розмарина

11 Nov 2025, 08:32 UTC≈7,580 viewsread 12 August 2026
Photo

Негрони фраппе Ингредиенты: Джин 20 мл Амаро 20 мл Вермут сладкий 20 мл Сок апельсина 20 мл Оранж биттер 3 дэш Приготовление: Шейк. Гарниш цедра апельсина.

9 Nov 2025, 16:34 UTC≈7,110 viewsread 12 August 2026
Photo

Хурма мескаль сауэр Текила, мескаль, пюре хурма, сироп хурма, сок грейпфрута, сок лайма, белок яйца, гарнир слайс хурмы

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

Citation-graph rank

Citation-graph rank — 1,132,463 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Алкогольные Рецепты \ Лучшие Коктейли” (@best_cock), 7,437 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/best_cock.

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.