Telegram RegisterThe public register of Telegram

Channel

⛽️ ГдеБЕНЗ

@gdebenzru

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

190,826subscribers

-885 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1004443906891
TypeChannel
Username@gdebenzru
DescriptionИнтерактивная карта АЗС, наличие топлива, обстановка на заправках и подтверждения от водителей. Без регистрации. Быстро. Удобно. 🇷🇺 Карта: https://gdebenz.ru/ Сотрудничество: @gdebenz_partner № 7678100659
CreatedBetween 1 June 2026 and 3 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/gdebenzru

Topic

Automotive — 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 85% 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
@gdebenzru/38 · this entry4 Jul 2026, 18:36 UTC@benzincream_russia/1414 Jul 2026, 20:15 UTC1.001.6 hours
@gdebenzru/46 · this entry8 Jul 2026, 03:46 UTC@benzincream_russia/1458 Jul 2026, 05:45 UTC1.002.0 hours
@gdebenzru/47 · this entry8 Jul 2026, 06:39 UTC@benzincream_russia/1468 Jul 2026, 07:00 UTC1.0020 minutes
@gdebenzru/35 · this entry3 Jul 2026, 03:38 UTC@benzincream_russia/1353 Jul 2026, 15:24 UTC0.9712 hours
@gdebenzru/37 · this entry4 Jul 2026, 10:52 UTC@benzincream_russia/1404 Jul 2026, 10:59 UTC0.977 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@benzincream_russia5 (5/5 hand-verifiable sample passed)0.991.6 hoursthis entry (50)

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 0 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 20 comparable posts for this entry, running 3 July 2026 to 29 July 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 @gdebenzru — which is this entry. That is a statement about our reading window, not a claim of authorship.

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

190,826191,711191,268.56 August 2026 — 191,711 subscribers6 August 2026 — 191,711 subscribers6 August 2026 — 191,647 subscribers7 August 2026 — 191,463 subscribers8 August 2026 — 191,321 subscribers9 August 2026 — 191,195 subscribers10 August 2026 — 191,019 subscribers11 August 2026 — 190,897 subscribers12 August 2026 — 190,826 subscribers6 August 202612 August 2026
9 measurements spanning 6 days, net -885. 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 190,693–191,844 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 03:45190,826-71
11 Aug 2026, 04:42190,897-122
10 Aug 2026, 04:11191,019-176
9 Aug 2026, 05:03191,195-126
8 Aug 2026, 05:16191,321-142
7 Aug 2026, 08:08191,463-184
6 Aug 2026, 11:10191,647-64
6 Aug 2026, 01:30191,711no change
6 Aug 2026, 00:52191,711first reading

Engagement

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

ERR · 30 days
89.7%
avg views ÷ 190,826 subscribers
Avg views / post
171,000
5 posts measured
Reaction rate
0.778%
reactions ÷ views · ER floor
Posts in window
5
of 20 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 29 July 2026
Posts held20 (3 July 202629 July 2026)
Views total855,900
Reactions total6,659
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 18:01 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
29
Links
40

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.

Reaction mix

35,656 reactions across 19 posts, in 20 distinct kinds. The most used accounts for 41.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14,70241.2%
👍12,71435.7%
🔥5,55715.6%
❤‍🔥8032.25%
👏3240.909%
🤝3240.909%
😢2800.785%
👎2270.637%
😱1750.491%
👌1650.463%
🙏1300.365%
💋490.137%
🥰450.126%
🎉330.093%
🫡320.09%
🗿250.07%
🌭240.067%
🤡180.05%
💩150.042%
🦄140.039%

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

Measured over the 20 most recent posts we hold, published 3 July 2026 to 29 July 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.

Telegram Stars

Stars received
976
across the posts below
Posts paid on
19
of 19 we hold a reading for · 100%
Most on one post
162
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gdebenzru. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 3 July 2026 to 29 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

29 Jul 2026, 07:12 UTC≈98,900 views1,067 reactions5 Starsread 12 August 2026
Photo

⛽️ Большое обновление ГдеБЕНЗ: чаты по городам и цены Обновились и сайт, и приложения. Рассказываем, что нового — и куда мы идём дальше 💚 💬 Чаты водителей по городам Теперь у каждого города свой чат. Не общая лента на всю страну, а разговор с теми, кто ездит по вашим улицам: где сейчас очередь, что с лимитами, куда лучше не соваться в час пик, на какой трассе спокойно. То, что не помещается в отметку «Есть / Нет»

👍656295🔥91👎13👏12

24 Jul 2026, 15:50 UTC≈143,000 views1,430 reactions9 Starsread 12 August 2026

Друзья, наше официальное приложение появилось в Google Play Market! Если для Вас удобнее приложение - милости просим 🙏💚 https://play.google.com/store/apps/details?id=ru.gdebenz.app.gde_benz_app

🔥862👍365134👎38❤‍🔥31

20 Jul 2026, 11:53 UTC≈219,000 views1,120 reactions16 Starsread 12 August 2026

Друзья, в скором времени поправим отображение АЗС в приложениях Столкнулись с лимитами, скоро все заработает! На сайте gdebenz.ru все работает без изменений Приносим свои извинения за неудобства! 🙏💚 📲 Где скачать • Google Play Market (Android) • RuStore (Android) • App Store (iPhone)

👍698🔥177168🙏44👎33

20 Jul 2026, 11:14 UTC≈196,000 views1,534 reactions74 Starsread 12 August 2026
Photo

⛽️ У ГдеБЕНЗ появились ОФИЦИАЛЬНЫЕ приложения! Вы просили об этом с первого дня — и вот оно: ГдеБЕНЗ теперь можно установить как обычное приложение. Спасибо, что вы с нами — это обновление, как всегда, для вас 💚 📲 Где скачать • Google Play Market (Android) https://play.google.com/store/apps/details?id=ru.gdebenz.app.gde_benz_app • RuStore (Android): https://www.rustore.ru/catalog/app/ru.gdebenz.app.gde_benz_app •

❤‍🔥689👍465237🔥103👎40

17 Jul 2026, 04:51 UTC≈199,000 views1,508 reactions37 Starsread 12 August 2026
Photo

⛽️ Комментарии к АЗС в ГдеБЕНЗ! Настоящая сила ГдеБЕНЗ — это вы, водители, которые помогают друг другу. Теперь у этой взаимопомощи появился голос: комментарии, свой профиль и команда друзей 💚 Спасибо, что вы с нами. Это обновление — снова ваше: мы просто сделали то, о чём вы просили чаще всего 🙌 💬 Комментарии под каждой АЗС Теперь под любой заправкой — живая лента водителей. «Из 5 колонок работает 1», «95-й привез

835👍404🔥174👎78👏17

13 Jul 2026, 03:19 UTC≈230,000 views2,666 reactions162 Starsread 12 August 2026
Photo

💵 Маленькое, но полезное обновление ГдеБЕНЗ Иногда приезжаешь на заправку, а там карты и СБП не проходят — только наличные. Обидно узнать об этом уже на кассе. Теперь такое можно отметить заранее — для соседей-водителей 💚 🏷 Новая метка «Только наличными» Когда отмечаете, что на АЗС есть топливо, можно добавить уточнение: сейчас здесь берут только наличные. Рядом — уже знакомая метка «Только по топливным картам». Вс

🔥1,380787👍435🤝47🥰17

12 Jul 2026, 04:14 UTC≈210,000 views2,237 reactions128 Starsread 12 August 2026
Photo

⛽️ Большое обновление ГдеБЕНЗ! Теперь карта не просто показывает, где по отметкам водителей есть топливо, а помогает ответить на главный вопрос за рулём: «куда сейчас заехать заправиться?» 💚 Спасибо, что вы с нами и каждый день отмечаете, где есть топливо и по какой цене. Всё это обновление во многом ваше — мы взяли то, что вы делаете вместе, и сделали удобнее для всех 🙌 🧭 Новый экран «Где заправиться» Раньше здес

1,370👍555🔥255👏50😱7

9 Jul 2026, 09:06 UTC≈220,000 views2,631 reactions69 Starsread 12 August 2026
Photo

⛽️ Большое обновление ГдеБЕНЗ! Теперь на карте есть ЦЕНЫ 💚 Друзья, спасибо, что вы с нами! ГдеБЕНЗ живёт благодаря вам — и сегодня он стал ещё полезнее. Мы добавили то, о чём многие просили: цены на топливо. Теперь можно не только видеть, где есть бензин, но и заранее прикинуть, где почём. 💸 Как это работает Цены отмечают сами водители — прямо на стеле или по чеку. Мы, как всегда, ничего не утверждаем от себя: по

1,520🔥629👍434💋33💩15

8 Jul 2026, 16:36 UTC≈192,000 views1,835 reactions13 Starsread 12 August 2026
Photo

🚨 Осторожно: в Google Play — ПОДДЕЛКА «ГдеБЕНЗ». Это не мы. Кто-то выложил в Google Play мошенническое приложение под нашим именем «ГдеБЕНЗ» (разработчик «TOV KOFE GRUPP»), скопировав наше название, логотип и даже наши скриншоты. К нам это не имеет никакого отношения. Это приложение обманом выдаёт себя за нас. Что оно делает с вашими данными, к каким разрешениям лезет и какую рекламу крутит — мы не знаем и не контр

👍1,300319👌132😱70👎14

8 Jul 2026, 16:10 UTCviews —

⛽️ ГдеБЕНЗ pinned «⚠️ Официальное заявление ГдеБЕНЗ ⚠️ Друзья, важное — пожалуйста, прочитайте и обезопасьте себя. 💚 ГдеБЕНЗ — это бесплатный народный сервис. Мы показываем, где сейчас есть бензин, и не зарабатываем на вас. Поэтому официально заявляем: 🚫 Мы не выпускали никаких…»

8 Jul 2026, 06:39 UTC≈189,000 views1,405 reactions18 Starsread 12 August 2026

❗️ВАЖНОЕ❗️ Основной адрес gdebenz.ru может открываться не у всех. Но знайте главное: мы вас не бросаем и никуда не уходим. ГдеБЕНЗ работал, работает и будет работать дальше — для вас 💚 👉 Если основной сайт не грузится — заходите на запасной: gdebenz.org Эти два сайта ПОЛНОСТЬЮ идентичные, все метки сохранены Сбросьте кэш или зайдите через инкогнито, если не работает Этот канал — страховка. Здесь, что бы ни случи

919🔥245🤝190👏35💋16

8 Jul 2026, 03:46 UTC≈167,000 views919 reactions5 Starsread 12 August 2026

⚡️ Друзья, сайт временно может не открываться У части из вас gdebenz.ru сейчас не грузится. Причина техническая — на стороне регистратора домена, мы уже занимаемся восстановлением. Что важно знать: 🔹 Все ваши отметки и данные целы — ничего не потеряно. 🔹 Сервис и серверы работают штатно, проблема только с адресом сайта. 🔹 Ничего переустанавливать не нужно — как только всё восстановится, сайт откроется сам. Держим

502👍266🙏86👌33🫡32

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 119,525 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.

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

Named by 6 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.

Domains linked from posts

7 domainsthis 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.

gdebenz.ru16 posts · 3 July 2026 – 29 July 2026 · example post
pay.cloudtips.ruregistrable domain: cloudtips.ru12 posts · 3 July 2026 – 29 July 2026 · example post
gdebenz.org8 posts · 8 July 2026 – 29 July 2026 · example post
play.google.comregistrable domain: google.com4 posts · 20 July 2026 – 29 July 2026 · example post
apps.apple.comregistrable domain: apple.com3 posts · 20 July 2026 – 29 July 2026 · example post
www.rustore.ruregistrable domain: rustore.ru3 posts · 20 July 2026 – 29 July 2026 · example post
vc.ru1 post · 7 July 2026 – 7 July 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“⛽️ ГдеБЕНЗ” (@gdebenzru), 190,826 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/gdebenzru.

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.